Whats the currently valid procedure to add a PVS-based machine catalog on-prem to Studio / WebStudio? As the native option was removed and the successor is not really usable atm - how should the catalogs be created? Only way is "power managed machines", "Other service technology" which results in "User data: On local disk" instead of "User data: discard". Any other option?

Use the pvs based virtual apps and desktops setup wizard

You can register the PVS servers within the PVS configuration wizard and use the Web Studio to configure and add PVS based machine catalogs. https://docs.citrix.com/en-us/provisioning/current-release/configure/citrix-provisioning-catalog-in-studio

You can use the export wizard to copy target to a cloud based studio

@Dennis have you tried that? i did and its awful 😉 Cannot understand why they removed the legacy method while this isnt really usable in production. Thanks @James Kindon, I will test the old school pvs wizard.

Tbh, I never tried that. We use our own Powershell script to create the machines. We mostly use XenServer with local storage (no pool) and after that I use the export wizard. We have a template on every Xen host and all hosts are defined in the hosting configuration.

The future will be towards the PVS by MCS wizard style setup, today it's fine to create a collection, but that is all it does - it will improve over the time and add more into the mix, people have been wanting PVS provisioning and management in Studio forever and a day, it will take a while, but it's happening

No question about that. The new solution is pretty cool and I cant wait to manage all centrally in studio. However I dont understand why the old way was dumped before the new way had feature parity. Also there is a massive lack of documentaion imho. When provisioned by studio will studio update the machine account password? Or will pvs server still do?

I think it was due to the move towards web studio being the new world, and studio on it's way out, and getting parity of process between on-prem CVAD and DaaS deployments - there is probably more technical depth than that, but that was my understanding of the changes PVS will still manage the lifecycle of the AD account today

Still decommissioning a working feature when there is no parity with the new one is not the smartest move but that that's what you get with the latest CR which Marco is or?

FWIW - the old method was actually deprecated back in 2019 when the CVAD Setup Wizard was added -- this was necessary for DaaS users because the DaaS studio running in the cloud could not communicate with the PVS server. At that time we added the CVAD Setup Wizard to replace that and that remains available today. The "old" studio method was only left in place to support folks running 7.15 PVS (which doesn't have the CVAD Setup Wizard) and was never implemented in webstudio since it couldn't work in DaaS. The new Webstudio based provisioning is available via the GUI for VMWare and via powershell for VMWare and XenServer (as of 2407CR) with more features being added in every release. As to AD account management -- with Studio/MCS based provisioning of PVS targets, we are adopting the same identity management as regular MCS VDAs (so an Identity Disk, with computer accounts managed via that) -- this is actually a great benefit because it also brings along all the other identity features previously only available with MCS (like Hybrid AAD, Pure AAD, non-domain joined, Citrix Service Continuity, etc). So the PVS server is no longer involved in AD account management and you use the regular support in studio (like Identity Pools).

@Simon Graham thanks for this information.