If you haven’t got this resolved – I would check the bios version and get the latest version. We had a similar issue with HP’s 650 ProBook and PXE booting, turned out there was issues with the bios.
From: [email protected] [mailto:[email protected]] On Behalf Of Matt Gerding Sent: Wednesday, 12 July 2017 12:11 AM To: [email protected] Subject: RE: [mssms] HP Elitedesk 800 G3 Drivers Maybe I’ll just start there and update the ADK. There is a different boot image that gets created with MDT. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Adam Juelich Sent: Tuesday, July 11, 2017 11:54 AM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] HP Elitedesk 800 G3 Drivers I don't use MDT but isn't there a separate MDT WinPE Boot image outside of the standard WinPE from the ADK? I'm running WinPE 1607 as well. I've never had to inject NIC drivers into WinPE as long as I continue to update the ADK. On Tue, Jul 11, 2017 at 9:58 AM, Matt Gerding <[email protected]<mailto:[email protected]>> wrote: Thanks for the quick response. I don’t get an IP, so I’m sure it’s the NIC driver.. I have an MDT Boot image OS Version 10.0.10240.16384, which was installed with the ADK ver before Win 10 1607. I know I’m running an old version and I intend on upgrading, but up until now, we have had no issues with hardware or Windows 10 1607 deployments. From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Adam Juelich Sent: Tuesday, July 11, 2017 9:55 AM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] HP Elitedesk 800 G3 Drivers When you get into WinPE, if you hit F8 do you have an IP Address? If no, then your NIC isn't in your Boot Image. Which ADK/Boot Image version are you using? On Tue, Jul 11, 2017 at 8:24 AM, Matt Gerding <[email protected]<mailto:[email protected]>> wrote: Looking for some troubleshooting guidance - I’ve set up driver packages for multiple devices in SCCM before (HP, Dell, Lenovo) and have run into almost no issues adding the drivers or deploying images. However, we recently received new HP hardware (HP EliteDesk 800 G3 mini desktop), the successor to the 800 G2, which we were using perfectly fine. I can’t get an image to deploy to the 800 G3. I grabbed the driver pack from the HP site, went through the normal process of importing the drivers, adding a package, distributing content to my OSD distribution point, added drivers to the TS..etc. I noticed a notification when importing the drivers suggesting that some of the drivers may not be compatible. I went through the drivercatalog.log file and found the following: The INF file data is invalid. Cannot initialize driver information. \\centurionmp.com<https://apac01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcenturionmp.com&data=02%7C01%7Ctodd.gannon%40cbh.com.au%7C58cfef3a885d484c638d08d4c8784918%7Cbdc5206836da48a79690d7703f926d76%7C1%7C0%7C636353866342063158&sdata=5Y7Jk5mVR4NnsMfKUXjpI0UMAxf9N0d6b%2FHWEVEzoz4%3D&reserved=0>\sccm\sourcefiles\OSD\Drivers\Source\HPEliteDesk800G3MiniWin10_x64\Network\Intel\IntelI219_KKMEB2\21.1_12.15.23.7\src\DRIVERS\iqvw64e.inf does not contain any supported hardware information. \\centurionmp.com<https://apac01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcenturionmp.com&data=02%7C01%7Ctodd.gannon%40cbh.com.au%7C58cfef3a885d484c638d08d4c8784918%7Cbdc5206836da48a79690d7703f926d76%7C1%7C0%7C636353866342063158&sdata=5Y7Jk5mVR4NnsMfKUXjpI0UMAxf9N0d6b%2FHWEVEzoz4%3D&reserved=0>\sccm\sourcefiles\OSD\Drivers\Source\HPEliteDesk800G3MiniWin10_x64\Network\Intel\IntelI219_KKMEB2\21.1_12.15.23.7\src\DRIVERS\iqvw64e.inf does not contain any supported hardware information. I thought that maybe I just had a corrupted file. Bad NIC driver. Grabbed the drivers a second time, but still no luck. Took the drivers off of the DVD that are packaged with the hardware to see if those would work.. still no luck. Individually downloaded the NIC driver and tried to inject it into the boot image. I still have the same issue. When I PXE boot the machine, it acquires an IP and starts loading winPE. The process gets to the MDT splash screen, hangs for about 2 minutes and then the machine reboots and goes back to the PXE network boot. I’ve tried more than one G3 computer, we have secure boot turned off, the drivers are x64, we deploy win 10 1607, running SCCM current branch. Any thoughts? Suggestions? As always, thanks in advance for your help and insight. Regards, Matthew Gerding Information Technology Centurion Medical Products 517.540.1618<tel:(517)%20540-1618> www.centurionmp.com<https://apac01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.centurionmp.com%2F&data=02%7C01%7Ctodd.gannon%40cbh.com.au%7C58cfef3a885d484c638d08d4c8784918%7Cbdc5206836da48a79690d7703f926d76%7C1%7C0%7C636353866342063158&sdata=cGqJjlJkzpQia2DTnjOn1eQV5V%2FOME%2BehLAiA21MWt8%3D&reserved=0> ••••••••••••••••••••••••• PATIENT CARE WITHOUT COMPROMISE™ This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this mail in error please notify the originator of the message. This footer also confirms that this email message has been scanned for the presence of computer viruses. Any views expressed in this message are those of the individual sender, except where the sender specifies and with authority, states them to be the views of the CBH Group.
