If your looking to put Windows 10 IoT on your HP thin clients, here are my tips on doing that.

I picked up some used HP T620 thin clients that had WES7 on them and I wanted to bump them to Win10 after it was released.  The ones that I'm using have a 16GB mSATA SSD drives and 4GB of memory.  I had to wait awhile for HP to get the 10 image out, but now you can install the HP Recovery Image Download Tool (ThinUpdate) 64-bit and that will help you build a USB stick with the Win10 IoT installer on it.
(sp74857.exe)
http://h20564.www2.hp.com/hpsc/swd/public/detail?sp4ts.oid=5404709&swItemId=vc_161298_1&swEnvOid=4195


Be sure to get the free management software too:  HP Device Manager
http://www8.hp.com/us/en/thin-clients/downloads.html#!&pd4=1

If your like me, you don't have the Win10 COA in the BIOS to activate this image, so it wants to block the install because the OS/BIOS check fails. Here is the work around:

Find this file on the flash drive: (Where your Flash drive is drive D:\)
"D:\IBRPE\THINSTATE.CMD"

Near the bottom, look for the deploy section and add -xb switch after IBRPE.EXE
:DEPLOY
REM - Deploy image. Remove C for OS
if exist C:\ call :REMOVEDRV C
%~dp0\IBRPE.EXE -xb %2 %1
goto :EOF


Adding the -xb command line switch disables the OS/BIOS check

After the install completed, I was able to capture the image with HP Device manager and install it on my other thin clients.  I did have to make separate images for both the Dual Core and Quad Core models.

Also, I have not been able to drop the IoT image over ThinOS.  There must be something in the BIOS that blocks that.  Let me know if you find a work-around.

Windows10 IoT is a specialized version of Enterprise, so you may be required to have a KMS server or Enterprise keys in order to activate.  It activated off my KMS server just fine.

Comments

ITman007 said…
Hello,

The link of the sp74857.exe was removed, do you have any other link please.

All The best
Ed Hammond said…
I found thinupdate here:
https://support.hp.com/us-en/document/c05359199
Mark H said…
The -xb command is not working out for me...

Popular posts from this blog

Add your Office 2016 KMS Keys to your Volume Activation Server

Solving WinRM Host connection errors in SCVMM - System Center Virtual Machine Manager 2012 R2

Adding Windows 10 to your Server 2012 R2 KMS Server