Scenario 1: Basic Troubleshooting
To resolve this issue, complete the following procedure:
- Shutdown all target devices streaming the vDisk.
- Refresh the console.
- If any target devices still show as connected to the vDisk, mark them down from the PVS console.
- Right click the vdisk and choose manage locks.
- Making sure all device are selected click Remove Locks.
- Check the console on any other PVS servers in the farm and ensure that they do not show the vdisk as locked.
Scenario 2: Core Troubleshooting
As a fix , remove everyone that is still connected and running using that vDisk. So there is an outage involved in this procedure for users using that image.
1. Users that are still connected should save their work and log off. This is going to be a complete outage for anyone that uses that particular image.
2. Go to your DDC and put the Desktop Group in maintenance mode. This will prevent the DDC from attempting to start up VMs and potentially lock up the vDisk while working on it. Then Force Shutdown on all the VMs. Verify in hypervisor console they are all shutdown.
3. RDP to a single PVS server and in the PVS Console, go to the Store and right click on your vDisk. Verify there is no gold lock next to the vDisk. If there is clear all the locks. Then click “Unassign from Selected Devices(s)…”
4. Make sure all your VMs are checked and click Unassign
5. If you have maintenance versions, you should preferably merge them at this point. Use the “Merged Base – Last base + all updates from that base” option so you get a nice single .vhd file.
6. Once you have verified you have a single .vhd file you can rename it if you want. Copy that .vhd file and the associated .pvp file to all your other PVS stores. Get all your PVS servers in sync and check the replication status. They should all have blue dots:
7. Now go back to your Store view and right click on your vDisk. You should now see an option to Delete. Click it.
8. MAKE SURE you DO NOT check the Delete the associated VHD files check box. Just click “Yes” only. All it does is delete it from the PVS database. It will not touch anything in your Store this way. Do this on all your PVS servers.
9. Now right click on “Store” and click “Add or Import Existing vDisk…”
10. Click Search to search your Store for vDisks. Only check that new .vhd you had created in step 5 and 6 above. Then click Add once it stops being grayed out.
11. It will be imported in Private mode every time. Go ahead and switch it to Standard mode. Also do check the Cache type, Enable Active Directory machine account password management, and KMS on the Microsoft Volume Licensing tab because all that will likely not carry over for you.
12. Now go to your Device Collection. In this example, we have 20+ Devices that need this particular vDisk golden image. We are not going to modify each one. So we will set the vDisk on the first VM only.
13. Now right click that VM you just set and click “Copy Device Properties…”
14. Hit “Clear All”, then check “vDisk Assignment” only, then hit Copy.
15. Now just highlight all your other VMs, right click in the highlighted area, and click Paste. Instantly all your VMs will be assigned that vDisk.
16. Now boot up a couple of VMs and verify the “Vdisk is locked. 0xffff8017” error is gone. Then disable Maintenance mode on your DDC and you’re back in business.
17. You can delete all those old .vhd, .avhd, and .pvp files from old versions of your image if you like or archive them somewhere.
