Boot vDisk Maintenance Versions to Specific Server

[Eric Hendricks]

Is there a way to force vDisk maintenance versions to boot to a specific server in a load-balanced environment?

 

This has become an issue in our environment, since we have an evenly load-balanced PVS farm. When trying to boot/update more than one maintenance VM to a maintenance version of a vDisk, the second VM will often attempt to boot to a secondary server due to the *.avhdx file for the new version only residing on the primary update server. We of course want production level connections to be load-balanced across all PVS servers where the vDisk files have been properly replicated, but for maintenance and updates, this is frustrating to deal with.

[Robert Young1709152714]

16 hours ago, Eric Hendricks said:

Is there a way to force vDisk maintenance versions to boot to a specific server in a load-balanced environment?

 

This has become an issue in our environment, since we have an evenly load-balanced PVS farm. When trying to boot/update more than one maintenance VM to a maintenance version of a vDisk, the second VM will often attempt to boot to a secondary server due to the *.avhdx file for the new version only residing on the primary update server. We of course want production level connections to be load-balanced across all PVS servers where the vDisk files have been properly replicated, but for maintenance and updates, this is frustrating to deal with.

 

Hi Eric, 

 

I think this is where the SkipRimsforPrivate registry key comes into play. Worth a test, but the stream service needs a restart so perhaps do it out of production time. 

https://discussions.citrix.com/topic/347079-provisioning-services-no-servers-available-for-disks-in-maintenance-mode/page/2/

 

 

[Robert Young1709152714]

I also just looked up some more recent cases and perhaps SkipRimsForPrivate is no longer needed in newer versions. Perhaps someone who knows more will comment here if they see this. 

The case I looked at states that the RIMS service is the one that decides where the vdisk version is present and decides the streaming server so if SkipRims is set then load balancing only applies and the steam will pick the least loaded server. 

So perhaps you have the SkipRimsforPRivate key already from an older version or previous troubleshooting ?