Im just wondering if anyone has any tips or tricks for Deploying Win7 via vWorkspace (mainly around the sysprep/unatended.xml file)
I have a Win7 client which is the basis for our main campus deployment, but I want to deploy it via vWorkspace to allow our remote users to test/evaluate it.
Basically im looking at deploying Windows 7 to my vWorkspace setup to allow staff and students to trial it ahead of a full deployment at the college - but we are using Microsoft MDT 2010 as our deployment solution, and thsi generates its own XML file, so I was wondering if there were ay best practice, etc and will the unatended.xml file that vworkspace lets you create will be sufficient?
Not sure what your deployment scenario is but I posted a blog on that might help you. I have not updated it to include the Optimizer that David referenced but you can insert that into the template creation process. Hope this helps you in some way.
I have converted by test Win7 Client into a VM using the vCenter Converter, then I ran the optimizer and then tried to create a VM from the template.
I get the following error;
I wonder if its because my "C:\Program Files\Quest Software\vWorkspace\Sysprep" folder on my broker only has the following folders; Win2K3 Win2K3x64 WinXP WinXPx64 Am I missing something for Win7
svanbent1
13 Posts
996
1
Posted November 23rd, 2011 11:00
If not mistaken installing update 1 for 4.0 does give full windows 7 support. if this is installed then you should not be getting that error.