Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
CRM IFD Questions RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    I read the Implementation Guide and the Working with CRM book as well as the IFD help files but I'm still not entirely sure what to do.

    I have a CRM server internally known as [servername]. During installation, I set it to run on [servername]:5555

    [servername] is connected to the internet and is known externally via [servername].triumtech.net. There are organizations A and B and to access CRM from the outside, I go on [servername].triumtech.net:5555/A. I know this is very temporary so I'd like to use the IFD setup.

    I have a domain [domain] that I control the DNS of. I have therefore set the DNS of crm.[domain].com to the public IP of [servername] and also set A.crm.[domain].com and B.crm.[domain].com to the same IP. My goal is to have CRM accessible via internet by A.crm.[domain].com or crm.[domain].com, whatever the Outlook client prefers.

    I also host a web application on the same server in IIS accessible via [servername]:80 internally and [servername].triumtech.net:80 externally. So everything DNS wise points to the same server. How should I sort it all out? Should I bind the CRM IIS site to crm.[domain].com:80? If I do so, can the web application still access CRM as if it were an internal server? How do the internal users access CRM? How should I set my IFD Root Domain and AD Root Domain?

     

    Thanks

    Tuesday, August 24, 2010 8:05 PM

Answers

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    In the IFD tool you will set the IFD ap root domain to triumtech.net:5555, the AD app root domain will be set to: servername:5555.

    Internally, users will type int servername:5555/orgname, externally they will type in http://a.crm.triumtech.net:5555

    This will not interfere with the site you have running on port 80.

    Everything else you have looks good to me.

    Jerry http://www.crminnovation.com
    Tuesday, August 24, 2010 8:19 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I ended up binding crm.[domain].com:80 to my CRM server and ran the IFD. The CRM sites seem to work well under crm.[domain].com/A etc but not under A.crm.[domain].com which I thought it was supposed to do. The DNS records are set but I don't really get how it would work given that the CRM IIS site is set to respond to crm.[domain].com. How would it know to respond to A.crm.[domain].com let alone mapping it to the right organisation?

    Also in the current setup, I somehow cannot connect to it via Outlook. It needs to access it via internet and entering crm.[domain].com or crm.[domain].com/A in the URL gives a specified server not available on some computers and mandatory updates cannot be installed on some other. Did I miss anything? The server is connected directly to the internet

    Thanks!

    Wednesday, August 25, 2010 10:31 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    wow, I just realised that the IFD tool never did anything. It just doesn't give an error when not run with admin rights. 

    Now I get it to actually run but accessing crm.[domain].com or A.crm.[domain].com etc give 404 errors. But if I bound A.crm... and B.crm.... etc and all to the CRM site, it works! Is it the right way of doing it?

    Wednesday, August 25, 2010 10:56 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    yes.
    Jerry http://www.crminnovation.com
    Thursday, August 26, 2010 1:27 PM