What Windows 10 version for my VDI desktop?

In a VDI project one of the questions in the design phase is always:  “What version I use for my Windows 10 VDI desktop?”. Before Windows 10, the Operating System release cycle was approximate 3 to 5 years. With Windows 10 a new release management concept is introduced called “Windows as a Service (WaaS)”. WaaS includes:

  • Feature updates: Twice a year new feature updates to Windows 10 will be released
  • Quality updates: Deliver both security and non-security fixes every month on patch Tuesday such as:
    • Security updates
    • Critical updates
    • Servicing stack updates
    • Driver Updates
  • Servicing channels: Allow organizations to choose when to deploy new features. The following channels are available:
    • Semi-Annual Channel (SAC):  This is also known as the Current Branch. Receive feature updates twice a year (Around March and September/October) with a 18/30 months support cycle. SAC releases numbers are for example: 1703, 1709, 1803 and 1809. (1809 stands for 18 = 2018, 09 = September).
    • Long Term Servicing Branch (LTSB) that is now called the Long Term Servicing Channel (LTSC). LTSC shares the same codebase as Windows 10 IoT and is only available when having a Windows 10 Enterprise license. The typical use cases are embedded systems such as manufacturing or medical equipment and KIOSK systems that don’t run Office and receive new feature updates every 2 to 3 years. LTSC comes with 10 years support cycle and looks like an Operating System release cycle before Windows 10 such as Windows 7 for example. The new announced LTSC version is called: Windows 10 2019 LTSC build 1809.
  • Deployment rings: are groups of devices used to initially pilot, and then to broadly deploy, each feature update in an organization

So we can choose between two servicing channels. Here is a quick comparison table between the two channels:

LTSB/LTSC Semi-Annual Channel (SAC)
Support 10 years 18/30 months (Windows 10 Support lifecycle, link.)
Latest new features or security enhancements No Yes
Support for new hardware (silicon) and Surface No Yes
Default browser(s) Internet Explorer 11 Internet Explorer 11, Microsoft Edge
Office LTSC only supports Office 2019.

On January 14, 2020 , Office 365 ProPlus will be no longer supported on LSTC or the older LTSB version (link)

Updates and Security updates Yes Yes
Office support Yes Yes
Universal Apps Support Yes Yes
Cortana support No Yes
Windows Store No Yes
Windows Ink and MS camera support No Yes
Includes non-business apps like Xbox, Minecraft, Candy crush No Yes
ConfigMgr Express Update No Yes

OneDrive files on demand that is introduced in release 1709 is not included in LTSB 1607.

No Yes

The advice from Microsoft is to use SAC channel over a LTSB/LTSC channel. Ask yourself the question: Why do I use a Windows OS? My personal answer on this question is: Because I need to run legacy Windows apps.  So a stable OS that requires less patching and overhead can be more relevant than having the latest features which involves more management, testing  and overhead. But more and more customers are migrating to Office 365.  Office 365 ProPlus delivers cloud-connected and always up-to-date versions of Office desktop apps. This requires Windows Update OS requirements for Office 365 ProPlus which means you’re stuck with the SAC channel.

For choosing between the Professional and the Enterprise edition there is a comparison table available link. Windows 10 Enterprise has for example more advanced security and management functions and support for LTSC.

When deciding what channel and Windows 10 version release to use, ask yourself the following questions:

  • Define the business scope, requirements, constrains, assumptions and risks.
  • What Windows 10 versions are supported by my VDI brokers and software such as Citrix XenDesktop, VMware Horizon, App Volumes and NVIDIA for example?
  • Are we going to use Office 365?
  • Do my applications support the channel and version? Ask the software vendors.
  • Define a update and patch management plan.
  • Perform a Proof of Concept (PoC).

I hope this blog post makes it easier to choose the right Windows 10 version for the VDI desktop.

VMware Horizon View Optimization Guide for Windows 7 and Windows 8 white paper update

VMware released an updated version of the “VMware Horizon with View Optimization Guide for Windows 7 and Windows 8” whitepaper. This white paper discuss the necessary information for optimizing a Windows 7 or Windows 8 virtual desktop image for VMware Horizon View using the Microsoft Deployment Toolkit (MDT) or use a script-based approach.

The updated (July 15, 2014) “VMware Horizon with View Optimization Guide for Windows 7 and Windows 8” whitepaper can be found here. Link

Changelog scripts:

Removed on 03 June 2014
The following code was removed to fix issues with IE10, IE11, and Adobe Acrobat:
rem reg ADD “HKLM\System\CurrentControlSet\Control\Session Manager\Memory
Management” /v MoveImages /t REG_DWORD /d 0x0 /f

Removed on 11 February 2014
Rem Remove recycling bin
reg ADD “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\
policies\Explorer” /v NoRecycleFiles /t REG_DWORD /d 0x1 /f

Updated version of the VMware OS Optimization Tool

The VMware Labs Flings has an updated version of the “VMware OS Optimalization Tool”. The VMware OS Optimization Tool helps optimize Windows 7/8/2008/2012 systems for use with VMware Horizon View. New enhancements are:

  • Updated templates for Windows 7/8 – based on VMware’s OS Optimization Guide
  • New templates for Windows 2008/2012 RDSH servers for use as a desktop
  • Single portal EXE design for ease of deployment and distribution
  • Combination of Remote and Local tools into one tool
  • Better template management, with built in and user-definable templates
  • Results report export feature.

The VMware OS Optimization Tool can be found here, link

Optimize Windows 8 for Virtual Desktop Infrastructure (VDI) environments

Optimize and tuning a Windows 8 desktop in a VDI environment is important to reduce for example the CPU, IOPS and the memory footprint. During the Microsoft Management Summit (MMS) 2013 a breakout session about optimizing a Windows 8 desktop for Virtual Desktop Infrastructure (VDI) is held. The session has three main subjects: 

  • Microsoft Guidance for Windows 8 Configuration VDI desktop. What version of Windows 8 do I need, how many CPUs, memory, disk partitioning etc.
  • Detailed Review of Component Configuration. What services do I need to enable or disable, do I need to disable SuperFetch?  All the optimization settings are available in VBS script
  • Recommendations for performance testing. This section is about the (third party) tools that can be used to do performance testing.

. The Windows 8 VDI sizing and optimizations  can be used for example on the following VDI solutions:

  • VMware Horizon View
  • Citrix XenDesktop
  • Microsoft VDI

A Windows 8 VDI optimization VBS script is available. This script does all the optimization work for you. Review all the settings before executing if the fits for your environment! There will be a PowerShell version available in the future. The Windows 8 optimization VBS script can be found here.

When you want to use Windows 8 for in your VDI environment this session helps you to size, tune and optimize your Windows 8 VDI desktop. The Optimizing Windows 8 for Virtual Desktop Infrastructure session can found here.