Hyper-V: How to remove disabled virtual network adapters from the parent partition

re: Hyper-V: How to remove disabled virtual network adapters from the parent partition

Ron Mitchell — Tue, 07 Jul 2009 17:02:30 GMT

John -

While Hyper-V Server R2 seems to fill a void, it is also lacking some serious management tools. For example, no device management such as Device Manager - no way to really install device drivers for devices that work with Server 2008 and not Hyper-V Server 2008 R2?

Information is spread all over the net like road kill and very little of it is helpful..

You've taken a good shot at things..but where are the tools from MS to manage this nifty system?

Ron Mitchell

re: Hyper-V: How to remove disabled virtual network adapters from the parent partition

jhoward — Tue, 07 Jul 2009 21:52:02 GMT

Ron - R2 introduces a new script, sconfig which goes much of the way to filling the void. Co-incidentally, Jeff posted up an article on our team blog just today on it: http://blogs.technet.com/virtualization/archive/2009/07/07/windows-server-2008-r2-core-introducing-sconfig.aspx

Also, this article is the best resource on how to otherwise generally remotely manage a server core box (including Hyper-V Server 2008 R2). http://technet.microsoft.com/en-us/library/cc753802(WS.10).aspx#bkmk_deployingservercore The devices bit is quite a long way down.

Thanks,

John.

re: Hyper-V: How to remove disabled virtual network adapters from the parent partition

Martijn — Wed, 19 Aug 2009 16:58:36 GMT

It worked great! I had a disabled virtual network adapter for another reason: I was fiddling with the virtual network stuff, because my VM's would get access to the internet like all other pc's. I tried bridging, one NIC, two NICs, etc.

It turned out that the simplest of all setups works. One NIC, one virtual network and no bridge of any kind. So the "best practise" seems bogus to me, because it doesn't allow my VM's to get anywhere on the network. Besides, it would occupy an extra port on the switch, which is nonsense.

Anyway, after fiddling, I ended up with a virtual network that doesn't show in the Hyper-V manager, but it *does* show in the network connections in the control panel. Disabled or enabled doesn't make any difference; Hyper-V thinks it doesn't exist. So, I disabled it. Because logically, I cannot delete it from the network connections, not from the device manager.

But this script deleted that useless good for nothing device, so now I have one working virtual network again.

Thanks!

re: Hyper-V: How to remove disabled virtual network adapters from the parent partition

Greg — Thu, 27 Aug 2009 19:30:14 GMT

What about NIC teaming in Server Core with Hyper V? I'm finding what Ron mentions above aobut documentation hard to find, scattered, and incomplete.

Thanks,

Greg

re: Hyper-V: How to remove disabled virtual network adapters from the parent partition

jhoward — Thu, 10 Sep 2009 05:24:33 GMT

Greg - a paper is in the process of being published, but for now, you need to refer to documentation supplied by the OEMs themselves.

Thanks,

John.