During a recent migration from ConfigMgr 2012 to ConfigMgr 1511, we encountered an issue with the built-in migration utility. While specifying the source hierarchy, we faced a SQL connection error. After some troubleshooting by Ajo Abraham from Microsoft, it was determined that the problem was related to a port connection issue. Because we were using a named instance, the connection needed to go through the SQL Browser service to retrieve the named details. To resolve this, we created an alias for TCP/IP in the SQL client configuration on the destination site server. Once the alias was set up, the connection worked. Note to future self: avoid using named instances for ConfigMgr. Reference details from the lab are below.
Screenshots
0 Comments