Having built a Windows 2003 or Windows 2008 virtual machine you realise the network adapter type isn’t the preferred model. After powering down, removing and adding a new adapter you’re unable to apply the IP address to the new NIC.

You’re presented with this friendly message, “The IP address x.x.x.x you have entered for the network adapter is already assigned to another adapter…”.

[The screenshot below explains]

IP address assigned to an orphaned adapter

What should I do about this?

Simple, you should remove the ‘missing’ adapter and here’s how.

• Login with an account that has Administrative rights.
• Open a Command Prompt.
• Type set devmgr_show_nonpresent_devices=1
• Type start compmgmt.msc

[The screenshot below shows the commands]

Environment variable to reveal more 'Hidden' devices

• In the Computer Management MMC expand out the Device Manager branch.
• Expand out the Network adapters branch.

[The screenshot below explains]

A single NIC, where's the other?

• On the MMC toolbar click View
• Select Show Hidden Devices

[The screenshot below explains]

Show Hidden Devices

• Looking in the Network adapters category now you should notice a few devices appear

[The screenshot below explains]

As if by magic, the missing NIC appears.

You’ll notice the orphaned adapter is ‘greyed out’.

• Right-click the greyed out adapter and select Uninstall.

[The screenshot below explains]

Remove the redundant entry

• Close the Computer Management MMC and Command Prompt windows.
• Well done.

Following on from my previous post…

If you’re running VMware ESX 3.5 you’ll need Update 5 if you’re planning to run Windows 2008R2 and Windows 7 guest operating systems.

Release notes:

http://www.vmware.com/support/vi3/doc/vi3_esx35u5_rel_notes.html

This is not breaking news but moreover a ‘note to self’ for anyone with the same thought process as me.

VMware training and common practice always says you should check the VMware HCL for any compatibility checks. Of course, what happens when the HCL isn’t up to date? It happens.

MS Windows 2008 R2 is listed as Experimental in the HCL for vSphere 4 Update 1 but actually the release notes state it’s officially supported.

So the ‘note to self’ for today…

“Also check the Release Notes”