Update Manager - never reboots host

[billmathews2013]

We are using Update Manager (on vcenter 5.1). We have a host that has a fresh install of esxi 5.1 (799733). Using Update Manager and applying the Critical Host Patches baseline tells me there are 111 patches available. If I look at the individual patches contained, most say the Impact is "Reboot, Maintenance Mode". However when I run the Remediation, the process only takes about 5 minutes, and never reboots the host. If I run a scan, it tells me no updates are needed. So it appears the patches were applied. However I'm concerned it went so quickly, and never required a reboot. Is this normal behavior. Is there any other way to confirm the patches were applied?.

[vmroyale]

There are only 2 patches available for ESXi 5.1 - you can verify this at http://www.vmware.com/go/downloadpatches

Are you using Fixed or Dynamic Baseline Criteria in the baseline?

[billmathews2013]

Hmm, yes I see your point about the patch list.

However Update Manager shows lots.  I even re-scanned the host first.  I notice that a lot of the Patch IDs are ESX400xxxxx.  These systems were previously esx4, then upgraded to esxi5.1.  So maybe it's still seeing the esx4 environment?

[vmroyale · Accepted solution]

Sounds like the baseline does include old patches. Choose the option to edit the baseline and:

If a fixed baseline is used, remove any non ESXi5 patches from the list.

If a dynamic baseline is used change the product to ESXi5 only.

[billmathews2013]

That did the trick, thanks