Toto je starší verze dokumentu!


Device Console Utility

Device Manager v konzolové aplikaci.

Nástin problému – Ačkoliv síťová karta je nativně podporovaná ve Windows 2008 R2, v Server Core edici nebyla rozpoznána správně. Pokud se připojíme přes vzdáleného Správce zařízení, píše to chybu 31. Pro instalaci ovladačů a znovu načtení ovladačů se použijí dvě aplikace:

  1. pnputil – pro instalaci ovladačů (.inf soubory); součást windows
    1. instalace
       pnputil -i -a package.inf

      resp.

       pnputil -i -a *.inf
    2. odebrání
      pnputil -d -f package.inf
  2. devcon – konzolovka, součást Windows Driver Kitu (WDK).

Instalace Intel ovladačů

Pro instalaci Intel ovladačů v Server Core edicích se dá použít utilita SetupBD.exe (která je společně s ovladači v Tools)

Získání DevConu z WDK

  1. Stáhnout Windows Driver Kit. WDK 7.1.0
  2. Připojit ISO obraz.
  3. k získání DevConu:
    1. buď přímo WDK nainstalovat: použít KitSetup.exe.
    2. nebo provést Administrative Installation MSI balíčku „setuptools_<Platform>fre.msi“:
      1. execute the following command:
        "%SystemRoot%\System32\msiexec.exe" /a "<path to WDK>\setuptools_<Platform>fre.msi" targetdir="<Desired Path>"

        např. (architektura x64, D: je virtuální mechanika)

        "%SystemRoot%\System32\msiexec.exe" /a "D:\WDK\setuptools_x64fre.msi" targetdir="%temp%"

Použití

However, even though the card is natively supported by Server 2008 R2 that Hyper-V Server is based on, it wasn’t immediately detected when I installed it. The easiest way I found to get the driver to load after initial installation is to use the devcon command line tool included with the Windows Driver Kit. It’s a command line version of Device Manager (since Server Core doesn’t include the device manager and running it remotely only allows read-only access).

First, verify that Hyper-V physically sees the card:

devcon findall =net
PCI\VEN_10EC&DEV_8167&SUBSYS_81671019&REV_10\4&35E69562&0&28A4: Realtek PCI GBE
Family Controller
ROOT\VMS_MP\0000 : Microsoft Virtual
Network Switch Adapter
PCI\VEN_8086&DEV_107C&SUBSYS_13768086&REV_05\4&35E69562&0&00A4: Intel(R) PRO/100
0 GT Desktop Adapter
ROOT\VMS_MP\0001 : External Network
4 matching device(s) found.

This should return network interfaces installed in your machine, including the new one. Next, check the status of the card:

devcon status "@<physical ID from findall command...>"

For example:

devcon status "@PCI\VEN_8086&DEV_107C&SUBSYS_13768086&REV_05\4&35E69562&0&00A4"

This should tell you that the card exists but has a problem, usually Code 01 if the driver exists but isn’t loaded. Code 31 means the driver it wants it can’t find – in that case you’ll need to download and install the vendor driver using “pnputil -i -a *.inf”.

Next remove the device then scan for PnP changes which will find it again, this time properly starting the driver:

devcon remove "@<same ID as earlier...>"
devcon rescan
devcon status "@<same ID as earlier...>"

This time it should come back happy and tell you that everything is working properly. The card should now be available in Sysconfig and the Hyper-V remote admin tools.

Zdroje

windows/devcon.1301408173.txt.gz · Poslední úprava: 29.03.2011 16:16 autor: sebi

Nástroje pro stránku