There are a lot of automation tools available which are able to deploy and configure an ESX host but if you want to use PowerCLI for the finishing configuration part there was always a manual step involved. I’ve found a way to start a PowerShell script from the service console trough SSH. The only thing you have to do is install WinSSHD on one of your Windows servers, just execute the distributable that you downloaded from the Bitvise website and follow the process. As soon as the installer completes, you will have a working WinSSHD installation on your machine. No changes to the default configuration are necessary; you only need to start it. However, you might want restrict your users' access to those features that they actually need, which will improve security. If you are new to WinSSHD, it’s highly recommended that you first make sure that you can establish a working SSH connection before you change any settings on the server. If you cannot connect to WinSSHD using its default configuration, this is most likely due to a network or firewall problem that you will need to resolve before you are able to connect. In its default configuration, WinSSHD accepts connections on the well-known port number for SSH servers, 22.
I’ve recorded a Jing video (with audio) which demos the CPU-Ready PowerCLI script running on my vCenter server launched from one of my ESX host’s service console.
Monday, March 22. 2010
How to access PowerCLI trough SSH
If you’re looking for a free SSH daemon, you might want to check out freeSSHd, like it's name says, is a free implementation of an SSH server. It provides strong encryption and authentication over insecure networks like Internet. Users can open remote console or even access their remote files thanks to buit-in SFTP server.
