Heads-up: Citrix DB migration per CTX280675 — don't forget the VDA Update Service (VuS) When moving the Citrix databases to a new SQL server, every service (Connection String) has to be repointed individually. The VDA Update Service (VdaUpdateService, cmdlet prefix Vus) is easy to miss because CTX280675 doesn't list it and was never updated afterwards— the article covers 16 Set-*DBConnection commands, and Set-VusDBConnection isn't one of them. Symptom: Studio (both Web Studio and the MMC console) fails to start on all Delivery Controllers with an error along the lines of "Could not find a working 'VDA Update' service." Running sessions and VDA registrations are unaffected. Fix: Run Set-VusDBConnection on every DDC. How we found it: After completing all CTX280675 tasks, neither Studio would open, while desktop logons and active sessions kept working. We asked the DBA team to bring the old SQL server back up — Studio worked again within seconds. On the old server we could see both DDCs still writing to the site DB:

sql

SELECT spid, loginame, hostname, program_name, DB_NAME(dbid) AS DatabaseName

FROM  sys.sysprocesses

WHERE program_name LIKE 'Citrix%';

There was a successor article, CTX558936, but it has been unavailable for some time as well. We still have the PowerShell script Citrix shipped with it — VuS isn't in there either, so that article would have had the same gap. Two gaps to watch for if you follow CTX280675: 1. Missing service — add Set-VusDBConnection as described above. 2. Wrong order — old SQL server shut down too early. Step 3 says to shut down the old SQL server, but the connection strings are only cleared in step 7. That asks the services to release a connection to a server that no longer exists. Set-*DBConnection ... -DBConnection $null -Force then fails with Citrix.XDPowerShell.Status.DatabaseError, and Set-LogSite -State Disabled throws a NullReferenceException because the logging service can no longer read its site object. Correct order: keep the old SQL server online until all connections on all DDCs have been cleared and repointed to the new server. Only then shut it down.