I am proud to announce that my first VMware Clarity Project the VCSA JSON Creator is now live! This has been something I have wanted to do for some time, and am glad to finally have the first version available for feedback. Let’s dive in and take a look.
vSphere 6.7 Update 2 is now available! Inside this update include enhancements to the vCenter Server Converge Tool. Let’s dive in and take a look at whats new and see how to converge a deployment using the new UI.
Previously I covered how to use the VCSA Installer to do a scripted upgrade and then I covered Patching the vCenter Server Appliance (VCSA) using the REST API - Part 1 (Postman Collection) However, after learning recently how to call API’s from Powershell I thought to myself, why not write a Powershell Module for this?
Introduction Using tools such as Postman can make it utilizing API’s a bit easier, but you still need to be familiar with a separate tool or UI.
If you havent heard vSphere 6.7 U1 is now out and is loaded with all new features! If you have used 6.7 GA you may have noticed the Auto Deploy functionality did not yet make it into the long awaited vSphere Client. With vCenter Server 6.7 U1 we now have feature parity and this means Auto Deploy has been added to the vSphere Client. Lets jump in and see some of the new functionality that has been included.
The first topic we will cover in our Automating your vSphere Upgrade series is updating our core infrastructure. Upgrading Platform Services Controller(PSC) and vCenter Server via the CLI installer. In our workshops one of the common things I hear is that most folks aren’t using the CLI based tools that have been included in the installer. I am a huge fan of these as they make migrations and upgrades seamless–especially when having to perform the task if you have multiple PSC’s and vCenter Servers. Using the CLI tools don’t have to be intimidating, as we go through this blog we will cover some how-to’s and benefits of using the CLI based approach.