Plain Virtualization

Today marks the release of the next iteration of vSphere. Most changes are the improvement of existing features and that includes what is embedded together with ESXi which is vSAN . First, vCenter Appliance will support Single Sign On domain with embedded PSC with Hybrid Linked mode. During this release, support for the upgrade with older vCenter Server with External PSC will not be possible at release. External PSC setup is still supported. There is a Hybrid Linked Mode which will support on prem vCenter Server 6.7 with VMware Cloud on AWS vCenter Server 6.5. Lastly, this is also the last release support for vCenter Windows Server as mentioned in the last release . There will be a backup tool and can be scheduled to help manage vCenter recovery process. In terms of migration to vCSA, the migration tool allows asynchronize background process to reduce the amount of downtime. The HTML5 Client (Clarity UI) has not feature priority up to 95%, up from version 6.5. Yo...

With the release announcement of vSphere 6.7 it comes with his in-kernel vSAN 6.7 upgraded together. With the big move to HTML5 client (Clarity UI), vSAN 6.7 will support Clarity and with much of its functions and management done in Clarity. That definitely better than using vSphere Web Client. Together with this release, a new assessment tool for HCI is introduced. This will work not just on vSphere but also Hyper-V and physical server. The best part is that this assessment tool is free. The long awaited support for WFSC is not possible with iSCSI target. Bigger improvement on destaging and data placement and failure handling. Check out the post here .

Recently I got asked how many characters can a VM name character support and any special character can be used? Been doing vSphere since version 3.x, it has never encountered to me there was a limit in that space. Having said that, there is a case where a customer would need this. Example, to have the VM name similar to the FQDN especially true in a multi-domain or tenant environment where VM name could be the same and only the domain or tenant is the differentiator. So doing a quick check here is the below KBs that state the limit: As of vCenter Server 4.1, the number of characters for a VM name is 80. KB Display names for any objects e.g. VM Name, Datastore Name, etc. should not contain special characters like %, &, *, $, #, @, !, \, /, :, *, ?, ", <, >, |, ;, ' etc are contained in names of vSphere entities such as virtual machine name, cluster name, and datastore/folder/file name. However, '-' and '.' is apparently supported.  KB Here...