Here's the issue.
I have a server being used for Hyper-V Server. Currently, the server
has one NIC, I would like to add a second, so I can dedicate the gigabit
NIC to VMs. When I first installed the server, I had an older 10/100
NIC (Intel chipset) in, but Hyper-V wouldn't even acknowledge the NIC.
Hyper-V does see the on-board NIC with no problems.

So, the question is, how can I get Hyper-V to "see" a new NIC, and let
me install drivers, preferably the one I mentioned above.

Thanks,
Jason A.

"Jason A Ash" <JasonAAsh@xxxxxx> wrote in message
news:Oz1LewKUJHA.5824@xxxxxx

> Here's the issue.
> I have a server being used for Hyper-V Server. Currently, the server has
> one NIC, I would like to add a second, so I can dedicate the gigabit NIC
> to VMs. When I first installed the server, I had an older 10/100 NIC
> (Intel chipset) in, but Hyper-V wouldn't even acknowledge the NIC. Hyper-V
> does see the on-board NIC with no problems.
>
> So, the question is, how can I get Hyper-V to "see" a new NIC, and let me
> install drivers, preferably the one I mentioned above.
>
> Thanks,
> Jason A.

Hyper-V doesn't do that. The Server 2008 OS does. If you use a NIC which
is supported by Server 2008 the drivers should install automatically. If the
OS doesn't have built-in drivers, try the website of the NIC manufacturer.

When the OS can see the NIC you should be able to access it through
Hyper-V. If the NIC is present and working when you install the Hyper-V role
it will offer to set up a virtual switch on that NIC. If the role is already
installed you can create the virtual switch from the Hyper-V MMC.