I installed Hyper-V on my new Windows Server 2008. My server has 2 nic's
with one disabled. After installing Hyper-V I realized that it virtualized
the parent partition's nic and made my enabled nic the virtual network
switch. I don't like that. I would rather the parent partition have a
dedicated physical nic. If I enable the physical nic, how can I make the 1st
physical nic dedicated to the parent partition and then make the 2nd physical
nic the virtual network switch. I know, it would have been easier had I had
the 2nd nic enabled before installing Hyper-V, but I am new on this
technology and did not realize it was going to do this. Should I uninstall
Hyper-V, enable the 2nd nic, then re-install Hyper-V or is there an easier
way to achieve my goal?

Enable the second NIC
Open the Hyper-V Manager
Click on Virtual Network Manager in the actions pane
delete any NICs it created - this will free up the physical nic once it's
done applying the changes
Add new NICs and connect them to the second physical NIC.

Should be all it takes.

--
Charlie.
http://msmvps.com/blogs/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel


"Rick Williams" <RickWilliams@xxxxxx> wrote in message
news:4ED98EBC-56FD-429C-AEFD-38827E581F87@xxxxxx

>I installed Hyper-V on my new Windows Server 2008. My server has 2 nic's
> with one disabled. After installing Hyper-V I realized that it
> virtualized
> the parent partition's nic and made my enabled nic the virtual network
> switch. I don't like that. I would rather the parent partition have a
> dedicated physical nic. If I enable the physical nic, how can I make the
> 1st
> physical nic dedicated to the parent partition and then make the 2nd
> physical
> nic the virtual network switch. I know, it would have been easier had I
> had
> the 2nd nic enabled before installing Hyper-V, but I am new on this
> technology and did not realize it was going to do this. Should I
> uninstall
> Hyper-V, enable the 2nd nic, then re-install Hyper-V or is there an easier
> way to achieve my goal?

I don't think the network configuration is exactly as perceived. Networking
in Hyper-V is a different can of worms and takes some getting used to.
Everything is virtualized, even on the parent partition, and even when it
appears not to be. On the positive side, overall it has been really great
for us and offers some nice flexibility. We have it on an HP blade server
with four NICs, and have been able to use teaming on the NICs (even though it
was stated it wouldn't work). Here's some good articles I would highly
recommend reading. There's even examples on configuring a "dedicated NIC"
and a "dedicated virtual network."

http://blogs.technet.com/jhoward/arc...n-hyper-v.aspx

http://blogs.technet.com/jhoward/arc...-networks.aspx

http://blogs.msdn.com/virtual_pc_guy...sor-to-me.aspx

Hope this helps,
Steve