{"id":46,"date":"2009-04-01T12:50:15","date_gmt":"2009-04-01T18:50:15","guid":{"rendered":"http:\/\/localhost\/todd_wp\/cleaning-up-orphaned-network-adapters-after-migrating-ms-vpc-2007-ms-vs-2005-vpcs-to-hyper-v\/"},"modified":"2013-07-01T13:59:27","modified_gmt":"2013-07-01T19:59:27","slug":"cleaning-up-orphaned-network-adapters-after-migrating-ms-vpc-2007-ms-vs-2005-vpcs-to-hyper-v","status":"publish","type":"post","link":"https:\/\/toddbaginski.com\/blog\/cleaning-up-orphaned-network-adapters-after-migrating-ms-vpc-2007-ms-vs-2005-vpcs-to-hyper-v\/","title":{"rendered":"Cleaning Up Orphaned Network Adapters After Migrating MS VPC 2007 \/ MS VS 2005 VPCs to Hyper-V"},"content":{"rendered":"

Sometimes you are unable to remove the Virtual Machine Additions and network adapters from a VPC made with the Microsoft Virtual PC 2007 \/ Microsoft Virtual Server 2005 VPC format before you migrate it to the Hyper-V format.\u00a0 When this happens orphaned network adapters exist in the migrated VPC.\u00a0 You may not even know you have orphaned network adapters until you reboot your migrated Hyper-V VPC for the first time.\u00a0 These network adapters can wreak havoc on your Hyper-V VPC.<\/p>\n

This post describes how to migrate a Microsoft Virtual PC 2007 \/ Microsoft Virtual Server 2005 VPC to Hyper-V format when you are unable to remove the Virtual Machine Additions and network adapters before you turn on the VPC in Hyper-V.\u00a0 The steps in this blog post cause the orphaned network adapters to appear in the migrated VPC and also describe how to remove the orphaned network adapters.<\/p>\n

Before we begin I’d like to mention there are several blog posts which document some<\/em> of the same steps you will find here, here are my favorites.<\/p>\n

http:\/\/technet.microsoft.com\/en-us\/library\/dd296684.aspx<\/a><\/p>\n

http:\/\/blogs.technet.com\/matthts\/archive\/2008\/09\/12\/vmc-to-hyper-v-import-tool-available.aspx<\/a><\/p>\n

I haven’t been able to find one blog post which walks through all of the steps and ties them together in this context.\u00a0 All of the blog posts and instructions I’ve found describe how to migrate VPCs assuming you can remove the Virtual Machine Additions and network adapters before you start the VPC in Hyper-V.\u00a0 That’s why I created this post.\u00a0 \ud83d\ude42<\/p>\n

Migrate the Microsoft Virtual PC 2007 \/ Microsoft Virtual Server 2005 VPC to Hyper-V<\/h2>\n

To begin, create a new Hyper-V VPC in the Hyper-V Manager.\u00a0 When prompted for the hard drive location select the VHD file for the Microsoft Virtual PC 2007 \/ Microsoft Virtual Server 2005 VPC you want to migrate to Hyper-V format and start the VPC.<\/p>\n

After the VPC is booted up, remove the Virtual Machine Additions left over from the MS VPC 2007 \/ MS VS 2005 image.<\/p>\n

\"image\"<\/a> <\/p>\n

When prompted to restart click Yes.<\/p>\n

\"image\"<\/a> <\/p>\n

After the VPC reboots, install the Hyper-V Integration Services.<\/p>\n

\"image\"<\/a><\/p>\n

When prompted to upgrade the HAL, click OK. <\/p>\n

\"image\"<\/a> <\/p>\n

You will be prompted for the location of the halaacpi.dll.<\/p>\n

\"image\"<\/a> <\/p>\n

Insert your OS installation media DVD and attach the VPC to it.\u00a0 (You can also use a mounted ISO file.)<\/p>\n

\"image\"<\/a><\/p>\n

Browse to the I386 directory on the installation media and click Open.<\/p>\n

\"image\"<\/a> <\/p>\n

Click OK.<\/p>\n

\"image\"<\/a> <\/p>\n

When prompted to restart click Yes.<\/p>\n

\"image\"<\/a><\/p>\n

After the VPC reboots click Cancel on all the Found New Hardware Wizard dialogs.<\/p>\n

\"image\"<\/a> <\/p>\n

Insert the Integration Services Setup Disc again.<\/p>\n

\"image\"<\/a><\/p>\n

You will be prompted for the location of the hidusb.sys.<\/p>\n

\"image\"<\/a> <\/p>\n

Insert your OS installation media DVD and attach the VPC to it.\u00a0 (You can also use a mounted ISO file.)<\/p>\n

\"image\"<\/a><\/p>\n

Browse to the I386 directory on the installation media and click Open.<\/p>\n

\"image\"<\/a> <\/p>\n

Click OK.<\/p>\n

\"image\"<\/a> <\/p>\n

At this point your mouse will fail to work in the VPC and you will see the following screen.<\/p>\n

\"image\"<\/a> <\/p>\n

Use the keyboard to select No, not this time., and select the Next button.<\/p>\n

\"image\"<\/a> <\/p>\n

On the next screen, use your keyboard to select Install from a list or specific location (Advanced) and select the Next button.<\/p>\n

\"image\"<\/a> <\/p>\n

On the next screen, use your keyboard to deselect Search removable media (floppy, CD-ROM…) and select Include this location in the search:.\u00a0 Enter or browse the the I386 directory on your OS installation media and select the Next button.<\/p>\n

\"image\"<\/a> <\/p>\n

The mouse driver installation begins.<\/p>\n

\"image\"<\/a> <\/p>\n

Select the OK button.<\/p>\n

\"image\"<\/a>\u00a0<\/p>\n

Enter the path to the I386 directory on your OS installation media and select the OK button.<\/p>\n

\"image\"<\/a>\u00a0<\/p>\n

The mouse driver installation completes.<\/p>\n

\"image\"<\/a> <\/p>\n

Hooray!\u00a0 You mouse works again in the VPC and you no longer need to use CRTL-ALT-LEFT ARROW to release it from the VPC and return to the host machine.\u00a0 Click Finish.<\/p>\n

\"image\"<\/a>\u00a0<\/p>\n

When prompted to restart click Yes.<\/p>\n

\"image\"<\/a> <\/p>\n

Once the VPC reboots you will notice the network connection icon in the System Tray indicates the network adapter has limited or no connectivity.<\/p>\n

\"image\"<\/a><\/p>\n

Inspecting the Network Connections reveals a network adapter named Local Area Connection 3.<\/p>\n

\"image\"<\/a> <\/p>\n

Opening the properties for the network connection reveals that any static IP addresses and DNS information which was originally set up in the VPC (before it was migrated to Hyper-V) needs to be reconfigured.\u00a0 <\/p>\n

\"image\"<\/a> <\/p>\n

Reconfigure the network adapter to use the original network settings.<\/p>\n

\"image\"<\/a> <\/p>\n

Click OK and the following error occurs.<\/p>\n

The IP address <IP Address> you have entered for this network adapter is already assigned to another adapter ‘<Name of network adapter>’.
\n‘<Name of network adapter>’ is hidden from the Network Connection folder because it is not physically in the computer. If the same address
\nis assigned to both adapters and they both become active, only one of them will use this address. This may result in incorrect system configuration.<\/p>\n

\"image\"<\/a> <\/p>\n

Click Yes to essentially cancel the action.\u00a0 Click Cancel to close the dialog.<\/p>\n

Removing the orphaned network adapters<\/h2>\n

At this point the orphaned network adapters must be removed so the newly reconfigured network adapter settings won’t conflict with the orphaned network adapter.<\/p>\n

This<\/a> Microsoft support article describes how to do this.\u00a0 The steps in the article are described below. <\/p>\n

First open a command prompt and enter the following commands.\u00a0 The first command configures the Device Manager to show hidden devices.\u00a0 The second command opens Device Manager.<\/p>\n

\"image\"<\/a> <\/p>\n

Notice only one Network Adapter is displayed in the default view of the Device Manager.<\/p>\n

\"image\"<\/a> <\/p>\n

In the View Menu, select Show hidden devices.\u00a0 Now notice several Network Adapters are displayed in the Device Manager.\u00a0 The ‘grayed out’ network adapters are the orphaned network adapters that will be removed.<\/p>\n

\"image\"<\/a><\/p>\n

To remove the orphaned network adapters, right click them and select Uninstall. <\/p>\n

\"image\"<\/a> <\/p>\n

Click OK when prompted to confirm the uninstall.<\/p>\n

\"image\"<\/a> <\/p>\n

After you have removed the orphaned network adapters the Device Manager will look like this.\u00a0 This list will differ on depending on your VPC.<\/p>\n

\"image\"<\/a> <\/p>\n

Now you can return to your new network adapter, configure it again and commit the configuration changes without receiving the error message.<\/p>\n

\"image\"<\/a> <\/p>\n

At this point your migration is complete and the network settings for the VPC are properly restored.<\/p>\n","protected":false},"excerpt":{"rendered":"

Sometimes you are unable to remove the Virtual Machine Additions and network adapters from a VPC made with the Microsoft Virtual PC 2007 \/ Microsoft Virtual [\u2026]<\/span><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[89],"tags":[24,8],"class_list":["post-46","post","type-post","status-publish","format-standard","hentry","category-operations","tag-hyper-v","tag-virtual-environments"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/toddbaginski.com\/blog\/wp-json\/wp\/v2\/posts\/46","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/toddbaginski.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/toddbaginski.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/toddbaginski.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/toddbaginski.com\/blog\/wp-json\/wp\/v2\/comments?post=46"}],"version-history":[{"count":3,"href":"https:\/\/toddbaginski.com\/blog\/wp-json\/wp\/v2\/posts\/46\/revisions"}],"predecessor-version":[{"id":823,"href":"https:\/\/toddbaginski.com\/blog\/wp-json\/wp\/v2\/posts\/46\/revisions\/823"}],"wp:attachment":[{"href":"https:\/\/toddbaginski.com\/blog\/wp-json\/wp\/v2\/media?parent=46"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/toddbaginski.com\/blog\/wp-json\/wp\/v2\/categories?post=46"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/toddbaginski.com\/blog\/wp-json\/wp\/v2\/tags?post=46"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}