Template Windows 2008 R2, Do we need Sysprep with vCenter

[Wajeeh]

Dear All,

In order to have vm template for Win 2008 R2, I created a standard config. VM and then converted it to template. Now when deploying a new machine from it, I am using a customization answer file which I also created myself. I am able to get a new VM, but I am still not clear if running a sysprep setup is needed in this case OR not, like it was the case of Win 2003 , sysprep files were required to be added to be added to vCenter server to change SID's.

Please assist, there is much discussion available when I searched but I didn't find something convincing, Some people mentioning after creating required standard VM and before converting to template manually RUN sysprep and select 'shutdown' choice, some saying in Win 2008 R2, this step is not needed and if you are using customization wizard, the resulting machine will have its SID change.

For example, while I read on this link:

http://www.vmadmin.co.uk/resources/36-virtualcenter/114-sysprepdeploytemplate

it says customization choices will be grayed out if sysprep files not found on vCenter server, but this is not the case with me, because I am using third choice 'customize using and existing customization specification', this link in the end also tells as 'Note: Windows Server 2008, Windows Server 2008 R2, Windows Vista and Windows 7 use a new method for imaging which does not require sysprep files on the vCenter server.'

Waiting for response.

Thanks,

[rcporto]

For Windows Server 2008 and above the sysprep are already present in default installation (default folder: %windir%\system32\sysprep), then the note about "does not require sysprep files on the vCenter server" tells you that you don't need copy sysprep files to vCenter Server, but run the sysprep on Windows clones still are a recommendation from Microsoft.

[admin]

As Richardson described, there is no need for Sysprep files on the vCenter Server. Windows 2003 servers did require Sysprep tools on the vCenter Server itself as the sysprep files were not included during OS installation. They were available on the Windows 2003 installation media. From Windows 2008 and until 2012 R2, the sysprep tools are included the OS when installed. This will probably also be the case for future Windows Server OS'.

The customization wizard will do it's job without you manually run the Sysprep command before you shutdown the machine and convert it to a template, so my advice is - dont run the command within the OS before converting.

You can use your custom sysprep answer file with the guest customization wizard. Just hit the checkbox with Generate new SID to ensure that the virtual machine that you are deploying generates a new SID.

\Ibrar

[Wajeeh]

Hello All,

I looked today in vCenter %allusersprofile%\VMware VirtualCenter\Sysprep and found there was no folder for Win 2008 R2 as also described by Richardson, it is inside the OS by default for case of Win 2008 R2.

Later I created two VM's using , deploy VM from template and "customize using existing customization specification" and I saw in events customization process started for both machines.

When completed I ran psGetSID on the two and found that SID is different on both. I am attaching here with, Now I think it is not required at all to rum sysprep in Windows ?

Please share thoughts.

thanks,

[admin · Accepted solution]

Yes, this is the expected result when using a Customization Specification - and there is a checkmark in Generate new SID.

When you use VMware vCenter Customization Specifications for Windows machines, it uses sysprep. Thats why you dont need to manually run sysprep inside the virtual machine.

It is basicly the same as running sysprep.exe /generalize.

\Ibrar