This post explains the steps you could take to remove a VSAN-enabled host from a VSAN cluster without putting it into maintenance mode. You could also use this method to remove an VSAN-less ESXi host from a cluster without putting it into maintenance mode.
Alot has been going on in my head about how I should transform my homelab from a simple physical box with just plain vSphere 5.5 on it and memory consuming applications like Microsoft Exchange and Lync to a nested ESXi environment where I can test new VMware features and technologies apposed to the Microsoft technologies I have seen for many years now.
Some time ago, I replaced the SSL certificates in our test environment with the SSL Certificate Automation Tool. Everything went well, but some of the applications we were using or evaluating stopped working. This post will hopefully help you prevent applications to stop working after you replace the certificates in your environments.
I have spent time solving an issue with host profiles on several environments running on vSphere 5.1 and HP BL460c G6 blades, to be specific. These blades have two local SAS drives in a RAID-1 configuration. This logical drive is used for installing ESXi and provides in a VMFS datastore.
Some days ago a HP SUM firmware upgrade of our HP BladeSystem enclosures and bladeservers caused a problem inside the iLO user database. The enclosure lost it’s SSO session with the blades, making it impossible to login to the iLO.