I have a Server 2016 PVS Machine catalog called PRDCVAD2k16 with 100 machines added from a PVS Device collection called PRDCVAD2K16 the target devices use the PRDCVAD2K16 PVS Vdisk. I am testing a new Server 2022 image with a new 2022 machine catalog called PRDCVAD2K22 with 5 machines added from a PVS Device collection called PRDCVAD2K22 the target devices use the PRDCVAD2K22 PVS Vdisk. Eventually i need to cut over all the PVS Target devices from the PRDCVAD2k16 catalog to the new PRDCVAD2K22 Vdisk and i am just thinking of the best way to acheieve this without downtime. I tested removing a machine from the PRDCVAD2k16 catalog and then moved the PVS target device from the PRDCVAD2K16 device collection to the PRDCVAD2K22 device collection in PVS and assigned the PRDCVAD2k22 Vdisk to the target device . I then ran the Export devices wizard in PVS choosing the new PRDCVAD2K22 device collection and was successfully able to add it the new PRDCVAD2k22 machine catalog and add it to the existing DG. This method seems pretty long winded so was thinking of alternatives ?? Can i rename the existing PRDCVAD2k16 Device collection to PRDCVAD2k22 in PVS and then rename the machine catalog to PRDCVAD2k22 and then assign the PRDCVAD2k22 Vdisk to the device collection ?

You can't rename those catalogs if they were created by the PVS wizard. I would just make new machines in a new Machine Catalog, then add them to the Delivery Group as you remove old ones from, it.

Historic as i wasnt here but i am pretty sure the targets was created using the PVS streamed VM setup wizard (Not the PVS Citrix Virtual Desktops Setup wizard (PVS didnt create the machine catalog) This means they was added manually from Studio on prem where you create a machine catalog and choose Citrix provisioning and connect to your PVS server and choose the device collection and it adds the devices from the device collection.

How many can you stand up? You might be able to do 5 at a time. Luckily the creation and deletion process of machines that are pvs are pretty quick. We had to do this for an environment to also swing their 2022 image to EFI, as the previous PVS image was BIOS.