Let me first touch on a few of the top consumer features before moving on to the more specific IoT device features. However, there are also some great IoT appliance features that will excite OEMs too. That is certainly the case with this new release. When Microsoft releases a new feature build, most of the new features are consumer-focused. What New Features Does 2019 LTSC Include?
It is certainly the first option for an OEM’s new project. 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. Lifecycle and support are the main reasons an OEM would want the new the 2019 LTSC product. The following graph identifies which processors and chipsets will receive continued support: nVidia is currently not supporting the latest graphics chipsets on the older 2016 LTSB product, prompting several OEM customers to transition to 2019 versions. In addition to chipsets, something as simple as your graphics card must also be considered. To use 8th or 9th gen Intel chipsets, you’ll need to move to the LTSC 2019 product. You must also consider the hardware lifecycle, which means keeping an eye on Intel’s chipset roadmap.įor the LTSB 2016 product based on build 1607, it only supports up the 7th gen Intel chipsets. 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. Even better, the 2016 product will be available and supported by Microsoft until July 2026. Here is a closer look at the Servicing for the Long Term Service Channel:Īn OEM with a solid and reliable product running on 2016 LTSB is set for years. For example, 1809, which is September 2018, will be the build and release for the new 2019 LTSC. The build versions will carry labels that correspond to the year and the month of the release.
#Windows 10 iot enterprise 2016 ltsb windows 10
This new focus will also drive a new Windows 10 feature build every six months-in March and September of each year. These changes will be permanent, moving forward. Additionally, “Current Branch for Business” (CBB) changed to “Semi-Annual Channel” (SAC). 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). (For more about that popular release, watch What is Windows 10 IoT Enterprise 2016?) Many planned to wait for the next release.Īlthough 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. The product still became popular, despite most OEMs feeling it was released too early. Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's configuration tag to point to a custom error page URL.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. This tag should then have its "mode" attribute set to "Off". It could, however, be viewed by browsers running on the local server machine.ĭetails: To enable the details of this specific error message to be viewable on remote machines, please create a tag within a "web.config" configuration file located in the root directory of the current web application. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). Runtime Error Description: An application error occurred on the server. Runtime Error Server Error in '/evalcenter' Application.