Windows 8: %windir%\system32\sysprep\sysprep.exe /generalize /oobe /shutdown /mode:vm Windows 7: %windir%\system32\sysprep\sysprep.exe /generalize /oobe /shutdown You can also run the following command line: Within the Windows 7 virtual machine, launch sysprep located in: %windir%\system32\sysprep\sysprep.exe Once the checkpoint is created and renamed, we can run sysprep.
It is also a good practice to rename the checkpoint to a name which references the update made. Prior to running sysprep, let’s create a new checkpoint for the virtual machine so we have a checkpoint to come back to when we are ready to make our next update to the image. Once I have completed the update of Microsoft Office and made all of my changes, we will need to run Sysprep again.
For this example, I am updating the Microsoft Office application to the latest version. Once the virtual machine is started, you can login and make your change(s) to the image. Within the Hyper-V console, revert to the correct checkpoint. This was done so I can easily revert the virtual machine back to a normal state prior to when I ran sys-prep. As a good practice measure, I created a checkpoint of the virtual machine prior to running sysprep. Part of the process needed when we created our collection was to run sysprep on our master image. This was created from our master virtual machine called Win7master. To recap our environment, we have a Windows 7 pooled desktop collection available to our users. Now let’s take a look at the steps needed in making a change or update to our image and making it available to users. In part II we saw how to deploy and publish a Windows 7 pooled virtual desktop. Applies to: Windows Server 20 R2 Part III
0 kommentar(er)
