Greetings, all. I've got this interesting case from a CVAD on-prem customer who had a failed 1912 to 2203 CU7 upgrade. Following the upgrade, StoreFront fails to enumerate against the 2203 CU7 upgraded controllers, but does work on the EOL 1912 DDCs. Their SQL DB is a bit of a mess following the upgrade, via the related PS commands, you can see 5 different schemas as set (1912 base, 1912 CU3, 2203 CU7, etc) Citrix support took forever to pick up this case, and is recommending roll back to snapshots and SQL DBs that 1 month old. To me, the SQL DBs are tainted and rolling back to 1 month old data via snapshot doesn't seem wise. we should be doing a parallel build, they've got only around 30 users, less than 10 VDAs, so we could migrate policies and other relevant settings where we can via Powershell to a new set of DDCs/site and keep the semi broken one up as a reference point. This customer is new for us, and it's possible that there were other failed attempts, for instance from 1912 base to 2203 CU3 prior to attempting it on 2203 CU7, maybe even they don't know what ISOs they downloaded & ran. What is your own vote? Try to troubleshoot the SQL mess as is, or parallel net new site build & migration of working settings?

Migrate. Get it to a known good base.

In my own lab, two controllers that started their life net new on 2511 (7.46.100) are nice and clean for the same set of related tests, for those reading, here's the reference KB https://support.citrix.com/support-home/kbsearch/article?articleNumber=CTX238581

Use the ACT and migrate to new site

Thank you for your feedback. We're on the same page, build new / build right

For 30 users and 10 VDAs i would just build from scratch and not even try to migrate. I net the VDAs are also an old OS given the state of the current infrastructure.