Moving SCCM DB to a new server

[Angersma]

Hello - We have moved our SCCM DB to a new SQL server and it is now listening on a custom port.   The old DB still exists on the old server for now, in read only mode.  

Under Site Admin -> Settings -> Deployment we have updated the DB Server name field in the format <servername>,<port #>, and the Test button says everything is fine.  However, it seems the App Portal is still referencing the old SQL server.   When we lookup Apps / Packages on the CI Deployment tab, to associate CIs to CM objects we do not see new objects that were created after the migration.   And we continue to see objects that were deleted from CM since the migration.  

Are there any other places to reference the new SQL server name?  

Thanks-

[CharlesW · Accepted solution]

On the SCCM server where the ESD Web Service is installed, open the web.config in C:\Program Files (x86)\Flexera Software\App Portal Web Service. You will want to update the connection string to the SCCM DB in this file. You will want to recycle the ESDWebService application pool after doing this.  There are no other locations where SCCM DB connection strings are defined, so I think that this should take care of the problem.