This message was deleted.
# citrix-vads
Slackbot
12/07/2023, 12:05 AMThis message was deleted.
s
Scott Knights
12/07/2023, 12:58 AMI have just done this. The procedure I used was:
• Use VEEAM replication to move the delivery controller to the new server
• Configure hosting to the new vcenter
• Use VEEAM replication to move the MCS template
• Delete the MCS machines from the old environment, deleting the accounts in the catalog, but keeping the AD account
• Create a new machine catalog on the new hosting from the MCS template
• Add machines to the catalog re-using the existing AD account
• Add the re-provisioned machines to the delivery group.
• Delete the old machine catalog once it was empty.
I staged the delete/recreate so put one machine into maintenance mode. Deleted it the next day and provisioned its replacement. Repeated each day until all the machines were moved.
Scott Knights
12/07/2023, 1:03 AMIf you don't use VEEAM, just backup and restore your delivery controllers and template instead. Or if you can use shared storage between both vcenters (such as an NFS share) you could storage migrate to the shared storage, remove from old vcenter inventory, add to the new vcentre inventory then storage migrate again to the final storage location. I have used this procedure several times before I started using VEEAM.
r
Ray Davis
12/07/2023, 3:12 AMYea what Scott said works and Cross center vmotion for the infrastructure parts worked well in The past too. For the hosting connection I have used that link you posted, twice to update the UID for the Machine catalogs for pvs and random mcs. You can also migration the golden images over and redeploy random machine easily. You can see my comments in that link years go. For persistent, it’s going to be different as the prov snapshot/provisioning chain is tied to the MC.
I would move the infrastructure parts first and validate all is good. Next I would create a test MC/DG on the old host connection. Then create the new host connection that will have a new UID. Next use the one liner script to update the UID to the for the test machine catalog you created to understand what to expect. Restart the DDC services. Then they should be good. I validated this with random XA and XD machines.
c
Craig Anderson
12/07/2023, 4:02 PMThanks! Sounds fun considering I've got 90+ non-persistent multi-session VDAs & 30+ persistent single-session VDAs.
s
Scott Knights
12/07/2023, 10:51 PMIf you don't care about the hostnames, just spin up a new catalog and reprovision new machines for the non persistent. I just like the hostnames starting from 1. Plus some other software would have needed reconfiguring if using new AD machine accounts.
Scott Knights
12/07/2023, 10:51 PMPlus it was a relatively small environment with not too many VDAs.
r
Ray Davis
12/12/2023, 1:27 PMI have done this many times, if you need help ask questions. I am sure @Scott Knights done this many times too 🙂