Troubleshooting vDisks

vDisk not booting after promotion

PVS vDisk promotion is an explicit action you can perform as an IT administrator if you need to add updates or patches. This process starts inMaintenancemode. You can move (or promote) this new version to aTestorProductionenvironment. InProduction, all targets have access to this new PVS vDisk version for use during the next PVS vDisk boot.

There are three ways to promote PVS vDisks:

• Maintenance(read/write mode) toTest(read-only mode)
• Maintenance(read/write mode) toProduction(read-only mode)
• TesttoProduction(read/write modes not applicable)

VHD-formatted PVS vDisks can become unbootable after promotion.

The content below provides troubleshooting steps you must perform if the PVS vDisk does not boot after promotion.

1. Create a problem report using the PVS console. You can save the report as a local .zip file.
2. Review the problem report with Support. Examining log messages is a critical step, enabling you to analyze and debug all events leading up to the boot failure.
3. Ensure you understand the PVS vDisk promotion process. IfClean Cache SecretsorKMS Licensingis enabled, the Provisioning server mounts the PVS vDisk locally to perform certain actions.

If the PVS vDisk uses a VHD format and does not boot after promotion, disable cache secret cleanup and KMS licensing support as follows:

1. Open thevDisk Properties窗口,从theGeneraltab, select theCached secrets cleanup disabledcheckbox. Alternatively, clearing theCached secrets cleanup disabledcheckbox enables the cleaning of cached secrets.

2. Select theMicrosoft Volume Licensingtab and setKMStoNone. You can select KMS licensing during PVS vDisk creation. You also can modify KMS licensing for an existing PVS vDisk version. TheGeneralandMicrosoft Volume Licensingtabs allow you to make settings changes that can lead to PVS vDisk boot issues. For example, settingKMStoNonecan prevent the PVS server from modifying the PVS vDisk.

   Collectively, theGeneralandMicrosoft Volume Licensingtabs allow you to modify settings that – contingent upon your selections – can trigger the inability of VHD-formatted PVS vDisks to boot after promotion.

   

   

3. Create a new version of the PVS vDisk and promote toTestorProduction. Next, you must determine if the targets now use this PVS vDisk boot appropriately. To clarify, if you make these changes and the resulting PVS vDisk DOES boot, you have confirmed that you are encountering the bug associated with VHD-formatted PVS vDisks.
4. To resolve boot failure after PVS vDisk promotion, convert your VHD-based PVS vDisk to a .vhdx PVS vDisk format. For more information, see theSupport Knowledge Center.