Citrix Provisioning - PVS rebalancing loop after changing from BIOS boot to UEFI Boot

book

Article ID: CTX696265

calendar_today

Updated On:

Description

Administrators might notice that when one of the PVS Servers in the site goes down / shutdown, the targets that were streamed from that particular PVS server go in to a loop when trying to rebalance to the other PVS servers in the site. i.e, the number of targets on each remaining PVS server seems to go up and down continuously for a long time. Administrators may also notice that some of the targets are in unresponsive state and did not successfully rebalance to the other servers. This problem affects only the targets that use UEFI Boot and does not affect the targets that use BIOS Boot.

Cause

BIOS reconnects are differentiated and handled differently compared to BIOS boot operations. However UEFI boot and reconnects are not differentiated and are handled in the same way. Treating UEFI reconnects the same as a boot operation limits the number of concurrent reconnections that can be made as per the Maximum devices booting setting. If this value has been reduced from the default value, it can lead to this problem.

Resolution

Adjusting the Maximum devices booting setting (default value 500) to a higher value (if required, depending on the number of targets in the environment) should help to allow more devices to rebalance quickly.

  1. Open PVS Console and connect to the PVS Site
  2. Expand Farm > Sites > Site >Servers node
  3. Right-click the PVS server and select Properties.
  4. Click Advanced button at the bottom and go to Pacing tab.
  5. Adjust the Maximum devices booting slider as per the required number of devices. (Default: 500)

 

image.png

Issue/Introduction

Administrators might notice that when one of the PVS Servers in the site goes down / shutdown, the targets that were streamed from that particular PVS server go in to a loop when trying to rebalance to the other PVS servers in the site. i.e, the number of targets on each remaining PVS server seems to go up and down continuously for a long time before it eventually settles down. Administrators may also notice that some of the targets are in unresponsive state and did not successfully rebalance to the other servers.