While this informational message can be caused by various reasons, here’s the list that I could think of off the top of my head: You’ve just completed virtualizing a server to a virtual machine and
I’ve been meaning to get some screenshots of this problem because I’ve been asked about this error a few times and since I had some P2V work tonight with a client that had the setup
To follow up with a post I made yesterday about reconfiguring an ESX 4.x server’s service console to different vmnics: Quick note about reconfiguring an ESX 4.x server’s service console to different vmnics https://blog.terenceluk.com/2011/01/quick-note-about-reconfiguring-esx-4x.html …
So I had quite the “kick off” on my first day back at work for the year 2011. To cut a long story short, I was asked to figure out why 3 of our UCS
As some of you may remember, I ran into an issue a while ago when I was deploying VMware View 4.5 for customer demos. The problem I had was that the View Transfer Server required
I ran into an issue while doing some tests at night for changing SCSI controllers on a virtual machine and thought this might be a common problem for others in the field so I hope
After noticing that I get asked: Why can’t I expand the provisioned size of a hard disk for a virtual machine on ESXi/ESX? … by clients on an average of twice a month, I thought
There are a lot items required to do after you virtualize physical servers such as uninstalling the hardware specific applications and removing hidden devices but one of the items I find people tend to miss
While this warning messaging doesn’t really affect a virtualized physical host after you’ve successfully P2V-ed it, I personally prefer clean Windows event logs because it makes troubleshooting errors in the future better. Problem You’ve successfully
One of issues I’ve come across over the past few years when virtualizing HP ProLiant servers was that I would continuously get the message: At least one service or driver failed during system startup …
