Day 1 – Sunday 26th of August
Some time ago I deployed vRealize Automation with vRealize Orchestrator embedded in the appliance in my home lab and I’m not very experienced yet with vRA and vRO. The reason that I deployed it is mainly that I want to get more hands-on experience with vRA and vRO and eventually use the gained knowledge for customers.
vRA was already running for a couple of months, and all the frontend self-signed certificates were already replaced by my Microsoft home lab CA issued certs. When I started using vRO, I noticed that the certificate was not replaced yet and that the appliance was still using the default self-signed one. I started googling how to replace the vRO certificate and found the following official VMware documentation. This article states that you can trust the already installed custom certificates in vRA. I executed every step from the official VMware guideline but was unsuccessful to replace the vRO certificates with the procedure. Fortunately, I was able to replace the certificates with another procedure. (more…)
Along with the vSphere 6.7 release, VMware released new versions of other products from their portfolio as well. In this blog post, I would like to demonstrate how you do an upgrade to the new vSphere Replication 8.1 version which was released last April. Since this is slightly different compared to the upgrade methods that are used in the past. (more…)
Currently, I’m working on a migration project where we are migrating VMs from a non-NSX legacy environment to a brand new NSX-enabled infrastructure. During the migration, I needed to apply NSX Security Tags in the destination environment. The tags needed to be applied based on the environment type e.g. Production and Development. And I thought; Yeah! PowerNSX is going to make my life more easier now.
Duplicate vCenter Instances registered with your Platform Services Controller can occur when you re-deploy a vCenter with the same name or in the same database. Duplicate vCenter instances can exist after a faulty certificate replacement as well.
Apart from the annoying ‘Can’t connect to vcenter.fqdn/sdk‘ message, some features are relying on properly configured vCenters within your SSO domain. You can get issues with your License Manager or with tools like vSphere Replication.
To recover from such a situation please follow these steps: