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…
Hello,

the -xb command is not working out for me on a MT42.

Mark H said…
The -xb command is not working out for me...
Unknown said…
Here is how I have gotten it to work on the T620 and the T630.


Make the USB key like normal using the ThinUpdate software.
Following the instruction above for adding the -xb command.
Download HP DeviceManager 4.7 SP2
Go to C:\Inetpub\Ftproot\HPDM\Repository\Tools\Imaging\HPWES8\ibr and copy the file 'IBRPE.exe'
Paste that file to your USB drive (overnighting the old one).
Boot with the key and tell it to install.
IT WILL FAIL and it will leave you at a command prompt.
Do the following:

Diskpart
select volume 0
remove letter = S
assign letter = T
exit

Diskpart
select disk 0
clean
convert gpt
create partition efi size=100
format fs=fat32 label="System" quick
assign letter=s
create partition msr size=128
create partition primary
assign letter=c
shrink desired=16
format fs=ntfs quick
exit

now run THINSTATE.CMD from t:\ibrpe
It should take about 20 mins to install
when it is done, it will show an error
type exit and the machine will reboot
ALL SET
Ed Hammond said…
Thanks for the update Ben
Unknown said…
No need to install HP Device Manager...
Here is a zip file that contains the correct IBRPE.exe version and edited THINSTATE.CMD
https://drive.google.com/open?id=1lGVlC_02TleCGRwNx5kPNrVN_kWq4fqK
Unknown said…
Couple years later this is still keeping IT people sane!! Thank you!!
Ed Hammond said…
We decided to start placing 128GB M.2 SSD drives into these and install the Full version of Windows 10. Works great! I can pickup a used 128GB SSD used on ebay cheap, just make sure it's not an NVMe. The T620 will not work with NVMe drives.
CloudInMyHead said…
This line doesn't look right in 1st.txt, Dd someone slip while typing 1% ?

% ~ dp0 \ IBRPE.EXE -xb % 2% 1

CloudInMyHead
CloudInMyHead said…
I am guessing this is a typo in 1st.txt...
% ~ dp0 \ IBRPE.EXE -xb % 2% 1
CloudInMyHead said…
Has anyone updated their process?
I did successfully get a plain jane version of HP Win IoT onto my Windows 7 Embedded HP T630 following these steps here (Thank you all!).

Then I tried to put our current production Windows 10 IoT image taken from a NEW HP T630 that came with Windows 10 IoT and we made modifications. I can't get that onto my old Win7 T630, I can only install the plain jane Win 10 Image. I have 5 different version of IBRPE.EXE BTW.
Ed Hammond said…
I've gone away from this process and now just install 128GB SSD M.2 drives and install our Full corporate image. It found it to be much easier to setup and manage with SCCM.
CloudInMyHead said…
I could do that as well Ed. I have an SSD coming but I would rather not run a full corporate Windows 10 because I don't want to have to patch them so frequently like a regular W10 system.
I'd rather stay in the Windows IoT world for this use case.
I'll keep at it and see what I discover.
Piotr1011 said…
can you describe or show in detail how windows 10 install on a 120 gb disk? I am trying to do this but my hp t620 can not see the new disk
Ed Hammond said…
Make sure that your SSD is not an NVME, those are not supported.
It needs to be just a M.2 SSD. Sorry I forgot to mention that.
Piotr1011 said…
it seems that the disk is ok: "a..data" su 800 , m2 2280 sata , 6gb/s ssd. On the left side 6pin , on the right side 5pin.
I formatted it to ntfs and cloned my wines10. hp t620 sees it in bios, but the system does not start.
Please help me, step by step how to do it. Unfortunately, I am not fluent in technical matters.

Regards Peter
Ed Hammond said…
I downloaded Windows 10 from Microsoft using the Media Creation tool.
That created a bootable thumb stick.
I booted the T620 from the thumb stick and installed Windows 10 onto the M.2 SSD.
I did not have to do anything different that I would on any other PC.
If you cannot see the SSD from the windows 10 installer, I don't know what it would be.
If you are cloning a different PC onto the SSD before installing it into the T620, that might be the problem since the drivers will be missing.
Always install a clean copy of Windows 10.
Another issue will be that you will need to buy a license of Windows 10, you cannot use the license from another PC by cloning the OS. We are a corporation, so I already buy Windows 10 Enterprise licenses.
Piotr1011 said…
Thank you very much for your help. It was possible thanks to your tips.
Unknown said…
Hi,

I tried this with a t520 and it failed to pass the bios key check, does anyone know a way to make that work on a 520 so i can do some lab tests before buying the key upgrade packs?
Unknown said…
Hi

I used this method with success on a T520 originally licensed for Win7 Emb, with some changes:

for the diskpart part, I had to look for drive S: on volume 1 instead of 0 as originally described:

select volume 1
remove letter = S
assign letter = T


Together with the diskpart commands and thinstate download from the google drive URL above, I could install the Win10 IoT Enterprise 2016 LTSB image successfully.
I used the image with filename 14WWETDJ601_US_111417.ibr.
In ThinUpdate, I choose 'download a thin client image', I selected T520 and the latest available image, sept. 2017.


Some side notes:
As the unit does not have the Win10 OEM key, this setup could not activate successfully.
It's required to get a valid key via the known channels.
The unit for test at my desk is equiped with a 16GB disk. After image deployment, OS reported 3.94GB free on C:, so roughly 10GB is used by Windows.


Good luck and thanks for all input and effort!
Unknown said…
I dont know if anyone looks at this still, but is this something that you could build into an SCCM task sequence? I really would prefer to avoid having to perform this process on the 70 Win7e thin clients I manage.
Ed Hammond said…
Anything is possible with SCCM if it's worth your time to set it up.
For me, there was no way I was going to make this level of change in production and even though I use SCCM for OSD Deployment, I chose not to automate it with a task sequence.

Think about installing M.2 SSD is yours. You can get them for under $50 for 128GB. Then you can even put a full Windows 10 image on them. That is what we do now. PXE boot, OSD image, Done.