OPERATIONAL DEFECT DATABASE
...
...
When attempting to customize the deployment of a virtual machine, the radio buttons are disabled (grayed out) When a virtual machine is deployed from a template, the SID is always the same, despite the fact that you chose the option to generate a new SID during template deployment and guest operating system customization When attempting to create a new virtual machine from a template in vCenter Server, you see the error: Warning: Windows customization resources were not found on this server In the guestcust.log file, you see the error: deploy doesn't contain known sysprep files When you ignore the errors, the virtual machine deployment does not get customized
This article provides information on the process of determining the correct version of Sysprep to use and the correct locations for these files.
This issue occurs if Microsoft's Sysprep files are not found on vCenter Server host or are not in the location they are expected and the Sysprep files are having incorrect version.
For Windows XP, Server 2003, and earlier operating systems, Microsoft has a different version of Sysprep for each release and service pack of Windows. You must use the version of Sysprep specific to the operating system you are deploying. The differences are not immediately visible in the packaging and documentation of the service packs, so it is necessary to manually investigate. Note: For Microsoft Vista, Server 2008, and later operating systems, the System Preparation tools are built into the Windows operating system and do not have to be downloaded or have the version checked. vCenter Server Sysprep Directory locations: vCenter Server DeploymentvCenter_directory_pathVirtual Appliance 5.x and later/etc/vmware-vpx/sysprep/Windows installation of vCenter Server 5.5 and earlier%ALLUSERSPROFILE%\VMware\VMware VirtualCenter\Sysprep which generally translates to C:\ProgramData\VMware\VMware VirtualCenter\Sysprep by default.Windows installation of vCenter Server 6.0 and later%ALLUSERSPROFILE%\Application Data\VMware\VMware VirtualCenter\Sysprep\ which generally translates to C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\Sysprep\ by default. Notes: C:\ProgramData may be a hidden folder.If Sysprep\ directory does not exist by default, you must manually create it. The contents of the Sysprep deploy.cab file must be extracted to the Sysprep Directory on the vCenter Server host. If the file downloaded from the Microsoft Website is a .cab file, use the Installing the Microsoft Sysprep Tools section in the vSphere Virtual Machine Administration guide for details on how to install the Sysprep Tools. If the file downloaded from the Microsoft Website is a .exe file, these additional steps must be executed to extract the files from the .exe: Open a Windows commandprompt. For more information, see Opening a command or shell prompt (1003892).Change to the directory where the .exe file is saved.Enter the name of the .exe file with the /x switch to extract the files. For example: WindowsServer2003-KB926028-v2-x86-ENU.exe /xWhen prompted, choose a directory for the extracted files.Browse the directory and double-click the deploy.cab file. Note: In some cases, the deploy.cab file may be located within one of the subfolders created in Step 3. Select and copy all the files to the Sysprep Directory and insert them into the correct folder. For example, if you are using Windows 2003, insert the files to the Windows 2003 folder found located at directory_path\svr2003. When the contents of the Sysprep deploy.cab file are extracted to the Sysprep Directory on vCenter Server: Log in to the vCenter Server as anAdministrator. Click Start > Programs > Accessories > Windows Explorer. Navigate to the Sysprep Directory as listed in the following table. Right-click on the Sysprep.exe file and choose Properties. Click the Version tab. Record the number at the top, next to File Version. This table lists the Sysprep version for the Windows versions that are supported for Image Customization. Compare the Sysprep version number with the Windows version for which it is intended: Windows VersionSysprep ToolSysprep VersionvCenter Sysprep DirectoryWindows 2000 Server SP4 with Update Rollup 1The updated Deployment Tools are available in the Support\Tools\Deploy.cab file on the Windows 2000 SP4 CD-ROM5.0.2195.2104vcenter_directory_path\2kWindows XP Pro SP2Download at https://support.microsoft.com/en-us/kb/8380805.1.2600.2180vcenter_directory_path\xpWindows XP Pro SP3 5.1.2600.5512vcenter_directory_path\xpWindows XP x64Download at http://www.microsoft.com/en-us/download/details.aspx?id=82875.2.3790.3959 (srv03_sp2_rtm.070216-1710)vcenter_directory_path\xp-64Windows 2003 Server SP1Download at http://www.microsoft.com/en-us/download/details.aspx?id=230965.2.3790.1830 (srv03_sp1_rtm.050324-1447)vcenter_directory_path\svr2003Windows 2003 Server SP2Download at http://www.microsoft.com/en-us/download/details.aspx?id=148305.2.3790.3959 (srv03_sp2_rtm.070216-1710)vcenter_directory_path\svr2003Windows 2003 Server R2Download at http://www.microsoft.com/en-us/download/details.aspx?id=148305.2.3790.3959 (srv03_sp2_rtm.070216-1710)vcenter_directory_path\svr2003Windows 2003 x64Download at http://www.microsoft.com/en-us/download/details.aspx?id=82875.2.3790.3959 (srv03_sp2_rtm.070216-1710)vcenter_directory_path\svr2003-64Windows Vista, Windows Server 2008, and laterSystem Preparation tools are built into the Windows operating system and do not have to be downloaded.Not ApplicableNot Applicable
For more information regarding the installation of SysPrep tools, see the Basic System Administration guide. For more information regarding supported operating systems for virtual image customization, see the Operating System Compatibility for vSphere Client, vCenter Server, and VMware vCenter Update Manager table in the vSphere Compatibility Matrixes . For more information regarding troubleshooting information for template deployment or cloning, see Troubleshooting template deployment or cloning when it fails (1004050) . For more information, see VMware VirtualCenter Templates Usage and Best Practices which provides for best practices on creating templates for vCenter Server . For more information regardingtroubleshooting customization issues with Windows 8 and Windows Server 2012, see Guest OS customization of Windows 8 and Windows Server 2012 may not complete (2037366). For translated versions of this article, see: Portuguese: Local e versões do arquivo Sysprep (2017334) Spanish: Ubicación y versiones de archivos Sysprep (2016847) Opening a command or shell promptTroubleshooting template deployment or cloning when it fails in vCenter ServerSetting up sysprep for use with VMware in Windows Server 2003Ubicación y versiones de archivos SysprepLocal e versões do arquivo SysprepGuest OS customization of Windows 8 and Windows Server 2012 may not completeSysprep 文件位置和版本Sysprep ファイルの場所とバージョン
Click on a version to see all relevant bugs
VMware Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
