The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

  • Twitter Updates

    • RT @michaelbolton: 1) Your periodic reminder: a test is not something we *write*. We write text and programs. A test is an experiment you *… 41 minutes ago
    • RT @BiancaPrins: Voor ons allemaal, een #draadje om tot het einde te lezen..... Juist nu (Volgt nog meer in de komende dagen)… 42 minutes ago
    • RT @McKayMSmith: 90) His entire life, Ben has chosen to place his faith in the law. “Law, not war” has been his motto for decades. “I hav… 43 minutes ago
    • RT @McKayMSmith: 82) “It's possible to take the most fundamental, strongly held ideas and change them. What makes people change? Sometimes… 44 minutes ago
    • RT @McKayMSmith: 65) “Now I will tell you something very profound, which I have learned after many years. War makes murderers out of otherw… 46 minutes ago
  • My Flickr Stream

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 1,640 other followers

ESXi 6.5: change the automatic startup/shutdown of guest VMs

Posted by jpluimers on 2019/03/14

One more article about differences between the old C# Windows vSphere Client and “new” vSphere HTML5 Web Client in ESXi 6.5 and up.

This time about changing the startup/shutdown sequence so automatically power on and power off virtual machines.

In the old C# Windows vSphere Client, this was at the host level in the configuration tab under Virtual Machine Startup/Shutdown. There you click on Properties, then adjust the order by moving them up and down (screenshots and more detailed instructions are at ESX(i) AutoStart virtual machines: how to change the VM startup/shutdown settings (via: VMware Communities)).

In the vSphere HTML5 Web Client, there are two bits for this:

On the server you need to enable AutoStart:

From:  to:

For each VM you have to enable AutoStart, then determine the order

  1. In the left, select the VM
  2. In the right, choose Actions, then Autostart, then Enable:
  3. Enable the columns in the VM overview:
  4. Order 1 means highest; adjust accordingly for each VM:

If after boot you get a “Failed – The operation is not allowed in the current state.“, then your machine still is in maintenance mode.


Related: ESXi 6.5: change the host name in the “new” vSphere HTML5 Web Client, or using DHCP option 12 « The Wiert Corner – irregular stream of stuff

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: