Tech musings and testings
I have put this function together for the purpose of documenting cluster settings. Used it a fair bit to gather information on environments that I have come accross that have not been well documented. In can be used as is but I’m fiddling around with it to produce some further information so likely to be updated in the near future. Hopefully of some use – connect to vCenter from POWERCLI and run the function. get-clusterdetails
I’ve recently had to audit and document several vSphere environments. Multiple hosts had been configured manually and there were some mistakes in the IP settings. I put together this POWERCLI function to report back on these settings and will now use it for documentation moving forward. Hopefully of some use to others too. Connect to a host or vCenter and give it a go.
As part of a security hardening exercise or indeed just because, it may be desirable to change the root account of your ESXi hosts to a complex password, bung it in a safe and let you admins connect via their AD credentials. To start with, join your ESXi hosts to your AD domain. I have pre-created computer objects in my test environment. I have also created an ESX Admins AD security group which by default allows its members admin access to an ESXi host once it has been joined to the domain. To join the domain run the following powercli...
I don’t know many people that enjoy writing documentation but it is a nessesary evil and can give you the opportunity to be creative with how you produce it. Often I will need to document a point in time install for ESXi hosts so have put together the below PowerCLI function to obtain some hardware and build information back. Running Get-HostDetails after connecting to a host or vCenter There are loads of good examples available but this works well for me. Output as below
In previous versions of vSphere it has been necessary to run CLI commands or edit host config to remove parent VMs (for instant clones) before shutting down a cluster. This is not required in ESXi 6.7 so the process has become a little easier. Here is a bare bones process that I use to cleanly shut down then startup a vSAN cluster running instant clones (tested with Horizon 7.7/ESXi 6.7 u1). In this instance, the vCenter appliance is also running on the cluster so this will add some extra steps to the process. **I have also included a few powercli...
