we have, in effect, all become advertisers of ourselves - self-evangelists ... what example are we setting?
Yesterday morning, my wife shared a video with me which had been shared with her through her Facebook community. It was the complete opposite - being the social media butterfly that she is - that I expected her to be watching, and it inspired me to reflect on my own use of electronic tools, social media, and why I resisted joining social media for so long.
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.
The concept here is to forward VPN traffic received on the public interface of the Internet router (via incoming TCP port 1194) to the OpenVPN server's interface. The VPN server authenticates the connection, and regulates forwarding traffic to and from various destinations on your private network, based on a defined set of rules. This could include forwarding traffic to your desktop to enable a remote sharing via VNC, RDP, SSH, or other protocol.
