CRM 2016 and SharePoint Quick Tips
I recently had to integrate CRM 2016 On-Premise with SharePoint On-Premise, and it was not as easy as I would of liked it.
Remember to :
- If you use a SSL certificate it must be at least 2048 bit in order to work between CRM and SharePoint
- When you connect more than one Microsoft Dynamics CRM organization to a single SharePoint server, the name you give the STS must be unique for each Microsoft Dynamics CRM organization.
- Connecting to more than one Microsoft Dynamics CRM organization to a single SharePoint server is only supported with SharePoint 2016.
- Create snapshots in your VM as you go along.. I had to rollback from time to time
- You would need at least Windows Server 2012 R2 to be able to run SharePoint 2016
- You can get away with host header binding in IIS, alternative mapping in SharePoint and DNS entries in the host file
- I like to use powershell where I can and normally start of by setting the execution policy Set-ExecutionPolicy -ExecutionPolicy Unrestricted
- I recommend renaming a new VM before you promote it to a domain controller. You can rename the VM name using Rename-Computer -NewName CRM powershell snippit
- You can create a self signed certificate using the New-SelfSignedCertificate PowerShell command or by using SelfSSL in the IIS 6.0 Resource Kit Tools
- You can enable .Net 3.5 feature using Install-WindowsFeature Net-Framework-Core powershell
- When generating a certificate, it is better to generate a wildcard certificate than a domain specific
- Follow the SharePoint CRM integration guide https://technet.microsoft.com/en-us/library/dn949332.aspx
Here’s a few pointer. Good luck