Jul 28 2020 10:39 AM - last edited on Aug 25 2020 11:55 AM by OlivierBloch
Have you ever run into questions when building an internet-connected smart display/kiosk, gateway, or robotics device using Windows 10 IoT Enterprise?
Today, in celebration of #JulyOT, I’ll be ready to discuss or answer any questions you might have around how to use Windows 10 IoT Enterprise to build the foundation for your intelligent edge devices in our Ask The Expert series.
As a Program Manager on Microsoft Windows IoT Team, I spend my days talking to customers, getting feedback, and building products to enable the next generation of embedded silicon and Internet of Things devices. Now, I want to share that knowledge with you!
Just last week we released an IoT Deep Dive to showcase how to build secure cloud-connected IoT solutions with Windows 10 IoT Enterprise. In the video Henry Fieglein from Dover Fueling Solutions described their real world solution which delivers personalized experiences in content and targeted advertising right at the gas pump; Amelia Casciola gave viewers a sneak peek of our new ARM64 support in her technical demo; and I showcased what’s next for Windows for IoT & answering the top questions from the community. (Raspberry Pi, vNext, etc).
You can watch that video here: https://www.youtube.com/watch?v=4na4RpxlnIw. Then, come back and comment with your questions!
I wanted to share a question I recently received around how to build these IoT solutions with a lower Bill of Materials cost. I thought it was interesting because it highlights the growing move of the industry to create more accessible and cost-efficient IoT solutions. The answer I shared was that enabling new smaller silicon, like the Qualcomm SDM850 or NXP i.MX 8M, with more powerful operating systems, like Windows IoT Enterprise, can truly help to democratize access to IoT solutions for all. Let me know your thoughts and, as always, share any questions you have on this topic or others.
I’m looking forward to hearing your ideas and questions – please post them as comments and I’ll do my best to help you answer them!
Jul 28 2020 12:14 PM
Aug 01 2020 06:20 PM
Aug 10 2020 11:07 AMSolution
Thank you for the amazing questions! We’re always to see customers as excited about Windows IoT Enterprise as we are at Microsoft. See below for some responses.
(RE Questions 1, 2, and 6)
Windows IoT Enterprise, version 2004 is updated on the semi-annual channel (SAC). LTSC is the Long term stability branch for 10 years. You can read about the differences between here: https://docs.microsoft.com/en-us/windows/deployment/update/waas-overview. The Microsoft inbox UWP apps are not included in LTSC versions (you can see a bit more about this at the link I referenced before). The OEM installed apps are recommended only for the SAC version. There are many considerations when deciding between SAC and LTSC which depending on your use case. That’s also described at the link referenced above.
In Win10 we combined all of the features from the previous embedded editions of Windows with the Windows Enterprise edition. So it is true that the media is the same. The activation keys come from a different range and the licensing restrictions and way you pay for a license is dramatically different. For 2019 LTSC, it will show as “Windows 10 Enterprise 2019 LTSC” even you activated it via IoT Enterprise keys. Starting in version 1903 (SAC) we introduced a unique product ID for IoT Enterprise and starting adding some subtle features to the IoT vs. the standard versions of Enterprise. If you activate with a IoT key you will get the Reserved Storage feature turned off by default. Also, the string in the description will change to “IoT Enterprise”. While the media will remain the same, we expect this trend of default configuration differences to grow over time.
(RE Questions 3 and 4)
Yes you can use Intune to manage IoT Enterprise 2019 LTSC updates. You can choose to use Intune, WSUS, or ConfigMgr. You can use these tools for version 2004 and 2019.
(RE Question 5)
188 is the new product ID introduced in version 1903 and above for Windows 10 IoT Enterprise SAC releases. Thanks for pointing out the doc page. We will follow up to update the doc.
(RE Question 7)
Windows Autopilot supports Windows 10 Enterprise 2019 LTSC which means it should support IoT Enterprise 2019 LTSC since they share the same media: https://docs.microsoft.com/en-us/windows/deployment/windows-autopilot/windows-autopilot-requirements. If you run into problems using Windows Autopilot with LTSC 2019, we can help to connect you with the right team for follow up.
Thanks for your awesome questions.
Jun 28 2021 11:02 PM
@Bervell - Thank you so much for sharing the details. Can you please confirm if you have a list of CSP supported for Windows 10 IoT Enterprise SKU? Or if it is possible to add up this information here https://docs.microsoft.com/en-us/windows/client-management/mdm/configuration-service-provider-refere...
This will help to clear a lot of confusion when configuring CSP for Windows 10 IoT Enterprise SKU. The CSP document is missing with this primary information.