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. :)
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.
