I am attaching the PVS POC guide from Citrix. I will now test with a v4 machine.Ģ) The vdisk seems to keep the exclusive lock on the disk when all machines have been shutdown.ģ) The shutdown machines show as stopped and not as de-allocated which means it is costing us money. I have to hard shutdown the machine to get it back. Provisioning Services creates a version (VHDX) and places that version in Maintenance mode (read/write). ![]() I will move the target device to a v4 machine and test again.Īdditionally on the v5 target device I have found the following so far:ġ) When the vDisk is in private mode and I hit restart after adding to the image, it does not reboot cleanly and stays on a black screen in boot diagnostics in Azure. The vDisk update process starts either automatically (scheduled), or when an administrator right-clicks on a managed vDisk, then selects the Run update now menu option. I have just read the post by Aran Walker on the PVS blue screening, which is one the of the issues I have been suffering with as well. ![]() I have a D2s v5 as the target VDI, with no accelerated networking. In the Deployment method field, select VDI onboarding scripts for non-persistent endpoints. I am utilising a D4s v4 for the PVS server (2112) with accelerated networking. In the navigation pane, select Settings > Endpoints > Device management > Onboarding. Is anyone successfully using PVS in Azure with users working on it in a prod environment?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |