Forum Discussion

Bervell's avatar
Bervell
Icon for Microsoft rankMicrosoft
Jul 28, 2020

Ask The IoT Expert: Windows 10 IoT Enterprise

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 ...
  • Bervell's avatar
    Bervell
    Aug 10, 2020

    Yinghua Zeng 

     

    Hey Sandy,

     

    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.

    Cheers,

    Michael

Yinghua Zeng's avatar
Yinghua Zeng
MVP
1. What is difference between Windows IoT Enterprise 2019 LTSC and Windows IoT Enterprise, version 2004? Which one should use? I notice that Windows IoT Enterprise, version 2004 has UWP apps preinstalled, so as Microsoft Store app.

2. Is Windows 10 IoT Enterprise 2019 LTSC is same as Windows 10 Enterprise 2019 LTSC, there is no different between them, just marketing spin? it is built based on Windows 10, version 1809 with 10 years support? After I activated IoT enterprise, my device was showing “Windows 10 Enterprise 2019 LTSC”, not “IoT”.

3. Can we use Intune manage IoT enterprise 2019 LTSC updates from Windows update for business? or do we have to use WSUS or ConfigMgr. Microsoft doc said Windows update for business is not supported, that is the only reason why we didn’t use IoT Enterprise for Intune managed Kiosk device, but using normal Windows 10 Enterprise.

4. Same questions as above, but for version 2004? And can it have feature upgrade to newer version later?

5. IoT Enterprise 2019 LTSC OperatingSystemSKU is 125, IoT Enterprise, version 2004 OperatingSystemSKU is 188, I don’t find them in this list https://docs.microsoft.com/en-us/dotnet/api/microsoft.powershell.commands.operatingsystemsku?view=powershellsdk-1.1.0 , do you have public Microsoft doc with updated Sku list?

6. I enrolled IoT Enterprise 2019 LTSC and IoT Enterprise, version 2004 to Intune, 2019 LTSC shows as “LTSC” in hardware inventory, but version 2004 shows as “IoT”. So this is probably related to question #2. 🙂

7. Deploy IoT device. Why cannot use Windows Autopilot for IoT Enterprise 2019 LTSC? Autopilot works for IoT Enterprise, version 2004, I tested that today.

Thank you for making this Q&A!

Regards, Sandy



Bervell's avatar
Bervell
Icon for Microsoft rankMicrosoft
Aug 10, 2020

Yinghua Zeng 

 

Hey Sandy,

 

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.

Cheers,

Michael

Resources