I assume you have seen this. PVS Servers have alot of RAM so the snapshot is probably better dont when the server is shut down. https://docs.citrix.com/en-us/provisioning/current-release/upgrade.html

A few weeks ago our network engineers had some trouble upgrading cisco switches. They had to revert the change but we're still having trouble with booting the pvs targets in one datacenter. At first it's fine but after several boots targer get a timeout with the tftp boot and the connecting to the Provisioning server. Resetting the stream service sometimes helps. Anybody experienced this before? Working with 2507.1 and vmware vsphere 8.

anyone seeing azure vm's routinely slow booting in azure? like you'll get the hyper-v screen and it just takes forever... so long that they never register

Since upgrading to PVS 2507CU1 from 2402 CU3 i cant see any of my templates on Xenserver when running the PVS CVAD Setup wizard anyone come across this ? I initially also had an error connecting to Citrix cloud via the PVS CVAD Setup wizard and had to uninstall/reinstall latest Citrix DAAS powershell sdk to fix

Has anyone ran into an issue with PVS 2402 CU3 upgrade where it says unable to communicate with license server? In the log I see this: Status message: ErrorCheckLsCompatibility [LASClient.cs(682): CheckLSVersion] I have LAS enabled on the license server AND I have legacy licenses too. Any chance CU3 does not like LAS enabled during ugrade?

i powered off and converted exisiting Bios PVS target device VM's to uefi on xenserver using xe vm-list name-label= and xe vm-param-set uuid=xxxxx HVM-boot-params:firmware=uefi and then attached the uefibdm.iso to the CD rom and assigned the UEFI converted Vdisk to the target device and then powered them on. They all boot fine but the CD rom drive letter has changed to G:\ which has caused an issue as we have a network drive that maps as G:\. During testing i did test newly created target devices using XD setup wizard using a new uefi template VM and tested migrating existing VM's from Bios to UEFI using the above commands and I did see this issue on the newly freshly created UEFI target devices. Because of this issue I booted the converted UEFI Vdisk into R/W mode on one of the newly created maintenace uefi target devices and manually changed the drive letter of the CDROM in diskmanagement from G:\ to B:\. The updated vdisk was then applied to the newly created UEFI target devices and no issues the drives map with the correct drive letters. I have then converted the remaining bios target devices from bios to uefi using the above xenserver commands and assigned the updated uefi vdisk with the correct drive mappings and experienced issues with the CDROM drive letter which i am finding confusing as the converted UEFI vdisk has the CDROM set as B:\ and works on the newely created UEFI machines using the XD ssetup wizard. Any idea ? anyone seen this behaviour?

Has anyone seen any issues with 2511 and VDA's retaining the identity of the maintenance VDA? The process we are following is: Create new version (Server 2019 vdisk) > boot maintenance VDA > upgrade VDA to 2511, upgrade TD to 2511 > seal with BISF + CTXO > promote to Test > boot test VDA. Connect to the test VDA and the GPO's from the maintenance VDA are applying, looking in GPRESULT and its showing as if its still the maintenance VDA.

@Barry Browne has left the channel

Is this support matrix this specific? We are running pvs 2503.1 and it is registering ok with LAS but this seems to indicate we need to be on 2507 LTSR for compatibility. https://docs.citrix.com/en-us/licensing/current-release/license-activation-service

Anyone using the vdisk replicator utility to sync PVS vdisks/versions from one site to another sep site? The last few months we've been noticing that the utility sometimes won't copy files to the destination. We may have to run the utility a few times for it to work. Also, sometimes if it does copy the files, it won't actually import the vdisk, or add the actual 'version' in the PVS console. We are on 2507.1

Hey Steve its connecting to the remote servers to run the robocopy scripts is it maybe failing to connect sometimes? Mine works fine on 2507.1. Only working sometimes really implies something environmental changing between runs. Maybe antivirus?

@James Lee joined #citrix-provisioning. They’re also new to World of EUC.

After all PVS targets are UEFI booted, do you change the boot file name? From C:\ProgramData\Citrix\Provisioning Services\Tftpboot\ARDBP32.BIN to C:\ProgramData\Citrix\Provisioning Services\Tftpboot\PvsNbpX64.efi

Hello everyone, we’re seeing a strange issue with Server 2019 + PVS (VDA 2507 CU1 / Target Device 2507 CU1): VMs register fine in the Machine Catalog. As soon as they’re member of a Delivery Group → stuck on “Initializing” / Unregistered. Output from Get-BrokerMachine attached as picture. What’s odd: • Same setup with Server 2025 works fine • Issue is reproducible even with a clean 2019 install • Every boot shows “Getting devices ready” (not just first boot) ◦ Sysprep state is OK Looks like devices are re-initialized on every boot, so the VDA never becomes ready. Anyone seen this with 2019 + PVS? It has worked fine until we deleted all devices and recreated them because we had to rebuild the PVS Accelerator Cache on XenServer.

PVS template on XenServer is set to boot only from network and wc disk size 30 GB. But when the targets are deployed using Citrix Virtual Desktop Setup Wizard, the target device have all boot options enabled (DVD-drive, Hard disk and network). Manually creating machine from PVS template doesn't do this, it creates an exact copy. Also, the wc cache disk size shows as 32 GB in the wizard and also after creation. Does PVS add the RAM cache (2GB) + WC disk size (30GB) when creating WC disk?

