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 in PVS to PRDCVAD2k22 and then rename the machine catalog to PRDCVAD2k22 and then assign the PRDCVAD2k22 Vdisk to the device collection ?

hey m8 - renaming shouldnt be a problem to do. you can also copy the vdisk assignment property from a 2022 target device and then paste it onto the 2016 servers in the console to quickly reassign the vdisks, reboot. might have to reassign/rename your dg's.

Hey m8 hope all good ? - Yeah think renaming is the easiest method as i just dont fancy removing machines from the old 2k16 catalog / moving them to new device collection in PVS / run export devices wizard in PVS to add them to the new 2k22 catalog / add them to the existing DG. Yeah i did have a thought about the DG as when you add a machine to a DG you choose the name of the DG from where to add machines from and if the name of the machine catalog changes from 2k16 to 2k22 i did wonder if the machines would need to be re added from the new catalog name (Same catalog but renamed) ....

Is this for desktops or published apps? Normally you could just add machines from the new catalog to your delivery group and remove ones from the old.

Server OS Published apps. I havent got the capacity to run the new machines side by side with old if i did as you say creating a new machine catalog and removing old machines from DG and adding new machines from new catalog would be easy

You could do it one at a time. Remove old add new and swap

yeah thats the first method i mentioned in my post remove machine from Prod DG / Remove from 2K16 catalog / Move it the 2K22 PVS device collection / Assign 2k22 Vdisk / Run Export device wizard and add the device to the 2k22 catalog from the 2k22 device collection/ add to DG (This could be a problem due to one prod DG) / Rinse repeat for rest of machines. The problem is we use local storage and each host (22 in total) has its own hosting connection so this process would be combersome as would have to run the PVS Export device wizard multiple times

I'm a big fan of tags, I have all my prod in 1 machine catalog and use tag for different workload, W16/W22, pub desktop against the tag, different AD group. Job's done.

yeah use tags and application groups with restrict launches to specific tags all the time. Just this enviroment that doesnt use any