Hello, I see that PVS 2402 is no more compatible with BIOS. Our VDA are in BIOS configurated in VMWARE. Should we recreate all our VDA in UEFI mode ? Should we recreate new master ? Is the PVS server not compatible or can I upgrade PVS Server and let Target Device in 2203 to test ? Thanks 🙂

Does someone already have a W11 24H2 Template for Citrix Optimizer Tool? I see there is a new one for Server 2025 with the latest version (3.4.0.1) but no specific one for latest w11 build

From @Rob Zylowski LinkedIn post, vDisk replicator can now be found here - https://community.citrix.com/citrix-community-articles/vdisk-replication-utility-r650/#_=_

👍 Thanks Jarian should have thought of that

Ran into a new issue today. We had a client moving their citrix licenses to a new license server. Done this dozens of times in the past. DDC licenses moved no problem. However PVS licensing popped the device doesn't have a license message. When we moved it back it was fine. Can we no longer change the PVS licensing server without a device reboot? Is there a command I can run on the PVS target device to have it re-allocate without rebooting all the target devices? These are 24x7 locations, so booting 1000s of VMs will cause some downtime and messages.

Hi is there any way to automatically monitor the % of the PVS cache disk usage across the Citrix VDI desktops, without e.g. SCCM? We currently have 15gb cache disks.

Hello, Could there be some problems when upgrading Active Directory Forest and Domain functionnal level from 2012 to 2016 when we have a Citrix farm 2203 CU1 with PVS on WinSRV 2019/2022 ? For me normaly not but I prefer ask 🙂 Thanks

I am provisioning pvs servers through studio in azure. its working pretty decent but i am running into one irritating thing so far. in the process you must define the write cache disk size. what happens is we use a d16ds_v5 which contains a temporary 600gb disk for a few different reasons. Bis-f does its thing and moves the w/c to the d drive (600gb temp) as it should. However, there is still a 32gb disk (e:\) from provisioning process. Question is, how can I get around that additional drive creation?

So continuing to troubleshoot the Web Studio created PVS machines. The PVS image is deployed to Azure via IPS, and that works great for the PVS console created machines. But Web studio machines will only do server side caching. I made a copy of the latest image in Azure. Opened it in Read/Write, closed it. And made it Standard. And it properly cached to ram fallback to disk. Switched back to the original non-opened disk, and it went back to server side. So it looks like something in the IPS deployment process might not be making it work correctly until you manually open and close it.

Does anyone have any advice for me on how to correctly activate minidumps on a PVS target to find the cause of a BSOD? I have configured the following settings via registry. The GUI throws a warning when confirming the settings. I suspect it has to do with the pagefile as we only have one pagefile on D:\ (via BIS-F) and not on C:\

I am reverse imaging a PVS vdisk in Xenserver to upgrade the Xentools. I got a merged base and created a MM Vdisk version and booted a MM target device and detached the Write cache disk and added a larger HDD 250GB and brought it online (MBR) then run P2PVS using "Citrix PVS Vdisk to this machine" option which completed successfully. I then shut it down and changed boot order to HDD and it boots up but gets stuck on a black screen and doesnt move off this. I done 3 other PVS Vdisks exact same method and didnt have any issues so not sure what is going on. Any ideas ?

Does anyone here use ReFS for the PVS store? I usually format the disk with NTFS and 64 KB allocation size.

for PVS provisioned by MCS vda's in Azure - can the actual w/c disk (the azure managed disk) be destroyed/reset at reboot/shutdown of the system? ideally the managed disk wouldnt hang around

Is it possible to have a pair of PVS servers steam vdisks to 2 different subnets, while the PVS servers are in a 3rd subnet?

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 ?

Hi all! Worked with PVS since it was release but never faced a subnet change of the PVS servers. In this setup someone decided to split the targets and PVS servers (HA) into different subnets. They are facing some retries and I want to move the servers to the same net where the targets reside. My plan is to move the load to PVS server 1 and then change configuration on number 2, including bootstrap. Then move the load back to the newly configured server 2 and then do the same config on 1. BUT is this possible during production, will the targets get the new IP configuration of the PVS servers on the fly or is it necessary with a reboot to get the correct information from in this case the ardbp32.bin file?

Interesting that PVS 2503 documentation came out, but no software.

It is there now. https://docs.citrix.com/en-us/provisioning/current-release

Doh my bad.

Looks like 2402LTSR CU2 supports server 2025 now, for both Server side and Target Device Side. https://docs.citrix.com/en-us/provisioning/2402-ltsr/system-requirements I also noticed they removed some verbiage around the SQL version support. However, https://support.citrix.com/s/article/CTX114501-supported-databases-for-virtual-apps-and-desktops-and-citrix-provisioning-pvs?language=en_US still shows 2402LTSR for PVS supports SQL Server 2017, 2019, 2022.

Been a long time since i last dropped a Vdisk on a Device collection (I want to swap out the existing Vdisk assigned to all target devices in the collection to a new Vdisk ) i am 99% certain it doesnt impact powered on target devices in the collection and they will continue to work and pick up the new vdisk at next reboot but my arse is twitching a little so best make sure

You know your week's going to be rough when you're troubleshooting a boot issue on a new image and realize that you forgot to install the PVS target device software...

Hello, what's the best way to update VMWARE Tools on a PVS Image ? Without rebuilding all the image. Do you have some tips ? Thanks

Has anyone seen this error after upgrading to 2402 CU2? VDAs are booting without any issue. TFTP is loadbalanced via Netscaler.

Has anyone enabled ReFS deduplication on their PVS servers vhdx volume storage? I know that the block cloning works on our primary server, as it reports more free space than others, but thinking about deduping the other PVS servers as well to more efficiently cache data in RAM.

Does anyone have an idea what could be causing the Virtual Apps and Desktops Setup Wizard wizard to fail but not generate a log? (XenDesktopSetupWizard.log) It only fails when creating BDM machines, PXE works fine. The VM is created without a cache disk (vSphere), but no AD Object and no machine in Studio.

Is there a sizing recommendation for WC Disk? Based on concurrent user count, weekly/daily reboot schedules

Server 2025 master image is blue screening post install if MS April cumulative update. This is PVS 2411 in Azure. Anyone else see this happening?

Does anyone have a writeup about why the WEM agent is being installed with the PVS Server Component? Noticed this on 2411 and 2503.

Avoid PVS Target Device 2402 CU2 No group policies are being applied at all. We first noticed this issue due to a missing time redirection policy. Error in the eventlog is attached. Support cases have been opened and can be referenced: 83282716 83261124 Session Manager "This session will be disconnected due to a policy evaluation error" - Page 2 - XenDesktop 7.x - Citrix Community