Hello everyone, Has anyone here already performed an in-place upgrade from Citrix CVAD / PVS 2507 LTSC to 2607 LTSC and can share their experience? We encountered a serious issue after the upgrade: vDisks in Standard Mode boot without any problems Golden Images / vDisks in Private Image Mode no longer boot = ERROR 4: No servers available for disk The problem occurred immediately after the upgrade Before the upgrade, the environment was working flawlessly under 2507 LTSC This is an existing farm that was updated via an in-place upgrade. So far, we’ve run various tests but haven’t been able to identify the cause. It’s notable that only Private Image Mode is affected, while normal streaming in Standard Mode continues to work flawlessly. Has anyone observed similar behavior after switching to PVS 2607 LTSC? I’d be particularly interested in the following points: Did you successfully perform an in-place upgrade from 2507 to 2607? Does Private Image Mode still work without any issues? Were there any special adjustments or workarounds required after the upgrade? Do you use BIOS or UEFI boot? I’d be very grateful for any tips or feedback. Thank you very much!

Hi Mark, you use multiple PVS servers? What does the load balancing say? Is it one the server you expect it would be? Also check: These keys located on your PVS Stream Servers under the following path:

HKLM\SOFTWARE\Citrix\ProvisioningServices\StreamProcess

•

SkipRIMSForPrivate

(REG_DWORD) ◦ Value:

1

◦ What it does: Normally, the PVS Stream Process ensures a vDisk is fully replicated across all PVS servers in the site before letting a target device boot. When a vDisk is actively locked in Private Image mode, it is only booted by a single target device and often resides on only one server. Setting this to

1

prevents replication synchronization errors (

"No servers available for disk"

) when booting that specific disk.

Hi Ray, thx 4 Info.... We've already set the Reg entry in our PVS infrastructure since the PVS farm was created. It has no effect. The load balancer looks fine. This situation is pretty unpleasant.

So you image is at server 1 and load balancing only points to server 1 for that disk? Also…when setting the registry setting you need to restart the steam process

Yes, the disk is on PVS 01. I've already tried several disks, including completely new ones for testing.... Standard boot works with all images. As soon as I switch to private mode, I get error 4. I suspect there's an error here with Inplace 2507 to 2607..... I've already created a completely new, blank disk and set up a new machine with a new MAC address and assignment. Same error.

Only cert related issues I seen with pvs were related to the new secure boot certificates