For those who have come across my previous post about installing the Nexus 1000v: Installing Cisco Nexus 1000v 4.0.4.SV1.3b VSM on vCenter 4.1 https://blog.terenceluk.com/2010/11/installing-cisco-nexus-1000v-404sv13b.html … I noticed a nice change for the installer in the
Some of you might have come across one of my previous posts: Creating vCenter 4.1 SQL database and ODBC DSN Connection https://blog.terenceluk.com/2010/10/creating-vcenter-41-sql-database-and.html … what I realized today while having to install Update Manager 4.1 was
I recently got asked a few times about what DSN to use for 64-bit and 32-bit versions of SQL Server so I thought I’d write a post to get that cleared up. The answer is
To follow up on a post I wrote back in October 14, 2010 which was titled: Problem when upgrading from ESX 3.5 to ESXi 4.0 or 4.1 – Why are my RDM LUNs showing up
I ran into an interesting error while working at a client’s office when I was given the wrong hostname for an ESXi server I needed to connect to and because the error message I saw
I was a part of a datacenter virtualization project a few months ago where we were p2v / cloning old physical hosts to virtual machines that was hosted by a new vSphere environment we have
The cold clone process when using the VMware Convert Cold Boot CD is pretty straight forward but in case anyone out there who haven’t tried using it before and would like to know what it
It’s not surprised that there are still plenty of legacy servers out there that dates back more than 5 years ago and I find that I frequently come across servers that have storage RAID controllers
The error message you see may vary as I find that other text tends to overlap the error message such as this which was displayed on one of our servers when you hit the ALT+F11
We have a window planned over the weekend to virtualize a few old physical Dell servers so I while preparing the documents and software we needed, I realized that the last cold clone WinPE boot
