Uncategorized

To follow up on my previous post: Deploying VMware vSphere 5.1 Single Sign On, Inventory Service and vCenter Server https://blog.terenceluk.com/deploying-vsphere-51-single-sign-on/ … this post serves to continue the deployment by installing an additional vCenter and configuring

As I had to deploy 2 new instances of vCenter over the weekend in Linked Mode, I took the opportunity to document all the steps so I could write a blog post demonstrating the steps

I have to say that I wasn’t too satisfied with the documentation available setting up the database for installing the VMware vSphere 5.1 Single Sign On component independently: … rather than using the VMware vCenter

As with my previous posts for creating vCenter 4.1 and 5.0 databases, this post serves to demonstrate how to set up the database for vCenter 5.1.  Before I begin, it’s important to note that the

While I’m sure not everyone is going to run into the same issue as I did here but because this issue almost got me to pick up the phone to call VMware support until I

While I’m sure there are probably plenty of reasons that could cause the following error: Error 29120. Database schema already exists I’ve encountered this error twice while installing vSphere 5.1 (Build 880146) and thought I’d

Problem You have an existing vCenter deployed in your environment and you would like to deploy a second node in Linked Mode so you proceed with the install of SSO on the second node: Select

While this is probably not going to be a common problem to many administrators out there, I figure I’d blog this issue I encountered today in case I come across it again. You have just