You’re offline. This is a read only version of the page.
15
I am migrating a Dynamics CRM 8.2 (Windows 2016 / SQL 2012) to a Dynamics CRM 9.1 (Windows 2019 / SQL 2019). I have following outlined steps to backup the database from the old environment; restore to the new environment; and import the organization.
All that works great if I only use the machine name. I can access new CRM using the server name (https://crm365v9) with a certificate from our internal CA, but it gives a cert warning of course. If I use the FQDN it will not authenticate me.
If I try CRM365v9.domain.com, it will not authenticate me.
The old server (crm365.domain.com) was accessed through the URL https://bcrm.domain.com. "bcrm" was a cname in DNS crm365.domain.com and used a 3rd party certificate. When I change bcrm to point to the new server and add the certificate in IIS, it won't authenticate me. Tried changing brcrm to an A record instead of a Cname. Still no go.
I have check SPNs and I believe those are correct.
Do I need to change Web Address in Deployment Manager? I tried, but it did not help.
I turned on Trace settings, but I am not seeing any files created in the folder specified.
PS C:\Windows\system32> Get-CrmSetting TraceSettings
CallStack : True
Categories : *:Error
Directory : c:\crmdrop\logs
Enabled : True
FileSize : 10
ExtensionData : System.Runtime.Serialization.ExtensionDataObject
Share
Report
All responses (
Answers (
