RDP issue with DL380 G5

[RSPiet]

We are trying to load Windows Server 2003 on a DL380 G5 using Rapid Deployment. The RDP job we’re using has been run successfully on a variety of Proliant servers. Our RDP server is currently version 3.70 and we still use a DOS automation CD.

The one issue we’re having is that the NC370i NIC drivers don’t load during Windows setup. At first it looked like the problem was that one of the DLLs was having its file name truncated to 8.3 format when it got copied down to the server in DOS mode. I found a utility to fix the name after it is copied, but Windows setup still refuses to load the driver. I did some research and found that there is a special driver that must be used for RIS with the NC370i. I was able to get the RIS driver to load from the $oem$ directory during setup, but Device Manager shows the NIC as not functioning with this driver.

Below are the error messages from SETUPAPI.LOG file when Windows tries to install the multi-function NIC driver during setup. It shouldn’t be an issue with the DLL as I can go into Device Manager after setup is complete and the driver loads fine when I tell it to search the C:\$oem$\1\drivers\net directory.


[2008/08/21 15:38:52 340.1870 Driver Install]
#-019 Searching for hardware ID(s): pci\ven_14e4&dev_164c&subsys_7038103c&rev_12,pci\ven_14e4&dev_164c&subsys_7038103c,pci\ven_14e4&dev_164c&cc_020000,pci\ven_14e4&dev_164c&cc_0200
#-018 Searching for compatible ID(s): pci\ven_14e4&dev_164c&rev_12,pci\ven_14e4&dev_164c,pci\ven_14e4&cc_020000,pci\ven_14e4&cc_0200,pci\ven_14e4,pci\cc_020000,pci\cc_0200
#-199 Executing "C:\WINDOWS\system32\setup.exe" with command line: setup -newsetup
#I022 Found "pci\ven_14e4&dev_164c&subsys_7038103c" in C:\drivers\net\bxvbd.inf; Device: "HP NC373i Virtual Bus Device"; Driver: "HP NC373i Virtual Bus Device"; Provider: "Hewlett-Packard Company"; Mfg: "Hewlett-Packard Company"; Section name: "NC373i_inst_x86".
#I023 Actual install section: [NC373i_inst_x86]. Rank: 0x00000001. Driver date: 05/22/2007. Version: 3.4.10.0.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [NC373i_inst_x86] in "c:\drivers\net\bxvbd.inf".
#I320 Class GUID of device remains: {4D36E97D-E325-11CE-BFC1-08002BE10318}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-124 Doing copy-only install of "PCI\VEN_14E4&DEV_164C&SUBSYS_7038103C&REV_12\5&1F051E87&0&0000E1".
#-175 SPFILENOTIFY_COPYERROR: Source = "c:\drivers\net\wdfcoinstaller01005.dll", Target = "C:\WINDOWS\system32\wdfcoinstaller01005.dll", Flags = 0x00000000, Error = 0x00000002.
#E176 SPFILENOTIFY_COPYERROR: returned FILEOP_ABORT. Error 1223: The operation was canceled by the user.
#W187 Install failed, attempting to restore original files.
#I060 Set selected driver.
#-166 Device install function: DIF_INSTALLDEVICE.
#I125 Installing NULL driver for "PCI\VEN_14E4&DEV_164C&SUBSYS_7038103C&REV_12\5&1F051E87&0&0000E1".
#E122 Device install failed. Error 0xe0000219: The installation failed because a function driver was not specified for this device instance.
#E157 Default installer failed. Error 0xe0000219: The installation failed because a function driver was not specified for this device instance.
#-166 Device install function: DIF_INSTALLDEVICE.
#I125 Installing NULL driver for "PCI\VEN_14E4&DEV_164C&SUBSYS_7038103C&REV_12\5&1F051E87&0&0000E1".
#I121 Device install of "PCI\VEN_14E4&DEV_164C&SUBSYS_7038103C&REV_12\5&1F051E87&0&0000E1" finished successfully.

[Cederberg]

I would recommed you to using WINPE for windows installations. I've had no problem deploying windows 2003 on DL380 G5 servers or any other servers using that NIC. The OEM drivers you are using are you sure it's for windows 2003? the OEM drivers are loaded as the first step in windows installation.

The original job for windows 2003 deploys the PSP on the end. So i belive that windows uses an general driver for the nic untill the PSP is Deployed

[RSPiet]

The problem ended up being long file names when you run Windows setup under DOS. Even though I was fixing the long file names in the $oem$ directory after they were copied, you have to use a $$Rename.txt file to tell Windows setup to rename the files when they are copied from the $oem$ directory.

http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/prork/prbc_cai_qcaq.mspx?mfr=true

http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/prork/prbc_cai_pwue.mspx?mfr=true