Microsoft CRM Houston

Installation Tips

• Microsoft Dynamics CRM requires the database to be installed on the default instance of SQL Server and requires mixed mode.
• Make sure before beginning the installation that none of the websites existing in IIS where CRM is to be installed are using a default port 80 without a host header.
• Create a separate Active Directory Organizational Unit for the CRM Security Groups that will be created during installation.
  • If you completely uninstall and reinstall, it is best to setup a new organizational unit for the reinstallation otherwise it could become difficult to differentiate between the old-unused security groups and the ones being used.
  • Create a separate administrator account to install CRM with – it’s a bad idea to use your regular domain admin account. Make sure this new account is in the Administrators Security Group on the local machine where CRM is being installed.
• Make sure the Windows Support tools are installed on the server where CRM is going to be installed. ADSI Edit Tool will be needed when you setup constrained delegation.
• If you use the IFD utility don’t try to do so with split DNS as the Outlook client will not authenticate correctly for laptop users that go between the local domain and remote.
• If you use SSL, get a wildcard certificate and learn how to setup a fully qualified host header in IIS. This will allow you to have multiple SSL enabled sites within a single IIS installation.
• Wait at least a month to implement any rollup updates released. The will often revise them after initial release so it’s best to wait (as with any Microsoft update).
• Wait at least a month to implement any rollup updates released. The will often revise them after initial release so it’s best to wait (as with any Microsoft update).
• Create a group policy for your domains internet settings if the system will be used externally by users. Add the full domain (i.e. *.easiintl.com) to the Trusted Sites Zone and weaken the active X security and allow login using current credentials. **This was the only way to make CRM 3.0 work externally with the Outlook client (and it worked more consistently than IFD too).