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
As with OCS 2007 R2, there are plenty of reasons why a call would fail so please be aware that this is one of the many reasons why. Problem You’re connected to your Lync Server
Ran into common problem that other administrators have probably come across the other day when I was migrating some old ESX 3.5 hosts to a new vCenter where I get the following error: The license
While troubleshoot the issues I had with a VMware ESXi cluster: https://blog.terenceluk.com/vmware-esxi-40-update-2-slow-boot-up/ https://blog.terenceluk.com/vmware-esxi-41-slow-boot-up-seemingly/ https://blog.terenceluk.com/slow-boot-up-times-on-esxi-41-do-you/ https://blog.terenceluk.com/problem-when-upgrading-from-esx-35-to/ I’ve noticed that the VMware KB article wasn’t clear on what variables existed in which ESXi version so I took
For those who have come across my previous post yesterday: VMware ESXi 4.1 slow boot up seemingly stuck at: vmw_vaaip_netapp, vmkibft, vmfs3 modules / processes https://blog.terenceluk.com/vmware-esxi-41-slow-boot-up-seemingly/ … because the host I ran into the problem
For those who have come across one of my earlier posts a few months back: Experiencing slow boot up times during an update from ESX 3.5 to ESX/ESXi 4.0 or 4.1? Check your RDMs https://blog.terenceluk.com/slow-boot-up-times-on-esxi-41-do-you/
I figure that I’ll most likely forget this some time in the future which is why I wanted to write a blog post about how you can obtain the boot up logs of an ESXi
During the first few Cisco UCS B Series deployments I was a part of, there was always this problem that I would run into that I knew what I needed to do to get around
