Longer Windows 10 servicing for enterprises and education

In case anyone missed the big announcement yesterday.

Helping customers shift to a modern desktop – Microsoft 365 Blog

In short:

Windows 10 Enterprise customers will get 30 month support (change from the 18 month). Those on current 1607, 1703, 1709, and 1803 will be extended to 30 months as well.

Future releases for Sept will have 30 months (starting with 1809) and spring releases (starting 1903) will still be 18 months for those that was faster cadences.

This is great news for Enterprise customers. For those on Pro version, might want to reconsider to move to Enterprise unless you can do the 18 month.

There are other announcements but this is the biggest as there were many concerns on the 18 month cycles.

Windows 10 Works with Existing Infrastructure

Deploying and managing Windows 10 in your business does not mean upgrading your client management infrastructure.  Use your existing SCCM and Windows Server investments to deploy and manage the new Windows 10, which has now been officially released.  See the matrix below for compatibility information.  Also note, a new version of System Center Configuration Manager is in the works which will offer new capabilities related to Windows 10 features but is not needed to get Windows 10 out to your users today!


Twitter: @jparekh_tech

Use Existing WSUS to Patch Client during ConfigMgr OSD Task Sequence

Usually when I go onsite to clients for OSD related projects, once in a while come across those that do not want to adapt to using the Software Update Point (SUP). These clients want the capability for integrating the Software Update process in the Build and Capture as well as the Deployment Task Sequences without SUP.

This is easy to do if you have the MDT 2010 Toolkit packaged.

In the Task Sequence for the Build and Capture (of the Deployment TS)

1. Add the MDT Task Use Toolkit Package

Figure 1

2. Add the task Set Task Sequence Variable. Set the WSUSServer variable to the corporate WSUS.

Figure 2

3. Add the task Run Command Line. Enter the command line as shown below (Figure 3).

Figure 3