Back

Now is a good time to consider moving from WES7

Windows versions, which one is best?

7 October 2019
Image

Now is a good time to consider moving from WES7

Context

The latest version of Windows Embedded Standard (WES) 7, Service Pack 1, is already well into it's extended support date period which is set to officially stop in October 2020.

Microsoft has changed direction with the successor OS in terms of product, licensing and customisation, this article will clarify the options and next steps.

Windows 10 IoT Enterprise LTSC is the closest successor to Windows Embedded Standard 7 (or 8/8.1) as it's designed for long term use in embedded applications; here is a breakdown of how this product is selected from the new naming strategy.

Customisation Workflow

You might still be wondering why now might be a good time consider the change, now is good because the workflow and most of the tools are different resulting in a steep learning curve if time is critical.

When creating your master image with Windows 10 IoT Enterprise LTSC you need to do this on the same hardware you use in production, not from a separate workstation with Visual Studio. The positive side of this is; there is no additional software to buy when you need to create your image, but this, of course, creates a completely new working environment. If the hardware is being refreshed on your product you would also need to consider sourcing this new hardware which you would like to use in production, because in the early stages this is used for creating your new OS. This is where RDS can make things simpler.

This also means you start from a standard install, which can be up to 15GB (64bit), you then remove parts or Microsoft branding, plus disable features, modify settings and enable the unique Enterprise features:

  • Custom Logon
  • Keyboard Filter
  • Shell Launcher
  • Unbranded Boot
  • Unified Write Filter (UWF)

As a solution provider, RDS can be flexible around the described build process;

We can provide the new target hardware kit (built to specification), pre-install the OS and activate a basic Windows 10 IoT Enterprise LTSC image meaning you only need to begin the customisation phase and testing phase.

We can also work closely with you to deliver a fully customised image as part of the whole solution, whether that is to work from a previous OS spec or to build from the ground up to new requirements.

We can even help improve consistency and reduce time spent in assembly by duplicating the image to each system pre-delivery.

Licensing

Licencing has changed too. In the past we had WES7P, WES7C or WES7E differentiated by the features available in the core OS, this is how Microsoft provided price differences.

Now license cost is dependent on CPU power, if you are refreshing your software may be a newer and more efficient CPU can be used to reduce license cost? This is something RDS will always investigate with customers.

Windows 10 IoT Enterprise LTSB

License

Cost

Use

Typical CPU Part Numbers

Typical CPU Codenames

Entry

25%

for ‘low power’ 

Intel Celeron or Pentium (N/J/G/3000), low power Atom. AMD G-Series, Athlon

Bay Trail, Braswell, Apollo Lake, Gemini-Lake, Elkhart Lake

AMD E-Kabini, Steppe Eagle.

Value

50%

for ‘mid-range power’

Intel Celeron or Pentium under Kabylake/Coffeelake naming, Core i3, i5 & Core-M. AMD  R-Series, Ryzen 3/5

Kabylake, Coffeelake, Icy Lake, Whiskey Lake, AMD Raven Ridge

High End

100%

For ‘High Power’ 

Intel i7, i9 & Xeon. AMD Ryzen 7, FX7500, FX9590

Kabylake, Coffeelake, Basin Falls, Pinnacle Ridge

 

As mentioned previously this is a new direction for Microsoft which always creates questions, feel welcome to call RDS to discuss your requirement for Windows on your embedded computer.

Click here to get more information about windows 10IoT edition

Windows 10 IoT information

Back