I ran into an issue recently where DRS was failing to move some VMs between 1 of 3 hosts.
To test the compatibility states I manually attempted a vMotion of one of the affected VMs to each host to see what the recommendations would say in the vCenter Web Client. In this case one of the hosts was failing to provide the following CPU instructions:
While we were upgrading one of our VCSA 6.5 vCenter appliances to 6.5 Update 1, I ran into an error Stage failed when trying to check for updates within the port 5480 admin interface.
Since migrating to the new Photon OS based vCenter 6.5 VCSA Appliance, we’ve had issues with alerts not being sent to email.
As it turns out, there’s a problem with the internal configuration not being updated properly. VMware is aware of it and should hopefully fix it at some stage.
For now you can follow the workaround below.
One of the more powerful features that VMware has added to several product lines lately has been vSphere tags. As time has gone on support for these tags has been added to other products beyond just vSphere vCenter such as vRealize Operations and PowerCLI cmdlets. I still see engineers ask why someone would use tags instead of the older school custom attributes, so I figured I’d show how we use them in my job.
We utilize tags in two specific ways. The first is to use the tags to filter groups of VMs for PowerCLI reporting. In our case we have tags created for each Engineering team so we can customize these reports only for the virtual guests that they have access to.
The second use for these vSphere tags is to filter objects in vRealize Operations for dashboards, policies, alerts, etc. Eventually reports from vRealize Operations may even replace the PowerCLI reports since most of the properties and metrics are already collected from vCenter.
define | broken 