4 Responses

  1. mark gabryjelski
    mark gabryjelski at |

    Funny on the timing of this post, Michael. Just had this conversation with my team, as we prepare for a 300 ESXi server / 6 x vCenter environment upgrade, and added this to the workflow.

    What COULD happen if you don’t reboot? Something as simple as being annoyed during the next use of Update Manager, or as bad as HA not working during a host failure (OK, the latter is me speculating worst case scenario…).

  2. Newsletter: January 25, 2014 | Notes from MWhite

    […] need to reboot your hosts after you upgrade vCenter This is a very good reminder – I learned about it the hard way.  Michael will show you what you need to know to avoid […]

  3. [VMware] news + interesting reads from the blogosphere: 26 Jan. 2015

    […] The Need To Reboot ESXi Hosts After vCenter Upgrade http://longwhiteclouds.com/2015/01/21/the-need-to-reboot-esxi-hosts-after-vcenter-upgrade/ […]

  4. vCoffee Links #13 – Lots of good vStuff!!! » vHersey - VCDX Two to the Seventh Power (#128)

    […] your host and received the message that a reboot is needed @vcdxnz001 explains why in one his post The Need to Reboot ESXi Hosts after vCenter Upgrade. The post includes a link to How to find VMware ESX(i) servers that need a reboot using PowerCLI […]

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.