I'm in the middle of replacing DDCs in a 2402 LTSR CU3 site as part of retiring Server 2016. Everything is working fine following the removal of the Server 2016 DDCs except for Web Studio (this includes connection brokering, MCS, Director, StoreFront, NetScaler, MMC Studio). The Server 2016 DDCs were cleanly removed from the site via Web Studio. For Web Studio, which runs on its own server that is co-located with Director, I have ran

StudioConfig.exe --server "<http://newddc1.domain.com|newddc1.domain.com>,<http://newddc2.domain.com|newddc2.domain.com>"

and confirmed that

C:\Program Files\Citrix\Web Studio\Site\assets\json\manifest.json

contains only the new DDCs. The output of

StudioConfig.exe --showserver

is also correct. If I add one of the Server 2016 DDCs back to the site, I can log into the site through Web Studio again. I've found that the

MultiSiteSettings

entry in the

[OrchestrationSchema].[AdminPreference]

table of the Site database only contains the old DDCs. I do have a secondary site defined, but even if I remove the secondary site the DDC count for the primary site never changes and the value in the database is never updated to reflect the new DDCs for the primary site.

[{"DisplayName":"PrimarySite","DeliveryControllers":["<http://oldddc1.domain.com|oldddc1.domain.com>","<http://oldddc2.domain.com|oldddc2.domain.com>"],"Default":true},{"DisplayName":"SecondarySite","DeliveryControllers":["<http://secondarysiteddc1.domain.com|secondarysiteddc1.domain.com>","<http://secondarysiteddc2.domain.com|secondarysiteddc2.domain.com>"],"Default":false}]

Before I update this value manually in the database, has anyone else run across this?