HP EliteDesk 800 G1 WinPE Driver for Windows 10

[talksr]

Does anyone know where I can source a WinPE driver for Windows 10 for an HP Elite Desk 800 G1 computer?

 

I have been on their support site, but I can't find that specific driver.

 

I need it for our RM CC4 server such that we can use Windows Deployment Server to deploy Windows 10 to this specific model of HP.

[mikeyd101]

We have a bunch of them new beginning of this year you should be able to get all the drivers via hp support site, not sure there's a specific driver for winPE I've just used the regular driver in MDT in the past.

 

One issue we did run into with these is that when they went into sleep they would start broadcasting ipv6 traffic (alot, tens of thousands of packets), I updated the NIC driver and disabled ipv6 and it cured the problem. Was some issue with a specific version of the Intel i217 NIC driver.

Edited February 1, 2016 by mikeyd101

[talksr]

We have a bunch of them new beginning of this year you should be able to get all the drivers via hp support site, not sure there's a specific driver for winPE I've just used the regular driver in MDT in the past.

 

One issue we did run into with these is that when they went into sleep they would start broadcasting ipv6 traffic (alot, tens of thousands of packets), I updated the NIC driver and disabled ipv6 and it cured the problem. Was some issue with a specific version of the Intel i217 NIC driver.

 

Thanks very much for your post.

I found the driver site for this model: Drivers & Software for HP EliteDesk 800 G1 Small Form Factor PC - HP Support Center.

 

But you mention you used the regular MDT driver. Where did you find this?

[superaz300]

Hello,

 

If this is for a CC4 network, can you not just simply import the driver into the RM Management Console and then regenerate the build disks, if your stuck give me a shout as I am known as the CC4 Driver Man back at my work.

 

Thanks

 

James

[mikeyd101]

The regular downloaded from hp driver imported in MDT.

 

Your'll probably need to get it out of the hp packaged .exe (mine was sp70278.exe) run that it creates a sp70278 folder with the actual driver installer and driver files with DRIVERS folder actually containing the importable .inf file.

 

it might also put the sp70278 under c:\swsetup as that where all the hp program and driver installations go.

[talksr]

Hello,

 

If this is for a CC4 network, can you not just simply import the driver into the RM Management Console and then regenerate the build disks, if your stuck give me a shout as I am known as the CC4 Driver Man back at my work.

 

Thanks

 

James

 

Well yes, that is what I was expecting, but we seem to be going round and round on the RM merry go round at the moment.

 

They have had me test that Windows 8 works, we already know it works on the same station through WDS.

Then they had me install Vanilla Windows 10 -already done that too and confirmed dev man has no errors or problems. I have suggested thrice now that we should export the working drivers from 10 Vanilla and use them, but now they want me to Smart Client it. Not sure what that is going to achieve. This issue has been dragging on for three weeks now, have got a stack of brand new systems still not able to go out to classrooms!

[superaz300]

Right, what I have made mistakes with before is this.

1. If you have the Window 10 Client Pack, its a new Windows PE 10 image and I am sure it is x64 bit, but its best to get x32 and x64 bit NIC drivers and import them both into the RMMC.

2. Make sure the NIC driver shows up on the RM Default Build Disk 10 template, if not add it.

3. Regenerate the build disk, and add it with WDA.

 

Boot it to from PXE, let it loads up the CC4 build client and you should have a Connected build session. Also, WSUS should pick up most of the drivers for Windows 10 and install them on there own, we noticed this with the Intel Nucs, all I needed to do was to import the NIC drivers, the rest of the drivers like Graphics, chipset etc was picked up by Windows updates at the end of the build session.

 

If you still need some help, PM me and we can do a remote session?

 

Hope this helps

James

[talksr]

Right, what I have made mistakes with before is this.

1. If you have the Window 10 Client Pack, its a new Windows PE 10 image and I am sure it is x64 bit, but its best to get x32 and x64 bit NIC drivers and import them both into the RMMC.

2. Make sure the NIC driver shows up on the RM Default Build Disk 10 template, if not add it.

3. Regenerate the build disk, and add it with WDA.

 

Boot it to from PXE, let it loads up the CC4 build client and you should have a Connected build session. Also, WSUS should pick up most of the drivers for Windows 10 and install them on there own, we noticed this with the Intel Nucs, all I needed to do was to import the NIC drivers, the rest of the drivers like Graphics, chipset etc was picked up by Windows updates at the end of the build session.

 

If you still need some help, PM me and we can do a remote session?

 

Hope this helps

James

 

Hello,

 

Thanks for your help. You would have thought it would be NIC drivers, but the funny thing is, it goes a long way through the RM build on Windows 10 and then when joining to the domain, it fails.

Build Process aborting due to the following error:

Communication exception failed to send request or receive

reply within maximum number of retries.

 

If there was a fault with the NIC drivers, it would not have managed to get that far.

Also, you mention "If you have the Window 10 Client Pack" - I don't have this, where can I source it?

 

Thanks again

[superaz300]

When I say the Windows 10 Client Pack, you can download this from the My Account are a on RMS website, think it's called the Windows 10 Build Client. This is of course if your support contract for CC4 is still valid. In terms of the NIC drivers, what I'm saying is it will use the x32 driver to install the operating system with, and when the OS is installed it will install the x64 bit driver for use within the rest of the build client.

 

Thanks

James

[talksr]

When I say the Windows 10 Client Pack, you can download this from the My Account are a on RMS website, think it's called the Windows 10 Build Client. This is of course if your support contract for CC4 is still valid. In terms of the NIC drivers, what I'm saying is it will use the x32 driver to install the operating system with, and when the OS is installed it will install the x64 bit driver for use within the rest of the build client.

 

Thanks

James

 

Ah I see, yes have a valid CC4 account. Didn't even know about this!! I am slowly finding out that they have missed telling me quite a few things. I went for my CC4 training about 4/5 years ago, maybe since then, there have been some reasonable changes.

[talksr]

Ah ok, we already have it - it must have been put on during the server install. We have a new RM server which was an upgrade for our old server 2003 model. It is just a case of putting on the right driver as you say. Really not sure why they wanted me to smart client it to diagnose this issue. I have already explained it works fine as vanilla. I need to get the driver on the image, and they have had me farting around smart clienting it when I have already explained that we have a really large number of these 800 G1s and can't be smart clienting them all. Language barrier maybe?

[superaz300]

When was the server commissioned? They have only just released this about 2 weeks ago. If you give me the exact model numbers of the computers, I will get you the drivers for you ready to import into the RMMC.

 

Thanks

James

[talksr]

When was the server commissioned? They have only just released this about 2 weeks ago. If you give me the exact model numbers of the computers, I will get you the drivers for you ready to import into the RMMC.

 

Thanks

James

 

Last week of December, so may have just missed out.

 

We have a couple of HPs which are not working.

The main one at the moment is the HP 800 G1. We have HP 400 G1's which work absolutely fine.

I ran the driver scan on a vanilla install on the 800 G1 and got the following driver: Intel I217-LM - it's the NIC driver. Have been banging on about this driver for around 1 week now and only today RM said I should import it into the build.

I have imported that driver and recreated the boot image. Will try it tomorrow and see if it works.

Keeping my fingers crossed.