Yep, it should work the way you intend. What I would do though is make sure to scan the hosts against that baseline first. Then when you do the remediate, it will say what patches it will install so you can uncheck any extras.
-----Original Message----- From: Michael Leone [mailto:[email protected]] Sent: Friday, February 05, 2010 3:34 PM To: NT System Admin Issues Subject: OT: VMware remediation Sorry for all the OTs. I've finally got my VMware Update Manager installed and working. My problem before was with the SQL user I had created for the VUM DB. Once I used the "sa" login, like I did for vCenter, it all Just Worked. So what I want is to upgrade my ESX hosts from Update 4 to 5. I want all 10 to be at Update 5, then I'll install all the fixes since that major update release. So what I did was create a new baseline, that filter out everything except Update 5, and attached that to all my ESX servers. The instructions are a bit confusing to me - I want to remediate *just* that new baseline, so all that happens is the Update 5 upgrade. (I want to do this in stages, obviously) When I go to remediate each ESX server, can I choose just that new baseline I created, as the source of the remediation? Even if there are multiple baselines attached? (I have the standard baselines also attached, for when I do the post-Update 5 patches). Since I have HA and DRS enabled, the remediation should migrate off all my VMs; upgrade my ESX server; reboot it (if necessary); and put VMs back on. I think. Or do I have to manuualy put the ESX servers in maintenance mode, first? Sorry for the nervous newbie question. But when it comes to updating VMware .. .well, I *am* a nervous newbie. :-) Thanks for any help ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
