Thursday, April 3, 2014
Thursday, March 20, 2014
After performing a V2V, P2V or a clone operation in which the VHD/VHDX file is copied to a new VM, a new NIC is installed in the virtual machine. This is evidenced by the need to once again set the IP configuration of the NIC.
Tuesday, March 4, 2014
The recommended action is to repair the state of the virtual machine, then attempt the operation again. I was able to repair the state by ignoring the last operation, but I was still unable to start or remove the VM from the console.
Wednesday, February 26, 2014
Think of it is a way to help keep you organized and getting things done.
Wednesday, February 19, 2014
Like I said, this is just the latest experience with these folks. I have had experiences like this ever since CenturyLink took over Embarq. Bandwidth issues, privacy issues, ineptitude. Nothing but laughs, right?
Since there are no other providers on my street, I am stuck with them. Comcast has lines running seemingly everywhere around my neighborhood. I'm sure if they shot a cable down this street, every single household would subscribe to their television, internet, and even phone services.
Wednesday, February 12, 2014
You might have tried this before, and discovered that navigating to Properties -> Hardware -> firmware and changing the startup order so that PXE was first. And it didn't work, did it? Why doesn't it work?! It's first in the boot order, right?!
Why do you need to open an elevated command prompt? With newer Windows operating systems, certain files and functions are protected. Even if your user account is in the local administrators group, you still won't be able to perform certain things on your computer.