Customization fails after VC 2.5 Upgrade
I’m going to upgrade my Virtual Center next week, this is a really good tip to keep handy.
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-
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
This post brought to you by: VMwarewolf
Customization fails after VC 2.5 Upgrade
vmwarewolf
Wed, 04 Jun 2008 17:30:02 GMT
More Stories
Security URL scanners
As the internet continues to evolve, so do the threats that come with it. One of the most common threats...
Security tools bookmarks
As I'm learning about different security tools and solutions, I keep adding to my bookmarks for follow-up. Today, I'm sharing...
Collection of build numbers
I feel like I'm always looking for an applications history of builds. Sometimes its for windows 10 others for different...
Using Automation to Create Optimized Windows Images for VMware Horizon VMs
https://twitter.com/jesperalberts/status/1410859089001914368?s=21 Automate your horizon view desktop build
VMware horizon view with shared GPU
One of my projects this year is to research and test using hardware GPU in our horizon view environment. Vmware...
Using vmware horizon view with Microsoft Azure MFA
We are looking to move from Duo to Azure MFA to standardize our security and reduce cost. I found the...
One thought on “Customization fails after VC 2.5 Upgrade”