vCenter 4.1 Update 1 "Additional Guest Operating System Customization Support"

[vmproteau]

I was reading the release notes for vCenter 4.1 Update 1. I noticed this statement with respect to additional customization support:

"Additional Guest Operating System Customization Support: vCenter Server now supports customization of the following guest operating systems: Windows Server 2008 R2 SP1 (x32 and x64) "

(1) Does this mean that we shouldn't patch our Windows 2008 R2 template with SP1 if we are still using vCenter 4.1 (without Update 1)?

(2) Also, it's possible that someone has already patched our Windows 2008 R2 template with SP1. What would be the consequences or potential issues if some VMs have already been deployed and customized in vCenter 4.1 (without Update 1)?

I doubt I will see any error, warning, or other if I tried to customize but, I want to make sure that there isn't some underlying issue that wouldn't be readily noticeable.

[MauroBonder]

you tried create a customization specification in vcenter ?! windows 7, vista and 2008 dont use sysprep, i test use customization to deploy vm with win7 and works fine.

see also http://kb.vmware.com/kb/1005593     

[vmproteau]

Not sure what you mean sysprep is still used for those OS types but, it is handled differently natively. So, although you don't need to put sysprep files out on the vCenter server, the guest is still getting "syspreped".

[AndreTheGiant · Accepted solution]

The reason is simple... SP1 is in RTM and will be released next weeks.

First version of vCenter 4.1 cannot support it only because was not existing.

Does not support does not mean that is does not work (sorry for the word game).

Andre

[vmproteau]

Yes...I suppose I was reading too much into it. I just didn't recall updates to customization support announced for various Service Pack releases.