VMware: Sysprep file locations and versions (1005593)
- When attempting to customize the deployment of a virtual machine the radio buttons are disabled (greyed out).
- When attempting to create a new virtual machine from a Template in ESX v3.5 you receive the following error message:
Warning: Windows customization resources were not found on this server
The problem is seen when if Micosoft’s sysprep files are not found on the VirtualCenter host, or are not in the location they are expected.
This article guides you through the process of determining the correct version of sysprep to use and the correct locations for these files.
Microsoft has a different version of Sysprep for each release and service pack of Windows. According to Microsoft, "You need to use the version of Sysprep specific to the operating system you are deploying." For more information, see http://www.microsoft.com/technet/community/en-us/management/setupdeply_faq.mspx
Link valid as of May 27, 2008. If you find the link is broken, provide feedback and a VMware employee will update the article as necessary.
The differences are not immediately visible in the packaging and documentation of the service packs, so it is necessary to manually investigate.
This article assumes that you have extracted the contents of the sysprep deploy.cab file to the directory C:\sysprep on the VirtualCenter Server host. You must substitute the actual directory in the instructions below.
- Log in to the VirtualCenter Server as Administrator.
- Click Start > Programs > Accessories > Windows Explorer.
- Navigate to the C:\sysprep directory.
- Right-click on the sysprep.exe file and choose Properties.
- Click the Version tab. Record the number at the top next to "File Version:"
The table below lists the supported versions of Windows for running VirtualCenter server. Compare the version number of sysprep to the version of Windows it is intended for:
Windows Version |
Default Directory |
Sysprep Version |
Windows 2000 Server SP4 with Update Rollup 1 Download at http://www.microsoft.com/downloads/details.aspx?FamilyID=0c4bfb06-2824-4d2b-abc1-0e2223133afb |
C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\sysprep\1.1 |
5.0.2195.2104 |
Windows XP Pro SP2 Download at http://www.microsoft.com/downloads/details.aspx?FamilyId=3E90DC91-AC56-4665-949B-BEDA3080E0F6 |
C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\sysprep\xp |
5.1.2600.2180 |
Windows 2003 Server SP1 Download at http://www.microsoft.com/downloads/details.aspx?familyid=A34EDCF2-EBFD-4F99-BBC4-E93154C332D6 |
C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\sysprep\svr2003 |
5.2.3790.1830 |
Windows 2003 Server SP2 Download at http://www.microsoft.com/downloads/details.aspx?FamilyID=93f20bb1-97aa-4356-8b43-9584b7e72556 |
C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\sysprep\svr2003 |
1.0 |
Windows 2003 Server R2 Download at http://www.microsoft.com/downloads/details.aspx?familyid=A34EDCF2-EBFD-4F99-BBC4-E93154C332D6 |
C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\sysprep\svr2003 |
5.2.3790.1830 |
Windows 2003 x64 |
C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\sysprep\svr2003-64 |
|
Windows XP x64 |
C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\sysprep\xp-64 |
This is not a comprehensive list, it only provides the versions of Microsoft Sysprep for the versions of Windows that are supported for running VMware VirtualCenter Server.
For more information on troubleshooting template deployment or cloning, see Troubleshooting template deployment or cloning when it fails (1004050).
Source: | 1005593 |
With a 2008 R2 server the sysprep location is.
C:\ProgramData\VMware\VMware VirtualCenter\sysprep
Does this mean that vCenter is not supported on Windows 2008 R2? I tried putting the sysprep files in C:\ProgramData\VMware\VMware VirtualCenter\sysprep\xp, but deploying from template with customization didn’t recognize that location.
Correct, vCenter is not supported on Windows 2008 R2, alot of functions won’t work