CAVD 24.02 CU3 and LAS DR testing

We replicate our Citrix servers to a secondary site. During DR testing, we bring up duplicates of everything in an isolated network. This has worked without issue in the past, but now that we have everything set up correctly with LAS, things have changed.

We assumed we could continue doing this and that license caching (30 days) would allow us to proceed. That did not happen. None of the VDAs would register with the Delivery Controllers.

Based on what I’m reading here:

https://docs.citrix.com/en-us/licensing/current-release/license-activation-service.html#critical-system-dependencies

This aligns with what we experienced during our disaster recovery test. Specifically:

Important: If any of the following system properties change, the existing activation becomes immediately invalid, and you must request a new activation.

Here is my tentative plan for our retest, and I’d appreciate feedback.

Restore the servers in the isolated environment as normal.

Reinstall the Licensing Server service on a different server with a different FQDN to avoid any impact on the production licensing server.

Allow that server outbound access to the LAS Citrix endpoints and register it in citrix.cloud.com.

Update the Delivery Controllers to point to this new license server.

This should satisfy licensing requirements and allow the VDAs to register. Once testing is complete, all servers will be terminated, and the license server entry can be removed from citrix.cloud.com.

My biggest concerns are whether this approach will work and whether the hardware identifier changes on the Delivery Controllers could cause any licensing conflicts with the existing production environment.