Via email came the following problem, “When I do a sysprep customization from a template using the wizard for a Windows 2003 Enterprise virtual machine and power it on, the sysprep part doesn’t apply. When I try to log in, it does load some settings and directly logs me back off again. When I hit “power off” and “power on” in that order, I see how sysprep gets applied during the next boot.”
The process of “sysprepping” a machine is specific to Microsoft Windows servers. The SYStem PREParation utility performs a number of tasks on an “imaged” Widows PC.
One of the main reasons sysprep is necessary is because Windows operating systems contain a number of elements that HAVE to be unique. Specifically, in a domain, every machine should have a unique SID (Security Idenifier).
In Virtual Center, the templates have to be Sysprepped to make sure the machines are unique. Thankfully, most of the mini-setup part can be automated by the use of the Customization Wizard.
However, here’s where we strike the difficulties above!
This is new behaviour in VirtualCenter 2.5. In 2.0 the sysprep launched visibly during the first boot, in 2.5 it happens this new way. Technically, this isn’t a real problem. The solution is as simple as, sysprep, image, deploy and then leave it alone for four or five minutes to allow the sysprep process time to re-configure the new virtual machine.
This is even more apparent with the VDI solution when deploying desktops.