Scenario: A Citrix Engineer added a second Provisioning Services server to an existing Provisioning Services site for high availability. The engineer copied the virtual hard drive (VHD) files to the store on the new Provisioning Services server. After doing that, the second server stopped showing the disk as 'available' under replication status. Why is vDisk replication status failing for the new server?

Question

Accepted Answer

A. The .pvp file has NOT been copied The .pvp file (vDisk Properties file) stores the properties and settings associated with a vDisk, and it must accompany the .vhd file in the store. Without the .pvp file, the Provisioning Services server cannot read the disk metadata and therefore marks the disk as unavailable under replication status.

Answer

B. The vDisk is still in Standard mode. Standard image mode is a valid operational mode for vDisks shared across multiple servers and does not cause a replication status failure.

Answer

C. The manifest file has NOT been created. Manifest files are relevant to versioned vDisk chains, not to the base availability of a vDisk on a newly added server.

Answer

D. The disk has to be replicated through DFSR. DFSR is one optional method for synchronizing vDisk files between servers, but manual copying is fully supported - the root cause here is the missing .pvp file, not the replication method used.

Scenario: A Citrix Engineer added a second Provisioning Services server to an existing Provisioning Services site for high availability. The engineer copied the virtual hard drive (VHD) files to the…

Question

Options

How the community answered

Why each option

Topics

Community Discussion