title: Configuring Microsoft Dynamics CRM 2011 IIS Settings, Registry Settings & E-mail Router Deployment URL
body: <p>I need help with configuration settings for CRM 2011 On-Premise. I am having problems finding example configurations with load balanced app servers. It seems most of the examples on the internet are for single app server configurations.  </p>
  
  <p>Our current setup consists of a pair of Cisco CSS (hardware load balancers) configured to load balance 2 application servers CRMAPP1 &amp; CRMAPP2. The Cisco CSS's are configured with a VIP i.e. crmtest.domain.org and incoming/outgoing is set to port 80. </p>
  
  <h2>IIS Settings</h2>
  
  <p>In IIS Manager I originally configured two bindings like the following:   </p>
  
  <p>Binding 1:</p>
  
  <blockquote>
    <p>Type: http<br>
    Host Name: crmtest.domain.org<br>
    Port: 80<br>
    IP Address: *  </p>
  </blockquote>
  
  <p>Binding 2:</p>
  
  <blockquote>
    <p>Type: http<br>
    Host Name:<br>
    Port: 1000<br>
    IP Address: *  </p>
  </blockquote>
  
  <p>I originally added the second binding (with port 1000) so we could target each individual app server. 
  For example, if we deployed a health check application on each CRM app server "http://crmapp1:1000/HealthCheck/default.aspx" and "http://crmapp2:1000/HealthCheck/default.aspx", this would be one way to check the health for each server. </p>
  
  <p>I say originally because I have since taken out binding 2 (with port 1000) and now only have a single binding for the load balanced URL (crmtest.domain.org). I will try to explain why. </p>
  
  <p>From many sources on the internet, I have been reading that more than one IIS bindings are not supported in CRM and we should only have 1 single binding. In my case this would be the load balanced URL crmtest.domain.org. </p>
  
  <p><strong>Question 1:</strong>  Will adding the second IIS binding, with port 1000, cause any problems with the CRM application?  </p>
  
  <p><strong>Question 2:</strong> For network load balancing &amp; WCF service endpoints to work properly, is it required to have one single IIS binding set to the cluster address i.e. crmtest.domain.org, port 80, IP Address: * ?</p>
  
  <p><strong>Question 3:</strong> Are there any settings or configurations in CRM that require us to target an individual app server?</p>
  
  <h2>Registry Settings</h2>
  
  <p>The Registry Settings in question are the following for each app server:<br>
  IncomingEmailServer: crmtestmr1<br>
  LocalSdkPort: 80<br>
  ServerUrl: "http://crmtest.domain.org/MSCRMServices"  </p>
  
  <p><strong>Question 4:</strong> Should both ServerURL registry settings, on each app server, be the same load balanced URL such as "http://crmtest.domain.org/MSCRMServices" or different URL's for each app server such as "http://crmapp1:1000/MSCRMServices" and "http://crmapp2:1000/MSCRMServices"?    </p>
  
  <p><strong>Question 5:</strong> Should the IncomingEmailServer registry setting simply be the E-mail Router server name? </p>
  
  <p><strong>Question 6:</strong> Should the LocalSdkPort registry setting be port 80 or a local port such as 1000?</p>
  
  <h2>E-Mail Router Deployment URL</h2>
  
  <p><strong>Question 7:</strong> Under the [Deployments] tab in the E-Mail Router Configuration Manager should the Microsoft Dynamics Server be the load balanced URL "http://crmtest.domain.org/Organization-Test" or a single app server URL such as "http://crmapp1:1000/Organization-Test"?</p>
  
  <h2>Other Configuration Settings (trying to be thorough)</h2>
  
  <p><strong>Service Principal Names (SPN)</strong><br>
  The Service Principal Names (SPN) are currently configured like the following: </p>
  
  <blockquote>
    <p>HOST/CRMAPP1<br>
    HOST/CRMAPP1.main.domain.org<br>
    RestrictedKrbHost/CRMAPP1<br>
    RestrictedKrbHost/CRMAPP1.main.domain.org<br>
    tapinego/CRMAPP1<br>
    tapinego/CRMAPP1.main.domain.org<br>
    TERMSRV/CRMAPP1<br>
    TERMSRV/CRMAPP1.main.domain.org<br>
    WSMAN/CRMAPP1<br>
    WSMAN/CRMAPP1.main.domain.org</p>
  </blockquote>
  
  <p><strong>Question 8:</strong>  Is there any reason we should add in HTTP/CRMAPP1 or HTTP/CRMAPP1.main.domain.org?</p>
  
  <p><strong>Service Endpoints in Developer Resources</strong><br>
  The current Service Endpoints are configured like the following:  </p>
  
  <blockquote>
    <p>Discovery Service<br>
    "http://crmtest.domain.org/XRMServices/2011/Discovery.svc"</p>
    
    <p>Organization Service<br>
    "http://crmtest.domain.org/Organization-Test/XRMServices/2011/Organization.svc"</p>
    
    <p>Organization Data Service<br>
    "http://crmtest.domain.org/Organization-Test/XRMServices/2011/OrganizationData.svc"</p>
  </blockquote>
  
  <p><strong>Deployment Manager Configurations</strong><br>
  The Web Addresses in Deployment Manager are currently configured like the following:   </p>
  
  <blockquote>
    <p>Binding Type:<br>
    (x) HTTP  </p>
    
    <p>Web Application Server:<br>
    crmtest.domain.org:80  </p>
    
    <p>Organization Web Service:<br>
    crmtest.domain.org:80  </p>
    
    <p>Discovery Web Service:<br>
    crmtest.domain.org:80</p>
    
    <p>Deployment Web Service:<br>
    crmtest.domain.org:80</p>
  </blockquote>
  
  <p><strong>CRM Deployment Properties in MSCRM_CONFIG database</strong>  </p>
  
  <blockquote>
    <p>ADDeploymentSdkRootDomain: crmtest.domain.org:80<br>
    ADDiscoveryRootDomain: crmtest.domain.org:80<br>
    ADsdkRootDomain: crmtest.domain.org:80<br>
    ADWebApplicationRootDomain: crmtest.domain.org:80<br>
    AsyncSdkRootDomain: crmtest.domain.org:80  </p>
  </blockquote>