If you have experienced the same and knows more about this, please feel free to share any comments.Have you ever run into questions when building an internet-connected smart display/kiosk, gateway, or robotics device using Windows 10 IoT Enterprise? Physical label info: t630/W10/32GF/8GR EURO Image tried: 16WWFTAN602 (Windows 10 Enterprise 2019 LTSC) - winver.exe shows build 1809 Image previously used is: 16WWFTCJ602 (Windows 10 Enterprise 2016 LTSB) - winver.exe shows build 1607 These images contain Windows 10 IoT Enterprise 2019 LTSC (build 1809).Īfter 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.ĭoes 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?Īnd, 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? The image names start with "16WWFTAN602_080819_" followed by a language/region code ("16WWFTAN602_080819_nl" for Dutch). 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. for thin clients purchased with a license for Windows 7 Embedded. for thin clients purchased with a license for Windows 10 IoT Enterprise and 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/. The model we deploy most often recently are T630's. Business PCs, Workstations and Point of Sale Systemsįor imaging thin clients, we use HP Device Manager (aka HPDM) or ThinUpdate.Printer Wireless, Networking & Internet.DesignJet, Large Format Printers & Digital Press.Printing Errors or Lights & Stuck Print Jobs.Notebook Hardware and Upgrade Questions.
0 kommentar(er)
