VMUG, VDM Challenge, vExpert, oh my ...

What have I been up to lately?

It has been a very busy summer so far. Besides my day job, very busy family life, and volunteer work, I’ve been actively engaged in the virtualization community; however, as a result, my blog posts have suffered. This is not simply an excuse, but an acknowledgement of my own limitations and a big kudos to all those who are able to continue posting regular updates in the #vCommunity despite external obligations. :)

four issues I encountered deploying vCenter and SRM 5.5 in a Windows environment

My Experience Deploying vCenter and Site Recovery Manager 5.5

Knowledge is like money: to be of value it must circulate, and in circulating it can increase in quantity and, hopefully, in value. - Louis L’Amour

The virtualization community, like many others, exibits a very generous spirit of giving. The knowledge that we each possess, perhaps acquired through our own experiences, evolves as we circulate it with others.

After being virtually off the social grid for the past month, I decided to resume my activity by sharing some installation ‘gotchas’ that I encountered while deploying vCenter and Site Recovery Manager 5.5.

Please note: these solutions are all based on VMware KBs (noted below) and were tested against vCenter Server and Site Recovery Manager 5.5 running on Windows Server 2012, with SQL Server 2012 SP1 supporting databases.

Although relatively minor issues, I hope that you may found this useful and may avoid some of the same headaches that I encountered.

how to log-in to a fresh install of vCenter Server 5.5 using domain credentials (updated)

Updated: January 24, 2014.

I have read a few posts within the community lately [1][2] about an issue being encountered after a fresh install of vCenter 5.5. Basically, what happens is the only user that can log-in to the vCenter server is the SSO administrator (Administrator@vsphere.local). This may seem like unexpected behaviour, especially considering that even the account (perhaps an AD service account) that was used to perform the install is also unable to log-in and see the vCenter Server.

In contrast to the long title for this post, the solution that I would like to share is short and straight forward. I hope that this solution will save you from some post-install headaches.