December 30, 2010
I have Windows Server 2008 R2 Datacenter installed on a HP DL-360 G5 box in a lab with the Hyper-V role installed and needed to dissolve my HP Network for an experiment. This turned into quite an ordeal as the team would not dissolve with the HP Network Configuration Utility and my frustration was reaching new heights!
I had tried everything I could think of short of removing the Hyper-V role (I still have guest OS’s on there that I want to continue testing) and nothing was working. Updates, unplugging network cables, changing IP addresses, none of it helped. I then thought that removing the virtual networks from the Hyper-V manager might help. I thought wrong.
Then I happened upon a forum that didn’t give me the answer I was looking for but it did give me an idea because the post has a good explanation of how Hyper-V treats network cards and virtual networks. My idea was to rename the NICs in the Network Connections window and then remove the virtual networks using Hyper-V manager. After that I was able to dissolve the network team using HP Network Configuration Utility!
This may not work for you but I hope it at least gives you an idea if you ever have a problem dissolving a network team when using Hyper-V.