 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
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.
How to Sysprep a VM (template) for vWorkspace to use