This is Part 2b of a Series of posts. Refer Part 1 and Part 2.

If you configured your development environment as per my previous post - you'll notice that if you log into the server using the IP (192.168.1.1) or the Host file configured URL (eg.http://contoso.crm.philiprichardson.org) that you will be prompted for Windows Credentials.

I use a neat little reg key on the CRM Server to change the internal subnet of the IFD setting. CRM looks at the IP of the incoming request and if this is in the internal range (this reg key) then it gives you a 'Windows experience'. If the IP is external it gives you an 'IFD experience'.

So if my client is configured with an IP of 192.168.1.2 (Subnet: 255.255.255.0).

  • When the Internal range is 192.168.1.1-255.255.255.0 you will get a Windows Experience. This is the value we provided in our config.xml when we installed CRM.
  • When the Internal range is 192.168.1.1-255.255.255.255 you will get an IFD Experience. This is because my client on the host OS has an IP of 192.168.1.2 (Subnet: 255.255.255.0) is outside the internal range.

 

Here are the two Reg Key Modifications. Note that this is supported (see the Implementation Guide (IG) for more details).

IFD Experience:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRM]
"IfdInternalNetworkAddress"="192.168.1.1-255.255.255.255"

Windows Experience:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRM]
"IfdInternalNetworkAddress"="192.168.1.1-255.255.255.0"

If you have your own network config - then you will need to work out the network addresses and subnet masks on your own. I strongly suggest you read the IG and the IFD Setup Doc. If you environment is on your network you may want to consult with your network administrator to figure out the right IP ranges.

Update: Fixed typos in the Subnet masks.