When Microsoft released its first Long Term Service Branch (LTSB) product in July of 2015, most people didn’t even understand what it was or why they would want to use it. The product still became popular, despite most OEMs feeling it was released too early. Many planned to wait for the next release.
Although Microsoft planned to release a new LTSB version every two to three years, the Windows 10 product quickly improved, prompting a release just a year later in 2016. (For more about that popular release, watch What is Windows 10 IoT Enterprise 2016?)
Then again, following two-plus years and numerous Windows 10 builds, Microsoft decided to change “Servicing Branches” to “Servicing Channels,” prompting an acronym change (Now, LTSC). Additionally, “Current Branch for Business” (CBB) changed to “Semi-Annual Channel” (SAC). These changes will be permanent, moving forward.
This new focus will also drive a new Windows 10 feature build every six months—in March and September of each year. The build versions will carry labels that correspond to the year and the month of the release. For example, 1809, which is September 2018, will be the build and release for the new 2019 LTSC.
Here’s an overview of 2019 roadmap:
Here is a closer look at the Servicing for the Long Term Service Channel:
Considering 2019 LTSC? Know This…
An OEM with a solid and reliable product running on 2016 LTSB is set for years. Even better, the 2016 product will be available and supported by Microsoft until July 2026.
However, it is important to remember that it isn’t just Microsoft’s roadmap you must consider when designing and forecasting the lifecycle of your device. You must also consider the hardware lifecycle, which means keeping an eye on Intel’s chipset roadmap.
For the LTSB 2016 product based on build 1607, it only supports up the 7th gen Intel chipsets. To use 8th or 9th gen Intel chipsets, you’ll need to move to the LTSC 2019 product.
In addition to chipsets, something as simple as your graphics card must also be considered. nVidia is currently not supporting the latest graphics chipsets on the older 2016 LTSB product, prompting several OEM customers to transition to 2019 versions. The following graph identifies which processors and chipsets will receive continued support:
Lifecycle and support are the main reasons an OEM would want the new the 2019 LTSC product. Not only does it extend the lifecycle by 2 additional years, but it opens the door to newer chipsets that will extend your hardware lifecycle. It is certainly the first option for an OEM’s new project.
What New Features Does 2019 LTSC Include?
When Microsoft releases a new feature build, most of the new features are consumer-focused. That is certainly the case with this new release.
However, there are also some great IoT appliance features that will excite OEMs too. Let me first touch on a few of the top consumer features before moving on to the more specific IoT device features.
Feature #1: Dark File Explore
Though Microsoft already has the “Dark” color option, it was impossible to turn it on in the file explorer. Now you can. Most OEMs never display the file explorer in their appliances, so this is not a must-have feature for an IoT Device.
Feature #2: Cloud Clipboard
I often need to copy something like a screenshot or text from one system to the other (I have two systems side by side). This new feature allows you to share a clipboard between your Windows 10 devices. Again, not something I can see an OEM using with an appliance, but still a nice new feature and one I’m personally excited about.
Feature #3: Improved Snipping Tool
The improved snipping tool (which I use daily) now gives you the ability to take a full-screen capture as well as a square-shaped or custom-shaped one. It also will be paired with a new Screen Sketch app that will allow you to add notations using Windows Ink.
Feature #4: New Search Experience
The next version of Windows 10 will deemphasize Cortana’s features and put search at the forefront of its UI. Different search categories are showcased at the top of the search panel, with Cortana’s pick-up-where-you-left-off activities being showcased. I wouldn’t see this as a new feature for an OEM appliance, but certainly, for situations where the search capabilities are required, this might be useful.
Feature #5 New Game Bar
The completely redesigned built-in Game Bar makes in-game controls more useful for PC gamers. No longer is it just a quick-bar for taking screenshots and recording video; it now showcases useful performance information such as CPU, GPU, and RAM usage. It also features a much cleaner UI that’s easier to understand. For OEMs that build gaming systems or appliances, this is a worthy feature update.
Improvements specific for IoT devices
Enhanced kiosk status reporting support via MDM
- Kiosks and digital signs are often placed in public places where issues are widely seen by people. With built-in status reporting, device management systems are automatically made aware of problems and can issue corrective actions like restarting the device or dispatching a service technician.
- Assigned access monitors the kiosk runtime state and allows the MDM server to query the latest status.
- Optionally, IT admin can opt-in to alerting mode, allowing an MDM to generate an alert to the MDM server when a kiosk runs into errors.
Simplified assigned access experience and ability to configure Edge kiosk settings
- Reducing deployment and management costs are key drivers of ROI. Windows 10 IoT Enterprise has improved features for configuring a kiosk experience via a new wizard in the Settings app, managing multi-app kiosks, and tailoring the Microsoft Edge browser experience for kiosk devices. More info here.
- Currently, you have the flexibility to configure Assigned Access using provisioning packages, the Settings app, and mobile device management systems. Now, a new set of Assigned Access APIs allows developers to configure Assigned Access programmatically from within their applications. More info here.
Ability to auto launch an app in the multi-app kiosk experience
- Customers can now specify an auto-launch experience as part of the multi-app assigned access configuration so the end user always has a default primary app experience.
- Added parameters to XML for multi-apps here
- You can control what the user sees from the moment the device is turned on until it’s powered off.
- Showing your logo instead of the Windows logo at boot, or auto-restart apps without error messages after an app crash, a system issue or a power interruption.
One last and very important item…
Several older Embedded products are ending their support in 2019 and 2020.
If you are still running any of the products listed below, start testing your platform on Windows 10 IoT Enterprise and 2019 LTSC now. It will be the product to use.
If you would like more information on Windows 10 2019 LTSC please reach out to our team here at Arrow via msembedded@arrow.com
