It’s been awhile since I had to update a Cisco UCS as I was on vacation when 2 projects needed to be delivered. Needless to say, I missed out on 2 deployments and was anxious
I ran into a problem while deploying a new vSphere environment for VIEW 4.5 today and thought I’d share my findings. The error message I received while adding a ESXi host to vCenter was: Call
There isn’t a whole lot to installing NetApp’s Virtual Storage Console 2.0 64-Bit for VMware vSphere 4.0 on a Windows Server 2008 R2 64-Bit server but since I had to do some documentation with screenshots,
I ran into an interesting problem the other day while refreshing one of our client’s Virtual Infrastructure 3 (VI3) hosts to vSphere 4.1. The ESX cluster had clustered SQL servers configured with MSCS and raw
We have an environment with a Windows Server 2008 R1 64-Bit SP2 server for a web application we host and during a recent maintenance window, one of the developers requested that we install .NET 3.5
We had a client out West who have been undergoing network infrastructure changes and after completing the majority of the project, they began to notice that an error message intermittently gets displayed for users when
I ran into an interesting issue a few months back when a client with OCS 2007 R2 called our support services because all of the translation rules in his location profile simply stopped working. The
We had to do some emergency maintenance with a new NetApp shelf a few days ago and found that because we were working with an older version of the firmware, there were commands that did
While performing some troubleshooting with a client a few weeks ago on their vCenter 4.1 server, I learned that vCenter 4.1 actually uses a 64-bit DSN. This meant that we no longer have to go
Warning: I’m not a SAN expert but as I’ve gotten more opportunities to work in datacenter projects, I’m beginning to see more real world SAN implementations and while this doesn’t provide a complete breakdown of
