P2V Conversion of an SBS 2003 Server–Part Four

Part Four – Second Run Tweaking the Server VM

This is Part Four of a Five part series about my experience doing a P2V conversion of my SBS 2003 server to Hyper-V. 

Here are links to the other parts:

 Part One – Creating the VHD

 Part Two – Creating the VM

 Part Three – First Run Tweaking the Server VM

 Part Five – Last Tweaks and We’re Running

Second Run – Configuring the New Virtual Hardware

The server reboots and we see the warning about services failing to start. Click the OK button.


After logging in, the Windows Product Activation Warning comes up. Click the No button – we still aren’t ready to activate.


This time there are some different errors. UPSMON_Service.exe crashed and the display resolution is set very low. The UPSMON crash is caused by an incomplete removal of the UPS software. Don’t send the error report – we don’t have an internet connection yet. But go ahead and adjust the resolution.


To take care of the UPSMONService error, go into the services MMC and change the UPSMONService Startup type to disabled and then click the OK button.


Non Present Device Clean-Up

There will be a number of hardware devices that were part of the original physical hardware that are still listed in the Plug and Play Enumerator, even though they are no longer present. Most of them won’t really cause any issues but some of them can be a problem. In particular, the O/S still has the physical NIC(s) listed and there is probably still an IP address assigned to that hardware. If we are going to assign the same IP address to the virtual server that the physical server had, we’ll get a TCP/IP Warning telling us the IP address is already assigned.


These “Phantom NICs” may come back to bite us at some point in the future, so it’s a good idea to get rid of them. Open a command prompt and type the following two lines:

Set devmgr_show_nonpresent_devices=1

Start devmgmt.msc


It’s important to type both commands into the command prompt rather than just starting Device Manager from the GUI. That’s because the “devmgr” environment variable that we just set will only apply to programs that are launched from the command prompt environment.

When Device Manager opens, click on View and then “Show Hidden Devices”


Expand Network Adapters and we can see the Phantom NIC. Non-Present devices show with a fainter colored icon than devices which are present. Click on the Non-Present NIC and then click the Uninstall button.


Click the OK button in the Confirm Device Removal warning box. The RAS Async Adapter gave an error when I tried to remove it, so I left it there.


Now at this point, depending on how anal you are about having a clean device manager, you can continue removing other non-present devices in other categories. For example, there is actually only one Disk Drive present in the server at the moment. All the other entries are from the various internal and external hard drives as well as USB sticks that had been plugged into the physical server over its lifetime. I’m fairly anal so I removed most of them. It’s a bit of a tedious job since the non-present devices must be removed one at a time. When we’re finished (or fed up removing phantom devices one by one), close Device Manager.


Now that the Phantom NIC(s) are gone, Open the Properties of the Local Area Connection and the double click Internet Protocol (TCP/IP).


Enter the server’s Fixed IP Address information. In my case, this was the same address that the physical server had used. I had no reason to change it, and by using the same address for the virtual server that was replacing the physical server, I didn’t have to adjust the router.


Now that the Network card has the correct IP address, we can connect the virtual Machine to a virtual network so that it can communicate with the rest of the network. On the Virtual Machine Connection Window, Click File>Settings.


Click on the Network Adapter in the hardware column and then select the appropriate virtual network from the drop down list on the right. I have several virtual networks on my Hyper-V server, including some isolated networks I use for testing. I connected this machine to the production network since it was replacing my production server. Click the OK button.


To confirm network connectivity, we can ping some hosts on the network, or open Internet Explorer and confirm we have Internet Access.


At this point I chose to reboot the server. I probably could have kept going, but I wanted to give everything a chance to start up from a clean boot.


In Part Five, I’ll cover the Last Tweaks to the server O/S, as well as configuring and testing the SBS backup to run in a Virtual Environment.

Explore posts in the same categories: Computers and Internet

Tags: , , ,

Both comments and pings are currently closed.

%d bloggers like this: