I had the opportunity to upgrade VMware vCenter 4.0 for one of the environments we manage a few weeks ago and figure I document the process. First, a bit of
About 2 to 3 weeks ago, I had to rebuild an environment’s vCenter server to move it off a Windows 2003 R2 server to a Windows 2008 R2 64-bit server
This post isn’t going to particularly interesting as it’s just screenshots of what it looks like to do an inplace upgrade of NetApp’s Virtual Storage Console from 2.0 to 2.0.1.
Update March 9, 2011: It looks like we finally have a firmware fix from Cisco: https://blog.terenceluk.com/firmware-update-fix-for-vmware-esxi-41/ ——————————————————————————————————————————————————————- I have been working in 2 separate virtualization environments with new Cisco UCS
As I indicated in one of my other posts: Problems installing VMware License Server on Windows 2008 R2 64-bit Server with Event ID 11920: “Error 1920. Service VMware License Server
I had to do an upgrade of vCenter from 4.0 to 4.1 for one of the environments we manage and came across a problem while trying to installing the VMware
The purpose of this post is to show the process of deploying VMware’s vMA (vSphere Management Assistant) in case anyone is ever interested in seeing what the deployment process and
This post will be short as the error message: Error connecting to server at ‘https://localhost/sdk/webService’ : Connection refused … is thrown if you don’t target the ESXi host first with
