Can't deploy new VM from template with vCenter v4

[dnebeker]

I'm new to vCenter, using ESXi v4

I have a template for XP SP2 and XP SP3 created and want to deploy either of them to a new VM. Unfortunately, Guest Cusomization always says "Windows customization resources were not found on the server." vCenter does have a customization pattern in View -> Management -> Customization Specifications Manager, so I'm assuming that 'server' refers to the template machine.

So far I've read many docs, blogs, forum posts, etc about how to do this. I've expanded deploy.cab from the installation discs and copied the contents to:

C:\Documents and Settings\All Users\Application Data\VMWare\VMWare VirtualCenter\sysprep\xp

The files that are in there are:

cvtarea.exe

deploy.chm

factory.exe

oformat.com

readme.txt

ref.chm

setupcl.exe

setupmgr.exe

sysprep.exe

wfinf_guide.doc

Some of the docs also discuss a 1.1 directory under sysprep -- not sure what should go in there or where it should come from.

Has anyone got this to work with XP? From my reading, it seems like that sysprep directory moves around on each release, and I'm not sure if any of the docs I saw were about v4.0, so I'm wondering if they've moved again...

Any help appreciated.

Doug

[VMmatty]

I've got a nearly identical setup and can deploy Windows XP VMs from template using a customization without issue. I have vCenter 4 and ESX 4 (not ESXi) and have the same files in the same location that you specify below.

Here are some thoughts on what to check:

1) Make sure that the Guest OS is configured to Windows XP (32bit of 64bit) and not something else.

2) Make sure you're using the Sysprep files from the correct version of Windows XP that you want to deploy.

[dnebeker]

@VMmatty

Thanks for the input. The sysprep files came from the support/tools directory on the installation CD, so I'm assuming they are correct. And OS type is Windows XP (32-bit).

Do you have a sysprep\1.1 directory? Do you actually have to run anything on the XP machine before turning it into a template (ie run sysprep or anything else)?

Doug

[VMmatty]

One more stupid question. What operating system are you using for vCenter 4? Windows 2003 or 2008?

[VMmatty]

I do have a 1.1 directory under the Sysprep folder (in my VirtualCenter directory) but it is empty.

You don't have to run anything on the XP virtual machine before turning it into a template. You should just have to place the files in the correct location on the vCenter server and then create a new customization specification.

I would try deleting and recreating the customization specification from scratch and seeing if that helps. Have you tried that already?

[dnebeker]

vCenter 4 is running on Windows 2008.

What do you mean about placing files on the vCenter server -- isn't the sysprep directory on the XP machine??? Maybe THAT'S where I've gone wrong. Off to try it...

[VMmatty]

Those Sysprep files need to be placed on the vCenter server, not the VM itself.

Also, with Windows 2008 the location is slightly different. It will be c:\Users\All Users\VMware, but that folder isn't visible by default. If you just type that into a run line it should bring you to the right place.

[dnebeker]

AH HA!

Now that I think about it's pretty obvious (was wondering why you'd ever have multiple sysprep directories). You put the files on the vCenter server.

Note: The path is actually controlled by the ALLUSERSPROFILE environment variable. That means on Win2008 the actual path is:

C:\ProgramData\VMware\VMware VirtualCenter\sysprep

Thanks for your help

[VMmatty]

That path or the path I listed above will get you to the correct location. Either way, glad you got it working!

[dnebeker]

OK, one more question

I'm using an already activated Windows XP as the base. When it started, it was asking for the license key (I didn't enter one in the Customization profile). Also tried entering the license key in the profile, but now XP comes up and wants to activate. I'm hoping to create a bunch of these for some testing and was hoping to not have to login to any of the machines once created from the template (basically just want to start them up and let them sit there and idle).

Is there any way to do this without having to manually go to each machine (and in this case activate)?

Thanks

[VMmatty]

I think the issue is the license of XP that you're using. OEM and MSDN/TechNet keys need activation when you clone them. A volume license key shouldn't need to be activated. Someone can correct me if I'm wrong.

What kind of key do you have?