Scenario: A Citrix Architect is designing a multi-server Provisioning Services solution for CGE. The solution must be highly available and minimize the risk of vDisk inconsistency. What should the…

Configuring separate local vDisk stores with only a daily robocopy script would lead to significant vDisk inconsistency due to the time lag between synchronizations, making it unsuitable for a dynamic, highly available PVS environment.

Configuring separate local vDisk stores on each Provisioning Services server, along with a robust replication mechanism to synchronize them, provides high availability and minimizes inconsistency by ensuring all server copies of a vDisk are up-to-date. This approach allows PVS servers to serve vDisks from local storage for performance, provided synchronization is effective.

Establishing a single vDisk store on a CIFS share on a NAS, which all Provisioning Services servers access, is a standard best practice that inherently ensures vDisk consistency. This centralized approach eliminates the risk of conflicting vDisk versions and provides high availability if the underlying NAS is fault-tolerant.

Creating the Provisioning Services vDisk store on a single DFS namespace provides a highly available path to the vDisk store but is not the storage mechanism itself, nor does it inherently manage vDisk consistency without an underlying shared storage or replication technology.