Vmware ESXi has a behaviour, all admins should be aware of (most probably in the first white paper I could find, it says this information but I do not read them :) ). When you rename a Portgroup for virtual machines, the information will not be updated on the virtual machines. So next time you shutdown and restart the virtual machines, they have no network connection as the connection points to a name which is not existing any more. Before the restart the virtual machines work normally. Windows Server has a very bad behaviour when the network cable is not plugged in: when starting, it is stuck until it gets network. Normally you restart the Server mostly for updates. So it will say forever "Preparing to configure Windows. Do not turn off your computer." / "Konfiguration von Windows wird vorbereitet. Schalten Sie den Computer nicht aus". Now what happens when you need to restart Windows Server because of updates and had the port group renamed? Infinite loop! I spend 3 hours trying to figure what is broken with the updates in the brand new installation of windows server. It did not even let me boot in safe mode (it just reverted the updates and rebooted - also infinite loop). The machine was showing almost 100% cpu usage and small HD activity. So you could assume it was doing something. Only by accident I checked the settings of the virtual machine and saw that the network was disconnected. Conclusion: technically Vmware product is behaving logically. But the Microsoft product behaves completely bad. It should at least put out a warning or give up trying the network (seems to be no time out there).
Posted on: Fri, 16 Aug 2013 21:10:57 +0000
Trending Topics
Recently Viewed Topics
© 2015