Customization fails after VC 2.5 Upgrade

A few people have notice that since upgrading to Virtualcenter 2.5 deploying a Windows 2003 VM from template no longer gives them the ability to customize.  The option is disabled.

The fix for this is simple.  You need to grab the new deployment tools from Microsoft’s site here also referred to as the sysprep files. You will be downloading WindowsServer2003-KB892778-SP1-DeployTools-x86-ENU.cab

This file needs to be extracted on the Virtualcenter server and placed in the following folder-

C:\Documents and Settings\All Users\Application Data\Vmware\VirtualCenter\sysprep\svr2003

Once these files exist in the correct folder, you will be able to deploy your W2K3 template.

For more details read the Virtual Center 2 Template Usages and Best Practices http://www.vmware.com/pdf/vc_2_templates_usage_best_practices_wp.pdf

Virtual Center VMwarewolf June 4th. 2008, 1:30pm

5 Responses to “Customization fails after VC 2.5 Upgrade”

  1. Customization fails after VC 2.5 Upgrade | Savage Nomads Says:
    June 6th, 2008 at 9:34 pm

    [...] Customization fails after VC 2.5 Upgrade [...]

  2. Virtualization Short Take #10 - blog.scottlowe.org - The weblog of an IT pro specializing in virtualization, storage, and servers Says:
    June 17th, 2008 at 11:03 pm

    [...] Blythe aka VMwareWolf posted an article about VM customization failing after VC 2.5 upgrade. Fortunately, the fix is easy; just download and install the correct version of the Sysprep tools [...]

  3. Customization fails after VC 2.5 Upgrade « Bjansema’s Weblog Says:
    June 18th, 2008 at 8:58 am

    [...] door bjansema A few people have notice that since upgrading to Virtualcenter 2.5 deploying a Windows 2003 VM from template no longer gives them the ability to customize.  The option is [...]

  4. Customization fails after VC 2.5 Upgrade « Hyper Info Says:
    June 23rd, 2008 at 2:12 am

    [...] few people have notice that since upgrading to Virtualcenter 2.5 deploying a Windows 2003 VM from template no longer gives them the ability to customize.  The option is [...]

  5. Deployed or cloned VM base disk will point to template’s or original VM’s vmdk if "Edit Virtual Hardware" is used to modify it | vmwarenews.de Says:
    February 5th, 2009 at 8:27 am

    [...] Customization fails after VC 2.5 Upgrade A few people have notice that since upgrading to Virtualcenter 2.5 deploying… [...]