Scenario: A Citrix Administrator is in the process of migrating the existing 7.15 LTSR Virtual Delivery Agent (VDA) machines used on premises to Citrix Cloud. The administrator has created a new…

Luis F.Dec 18, 2025

The correct answer is A. When you migrate VDAs from on-premises to Citrix Cloud, the VDA machines need to know where to register, and on-prem VDAs are configured to point to on-prem Delivery Controllers, not Cloud Connectors. If the master image was never updated with the Cloud Connector addresses, the VDAs will keep trying to reach the old controllers and never successfully register in the Cloud environment. Updating the master image to communicate with the Cloud Connectors is the critical step that actually redirects that registration traffic. B is a trap because even with one connector down, you still have the second one available and registration should still work. C is wrong because policy migration affects session behavior and settings, not whether the VDA can register. D is tempting but the question does not say the version is incompatible, and 7.15 LTSR VDAs can register to Cloud as long as they are pointed correctly.

Nina C.Dec 25, 2025

I went back and forth on D because my first instinct was that a 7.15 LTSR VDA is just too old and needs an upgrade, but that is actually not the blocker here, because 7.15 LTSR is supported with Citrix Cloud as long as the VDA knows where to register. The real issue is that the master image still has the old on-premises Delivery Controller addresses baked in, so when those VDA machines boot off that vDisk, they go looking for controllers that are no longer in charge, and they never find the Cloud Connectors at all. Option B tried to trip me up too, since I know you need two Cloud Connectors for high availability, but one being down does not stop registration, the second one handles it. So A is the one, the VDA configuration in that master image has to be updated to point to the Cloud Connectors before anything else will work.

Giselle K.Dec 31, 2025

The Cloud Connector is what brokers registration between the VDA and the Citrix Cloud control plane, so if one of your two connectors is down and the other is overwhelmed or also has issues, your VDAs have nowhere to register. Connector redundancy is designed for failover but it is not a guarantee that registration succeeds when one is unhealthy, especially right after a restart when all your machines are hitting registration simultaneously. I have seen environments where a single degraded connector caused mass registration failures even though the second one was technically up, because the load or the timing knocked it out of the handshake. Before you go tearing apart your master image or worrying about policy migration, pull up Citrix Cloud Director and check the connector health status first, because that is the most likely chokepoint in this specific scenario.