[toc] Introduction If you work in the VMware suite of products and haven’t heard of or checked out the VMware Flings website, head on over and check it out! As the website says; “Flings are apps and tools built by our engineers that are intended to be played with and explored.” A lot of products and features that make it into the product start out as being VMware flings. Some recent ones that come to mind are the vCenter Migration Tool (migrate Windows vCenter to the Appliance), HTML5 Web Client, ESXi Embedded Host client … you get the drift.

Early this morning VMware released the results for the VMware vExpert 2017 programme. Before even seeing the post, I woke up to a couple of slack messages with congrats (I’m currently on holiday and also on the Gold Coast, 1 hour behind my normal time zone!). I checked out the official post (link below) and sure enough my name is listed there, along with 1400 odd other people! From what I’ve seen there were around 100 new members in 2017.

Introduction The VMware vCenter Support Assistant is a free plugin made available by VMware in the form of a virtual appliance. After deploying the appliance, it can be registered to vSphere SSO and you can authorise one or more vCenter Servers to Support Assistant. Support Assistant provides the following benefits: Reactive support. You can use the Support Assistant plugin in the vSphere Web Client to easily create new service requests (SRs), as it is essentially a front end to the MyVMware portal.

Introduction Nimble Storage arrays are one of my favourite SAN arrays to work with at the moment. However, until Nimble OS3 which was made GA on the 31st of August, 2016, there was no support for the XCOPY VAAI primitive. This meant that when performing actions such as a storage vMotion that moved data between datastores on the same array, or cloning virtual machines, the ESXi host performing the action was required to read the data from the array up through the ESXi host, and then write it back to the array, creating additional load on the ESXi host and traffic on the storage adapters and network.

The post below will walk through the deployment of an embedded vCenter Server Appliance 6.5 using the GUI installer, where the PSC and VC roles are installed on the same servers. This deployment model is perfect for smaller environment where Enhanced Linked Mode is not required. The PSC Topology Decision Tree is a great read if you aren’t sure on how you should deploy these core components given your requirements.

The post below will walk through the deployment of an embedded vCenter Server Appliance (VCSA) 6.5 node to a target ESXi server using the command line interface (CLI) deployment method. If you are interested in also seeing the GUI deployment or other GUI/CLI deployments, please see my post here which has links off to other individual articles for different deployment methods. For each of the deployment methods I am providing a video as well.

The post below will walk through the deployment of an external vCenter Server Appliance (VCSA) 6.5 node and Platform Services Controller (PSC) to a target ESXi server using the command line interface (CLI) deployment method. If you are interested in also seeing the GUI deployment or other GUI/CLI deployments, please see my post here which has links off to other individual articles for different deployment methods. For each of the deployment methods I am providing a video as well.

[toc] Introduction So I’ve finally had some spare time to download and have a look at some of the vSphere 6.5 components and I’ll be planning to do a few blog posts in early 2017 on some of the cool new features that have been added in this release. I’ve decided to start with a few posts on the deployment of the vCenter Server Appliance (VCSA) using both the new GUI installer and the CLI option as well.

Just a quick note on something I spotted as I’ve been working through some blog posts for vSphere 6.5. It looks like you can now upload files for a Support Request to VMware directly from the vSphere Web Client. KB 1008525 lists some of the main methods for uploading diagnostic information to VMware including using the Support Assistant (which I am planning to do a post on), FTP and email. It does not yet contain information for this new feature in vSphere 6.

Every now and then I need to find the version and build number of VMware vSphere Update Manager that is running in a customer’s environment. I’ve written this post mainly as a reminder to myself, but hopefully it helps someone else down the track. VMware have a KB article for most of their products to correlate the build numbers with versions. The specific article for VUM is KB 2143837. Sometimes these aren’t always right up to date unfortunately.