This message was deleted.

That’s easily doable… First migrate your on prem catalog to the Citrix cloud database. Use the automated configuration tool provided by Citrix to migrate the catalog. And once the catalog and hosting connection are in place follow the normal process of adding machines to the Catalog. DM me in case any specific questions/concerns.

Also I delay the broker agent service when updating the ListOfDdcs, one of many ways to achieve this.

But when the natural gpupdate occurs, it should works right?

From my findings and experience when the gpupdate runs it will update the keys yes. But if the broker agent starts before the keys are updated it won”t register. When this happened to me many years ago, I would look and see the keys pointing to the cloud or another site. But they would show unregistered still. Because the GPO update seemed to be slower than when the start of Citrix desktop service on the vda. Or the service was faster depending on how you look at it. What I do as testing is stop the service update the keys manually the start and it registers. I do this on the unregistered VDa only to test to ensure it will register. So I know it works and can register. Next step I do is delay the citrix desktop service on the VDA so the GPO can do it’s thing first with the keys. You can do this many ways. Here are some ways. 1. Set the service to delay either on the golden image or via GPO 2. Use BISF (GPO setting) 3. Do a schedule task with a script on startup. 3a. Net stop, BrokerAgent reg add HKLM\software\citrix\virtualdesktopagent\ListOfDDCs(example path) net start brokerAgent 4. Use Jeremy Saunders vda scripts. https://www.jhouseconsulting.com/2019/03/04/controlling-the-starting-of-the-citrix-desktop-service-brokeragent-1894