5 Responses

  1. Gabrie van Zanten
    Gabrie van Zanten at |

    For homelab I can imagine disabling this. For production environments I hope nobody disables this warning.

    Reply
  2. Gabrie van Zanten
    Gabrie van Zanten at |

    Not sure we’re on the same page 🙂 In my book having ESXi shell access and SSH enabled is a big no-no. There are only a few, mostly troubleshooting, situations where you really need this kind of access, everything else is done through vCenter, PowerShell or vMA. So when someone enables SSH or Shell access I want every VMware admin in my group to see this and ask him what he is doing. When working at the shell, it is also easy to forget to disable it again after you’re done. In that case the warning is a nice reminder.

    Enabling SSH as a default would get you fired 🙂

    Reply
  3. davelee212
    davelee212 at |

    I had a situation recently where the services on a host had fallen over and I was unable to connect to the host via the vSphere Client or, strangely, on the console of the machine itself. SSH was the only way in I had to the machine. I’ll be leaving SSH enabled on all my hosts from now on! I see no reason not to – surely you would keep the management network secure and the root passwords set to something strong any so there shouldn’t be an issue with this.

    Reply

Share your point of view!