Hi Guys, we we recently bombarded by Security Team asking to implement a number of small things. Now they are asking for another bunch to be implemented on Windows Server 2022 Citrix CVAD, running on Nutanix AHV as PVS targets booting from BDM iso. Could you tell if you were successful in implementing any of these or found enough evidence that something is not supported or doesn’t work well? Bitlocker vTPM Secure boot VBS Code Integrity Credential guard Remote Credential guard from what I found som far: Bitlocker: Not supported on PVS targets. https://docs.citrix.com/en-us/provisioning/2206/manage/managing-target-device.html https://support.citrix.com/support-home/kbsearch/article?articleNumber=CTX331016 vTPM: Not clear. Surely you could create a VM with vTPM, but I couldn’t find a process where PVS target situation is mentioned. So we have VM running PVS target and currently configured without vTPM and we want to end up with vTPM attached a properly functioning. Secure boot: Supported. However I ended up with a blue screen after enbling secure boot on a target VM. Potentially missing some steps. Haven’t found info on how to to it properly for PVS target. Also I couldn’t see much value in this one for PVS. https://docs.citrix.com/en-us/provisioning/current-release/configure/configure-UEFI.html https://docs.citrix.com/en-us/citrix-virtual-apps-desktops/install-configure/security-policies/secure-boot.html VBS: Not clear There was a dedicated option for Vsphere VMs for this. For AHV seems to work differently. Code Integrity: Not clear Not sure if that works for PVS / AHV combo. This could be enabled via GPO once VBS is enabled. Known for causing performance issues. Like massive ones. Crazy IOPS and CPU for hours. we had a number of cases with Microsoft for this on persistent VDI. Credential guard: Not clear I could see there is an option on AHV VMs. but not sure if that works for PVS targets. And if that works how reliable is that. some comments here abotu VM density and Virtual Trusted Platform Modules (vTPM) to store MS policies is not supported. https://portal.nutanix.com/page/documents/details?targetId=AHV-Admin-Guide-v10_3:ahv-windows-defender-credential-guard-support-c.html#nconcept_x14_k3z_rnb__section_dbd_yyw_rbc Remote Credential guard: Supported. Seems to be just a gpo settings “Restrict delegation of credentials” and has nothing to do with PVS or AHV

@Patrick Brörken has left the channel

PVS 2507 on XenServer - Target devices on same VLAN as PVS server are working fine. However, target devices on different VLAN are slow to boot and stuck at this screen forever. WC is set to Cache on RAM with overflow to disk. DHCP options 11, 66 and 67 are set on the non-PVS VLAN.

This is driving me up a wall. Built a new S19 Platform layer, compiled the image (App Layering), and the target device refuses to grab an IP and boot. No ghost NICs, the one NIC is a vmxnet 3, etc. What am I missing here?

Vmeate has been changing nic pci slot number. I would check that

Hey Folks, there is a known issue with PVS and CU2604, SecureBoot doesn't work after, it's related to MS certs. Citrix support says to upgrade to PVS 2601, I am on PVS 2402 LTSR. 1. With PVS, is there really a security benefit to use it? VBS can run without it. Still it was working, it's a pity to lose it. 2. Being told to upgrade to CR 2601 when supposedly LTSR is in support (I run a LTSR env so I am losing my entitlement by updating PVS), it sounds like limited support and if there is a bug they can't fix, you're told to upgrade, pretty bad if you ask me. It doesn't sound right to me in the way LTSR is supposed to be supported. Do I expect too much? I want to push back but I want the community opinion first. Cheers !

Getting the attached error when deploying target machines on XenServer pool. I am not sure why PVS tries to make connection to XenServer host IP address instead of FQDN, we have wildcard cert on all XenServer hosts issued by Internal CA and it is approved by all domain joined computers. We have already deployed 160 devices to the same pool, getting error when trying to add more. Host connection test is successful from Studio and from PVS console.

Getting this warning message after every reboot.

i am provisioning m6id-4xl instances in aws with MCS. I am having issues with the disk not initializing, this all the logs, pagefile etc, are problematic. Any suggests on what to do/try? I've set the master image up with the same SKU. For this particular instance, the OS is 2019, but we also have 2022/2025

After creating a MCS-Provisioned machine catalog for PVS Machines (Win11 on XenServer) docs.citrix.com/en-us/…/create-hybrid-joined-catalogs.html#… the Write Cache Disk is assigned Drive Letter E: I assume the MCS creation process can't handle the BDM Disk and MCS Identity Disk on IDs 0 and 1 Any Ideas how to make it D again?

-WriteBackCacheDriveLetter

from

New-ProvScheme

only accepts E ore higher.

We migrated Citrix workloads from VMWare to XenServer. We have 900 PVS target machines and 15 MCS machines. MCS machines on initial boot gets DHCP IP and it works, after few days MCS machines loses IP and gets an APIPA address. PVS targets on the same pool and same DHCP VLAN working fine. We are not sure where the issue. Whether MCS handles DHCP lease renewals differently?

I'm struggling with time issues in a new W11 25H2 master on ESX. The master is built via an SCCM TS, and when finished both the time zone and time is correct. I take a snapshot of the VM and then updated the MCS catalog with that snapshot. Any device provisioned boots up 4 hours ahead of time, even though it's still in the correct time zone. Anyone ever run into this before?

anyone know why these are not displaying correctly ? within citrix Cloud monitor / PVS 2507CU1 on prem

anyone got the free control up disk monitor tool they could send me? Troubleshooting a PVS write cache filling up and used procmon (Create new file operations / c:\ path but seen control up do a disk monitor tool as well that looks decent

If you are using Proxmox with PVS, the 302 virtio drivers crashes out during the disk copy process. If you install JUST the 302 network drivers, then you can capture the image. After that capture you can install the rest of the 302 package.