Solved!
Go to SolutionHow to Sysprep a VM (template) for vWorkspace to use
Hi Guys,
I thougth this would be the easiest part of setting up our vWorkspace environment, but apparently not!
What i'm trying to do: setup a VMWare template that vWorkspace uses as a template for creating VMs.
What I do:
1) create a win7 VM in vmware.
2) log in, run Sysprep choosing OOBE and Generalise, and shutdown
3) convert the VM into a template
4) on the vWorkspace console i try and "add computers...", choosing the above template, create a fairly benign unattend.xml using the vWorkspace interface (i don't import).
5) tell vWorkspace to create the VM
6) VMWare creates the vm, boots it up, and then it just goes to the first screen of the OOBE - asking for my name.
Am i doing something wrong? i thought at this point vWorkspace should inject the unattend.xml and customise everything? if there's something i haven't explained in detail enuogh please let me know.
Thanks!
Nick.
The sysprep function of OOBE is working. I.E. Once you boot the VM up after the provisioning of the VM you are presented with the OOBE UI. What seems to not be happening is the customisation by vWorkspace: Timezone, Domain joining and hostname setting.
vWorkspace verison is : 7.2.303.461
vCenter version is : 4.1.0
Nick.
Dell-Matt-E
57 Posts
1482
0
Posted October 11th, 2011 04:00
Is Sysprep running at all and just not joining the domain?
Also, which version of vWorkspace and vCenter are you using?
Dell-Matt-E
57 Posts
1483
0
Posted October 11th, 2011 04:00
On the domain configuration in sysprep are you using FQDN or Netbios?
Dell-Matt-E
57 Posts
1483
1
Posted October 11th, 2011 05:00
Could you log a case with support? I am travelling and not sure what else I can really suggest.
Following your original steps I don't believe you need to do step 2. I have never done this step.
ok, tried that. it doesn't fail (deosn't leave me at the OOBE screen obviously - there was no sysprep'ing), but when i log into the VM and check the hostname, it's still the original pre-template hostname, so the vWorkspace customisation process isn't taking.
Is there somewhere i can find logs to see what's going on?
Dell-Matt-E
57 Posts
1480
0
Posted October 11th, 2011 06:00
No, as we will kick off sysprep by configuring the sysprep setting through our wizard when provisioning new VMs
rmack1
1 Rookie
•
48 Posts
2122
1
Posted October 11th, 2011 08:00
Hi Nick,
The vWorkspace sysprep needs pntools manually installed on the template so that the connection broker can copy the sysprep files to the target VM. If pntools isn't installed the VM will just sit there after power-up.
Provided VMware tools are installed as well (which they should be) you can find out if the sysprep has worked by looking at the VM summary (in VI Client console) to see if the hostname/domainname has changed.
regards,
Rick