In his article, Dwayne talks about vCenter Update Manager 4.1, and the fact that it seems to be the last version of the tools that will allow you to patch your Windows and Linux guests:
VMware vCenter Update Manager Features. vCenter Update Manager 4.1 and its subesquent update releases are the last releases to support scanning and remediation of patches for Windows and Linux guest operating systems and applications running inside a virtual machine. The ability to perform virtual machine operations such as upgrade of VMware Tools and virtual machine hardware will continue to be supported and enhanced. [VMware vSphere 4.1 release notes](http://www.vmware.com/support/vsphere4/doc/vsp_esx41_vc41_rel_notes.html#featureplatformnotice)
Dwayne talks about this as being a bad thing, and that’s where I disagree. I have never understood why VMware saw it as their job to patch the operating systems the guests are running, and I have yet to see anyone actually use this feature. Obviously I was wrong, someone does indeed use it, but I really can’t understand why.
I’m a keen believer in doing what you know, and doing it well. Let «native» patching solutions take care of the guests, Windows Server Update Services (WSUS) comes to mind, and leave vCenter Update Manager (VUM) to take care of patching your VMware products.
I wouldn’t mind seeing vCenter Update Manager (VUM) extended into patching the VMware Workstation, Fusion and Player installations your enterprise might have, but I really think that losing the fat that is guest OS patching can only be a good thing.