Thin clients: Windows 10 IoT Enterprise OS builds and licensing

[DaveVanDulm]

For imaging thin clients, we use HP Device Manager (aka HPDM) or ThinUpdate.

The model we deploy most often recently are T630's.

Up to now, for identifying which OS Image to deploy, I used to look at the physical tag on the thin client, which states something like t630/w10/....  for thin clients purchased with a license for Windows 10 IoT Enterprise and

t630/w7/.... for thin clients purchased with a license for Windows 7 Embedded.

In August 2019, new OS images have been released for the T630, which I noticed when looking for available images using HP Update Center in HPDM. The image names start with "16WWFTAN602_080819_" followed by a language/region code ("16WWFTAN602_080819_nl" for Dutch).

These images contain Windows 10 IoT Enterprise 2019 LTSC (build 1809).

After importing and deploying this image to a T630 thin client which had "t630/w10" on it's label, Windows would not activate, stating the digital license does not match the current OS.

Does anyone know whether Win10 IoT Enterprise 2019 LTSC won't activate on all thin clients previously purchased with Win10 IoT Enterprise 2016 LTSB, using the digital license?

And, if it indeed won't activate, how can we identify which Win10 IoT version a specific thin client is licensed for, without having to contact HP for each device?

Additional information:
HPDM Version used is 5.0

Image previously used is: 16WWFTCJ602  (Windows 10 Enterprise 2016 LTSB) - winver.exe shows build 1607

Image tried: 16WWFTAN602  (Windows 10 Enterprise 2019 LTSC) - winver.exe shows build 1809

Physical label info: t630/W10/32GF/8GR EURO

                                    BID=16WWFTBE3**#SABB#DABB

If you have experienced the same and knows more about this, please feel free to share any comments.

Regards,

Dave

[nemaddux]

I am experiencing the same issue using ThinUpdate.

I am trying to deploy the image on an MT44 Thin Client. 

Did you ever have any luck?