Optimize the boot image updating process
To make your life easier, keep the drives different sizes with the Pv D drive being larger.
For this article, I will use a 10GB Write Cache drive and a 20GB Pv D drive.
Servlet/download/25161-102-648285/XD - Windows 7 Optimization Once the basic VM is built there are four things that need done before joining the VM to the domain. The Write Cache and Pv D drive be different sizes or strange things can happen.
So just forget about doing any of the items usually done by pre creating a Write Cache drive.
The Write Cache drive is always created as Drive D and the Pv D is created with the drive letter assigned during the Wizard.
If not, click No, shutdown the VM, make the change and power the VM on to continue.
Second, a Target Device was created, as shown in Figure 28, with the MAC address of the VM, linked to the v Disk just created and the Target Device is configured to boot from its hard disk because the v Disk is empty right now.
Make sure the new drives are created in the proper storage locations as shown in Figures 7 through 9.
PVS uses the different disk sizes to determine which disk to use for the Write Cache.Ever since the first article in this series came out in January 2014, I have been asked by numerous people to add an article that includes Boot Device Manager (BDM).Since I am here but to serve, I am finally getting around to updating the process to include BDM.My Group Policy with Preferences is linked at the OU that will contain the computer accounts created by the Xen Desktop Setup Wizard.These are the settings in the policy used for this lab.Assumptions: Note: While with BDM, PXE, TFTP and DHCP Options 66 and 67 are not needed, they are needed for the initial running of the PVS Imaging Wizard.