NOTE: This batch script will close out of Steam and reopen it in Big Picture Mode. If you have a slow computer or you do not have Steam set to log in automatically at launch then this may not be a good solution for you.

Create a batch script and put it somewhere such as “C:\Users\YourNameHere\My Scripts\Steam Big Picture.bat”

I have successfully upgraded a VSphere environment to 5.1 and everything seems to be working perfectly besides the fact that the console now takes upwards of 15 seconds before it comes into view from black. This is in contrast to the previous vCenter 5.0 server that I had configured with half the memory which took less than a few seconds to come into view from black.

UPDATE: I started another vCenter 5.1 server from scratch and installed all the components manually in the correct order. I was then able to log into the vCenter server through the vspher client. This server is now in production and appears to be working correctly.

vSphere 5.1 was released recently.

I tried setting up a new vCenter Server 5.1 on a Windows 2008 R2 SP1 server with the Simple Install option. Installed smoothly without error. Now unable to connect to new vCenter server with the following error. It appears I am not the only one with the issue. http://communities.vmware.com/thread/420143

I will be sure to update this post with the solution. I am about try installing without the Simple Install option.