Is it possible/supported to have a CRM 2011 host work with two different host names? We have tried this, but not everything works perfectly.
Example:
- A server with server name “app1“.
- An AD/DNS entry pointing the host name “crm” to “app1“.
When users navigates to “crm” the requests work 99% of the time, but a few internal javascripts in CRM targets the original “app1” server. For example a request from normal edit forms that retrieves the roles. The javascript variable called “*SERVER_NAME*” always has value of “app1“, no matter the request URL. A cross-server warning might appear or the functionality may just silently fail.
This also happens when accessing the FQDN of the server, so “app1.mydomain.com” still produces the same result and failing/warning functionality.
I imagine this would be a similar problem when dealing with load balanced installations? How do they handle this? I.e. they target host name X and can get host name Y or Z.
Edit: I’ve understood that this may be called “domain alias” or “host alias” since it is an active directory entry.
You cannot have multiple hostnames for the CRM system.
Open the deployment manager on the CRM server.
Go to Actions -> Properties -> Addresses
Adjust the stated addresses to the one which you use to access the CRM system. These settings are important for the CRM to define its “identity”.
If you have configured IFD you configure an additional external identity.
By the way. Depending on your environment it might be necessary to set an SPN. See http://blogs.msdn.com/b/webtopics/archive/2009/01/19/service-principal-name-spn-checklist-for-kerberos-authentication-with-iis-7-0.aspx
Regarding NLB: http://technet.microsoft.com/en-us/library/hh699803.aspx