Accessing Direct Console User Interface (DCUI) from an SSH session (2039638) | VMware KB

For times when you don’t have access to out of band management like  HPE iLO or Dell RAC, but you do have access via SSH. Set your SSH session windows to accommodate the DCUI layout, connect with SSH and launch DCUI with this command: dcui

Source: Accessing Direct Console User Interface (DCUI) from an SSH session (2039638) | VMware KB

VMware announces vSphere 6.5!

Today at VMworld Europe, VMware announced vSphere 6.5. This highly anticipated release promises to deliver on several key features and components that have been in the works for some time. Among the anticipated features are native backup and restore of the vCenter 6.5 appliance, the HTML 5 vSphere Client, native HA for the vCenter 6.5 appliance, Update Manager integrated with the vCenter 6.5 appliance. This release also brings VMotion encryption, VM disk level encryption, vSphere integrated Containers, major enhancements to DRS, dramatic improvements to API and automation capabilities with enhancements to REST APIs and CLI’s as well as improvements to the logs and integrated GUI for Auto Deploy, to name a just a few.
For more information on the vSphere 6.5 announcements visit VMware’s vSphere Blog posts:

Introducing vSphere 6.5
What’s New in vSphere 6.5: vCenter Server
What’s new in vSphere 6.5: Security
What’s New in vSphere 6.5: Host & Resource Management and Operations

The vSphere 6.x product page at VMware.com also highlights the product versions and licensing:

vSphere and vSphere with Operations Management

With VMworld Europe 2016 underway, expect more announcements from VMware.

Attempting to join an Appliance-based Platform Services Controller or vCenter Server to a vSphere domain fails with the error: ERROR_TOO_MANY_NAMES (2114233) | VMware KB

I ran into this issue today. We were deploying a vCenter appliance to a site with an external PSC. In the process we had an issue with name resolution and had to rerun the installation. While the vCenter inventory had been cleaned up by deleting the VCSA vm, the SSO directory still had an entry and needed to be cleaned up before we could successfully deploy the vCenter appliance.

Source: Attempting to join an Appliance-based Platform Services Controller or vCenter Server to a vSphere domain fails with the error: ERROR_TOO_MANY_NAMES (2114233) | VMware KB