By Jeffrey Cook, Solution Consultant in System Management and End User Computing, Data#3.
[Reading time: 2 mins]
Since April 2016 a couple of things have happened in relation to Windows 10 and the new windows servicing model. We now have three versions of Windows 10:
|Name||Date code||Build number|
|Windows 10 RTM||1507||10240|
|Windows 10 November Update||1511||10586|
|Windows 10 Anniversary Update||1607||14393|
This is the first CBB release of Windows 10 since Release To Manufacturing (RTM) so a number of the servicing options are now available. If you are using servicing plans in System Center Configuration Manager (ConfigMgr), Windows Server Update Services (WSUS) or Windows Update for Business, this will enable the servicing of your 1507 clients with the CBB release. For more details see Windows 10 1511 is now a Current Branch for Business (CBB).
It is also worth noting that Windows 10 RTM is now in the second cycle of CBB. This means that RTM will no longer be supported after the next CBB release. For you to stay supported you will need to start planning to migrate devices onto newer releases of Windows 10 before the RTM becomes unsupported.
How do you know the version you are on?
Open a command prompt and run “winver”.
When will the next release be?
Microsoft has said 3-4 times a year, but as you can see above this is just a guideline. It will pay to be prepared for the possibility of a release every 3 months but it is unlikely that it will occur.
While this is being called an “update” and being released as such, in the general terminology of servicing I would consider this an “upgrade” as it is a feature release for Windows 10. For the purpose of this post I will refer to it as a feature update.
Firstly, let’s define what exactly a “feature update” is. It is a feature release for Windows 10. A feature update adds new features and functionality to Windows 10 and is identifiable by a new build number. Some of the additional features in the 1607 release are:
Note: This is not a security update. Security updates will not be effected by this update.
If you are running 1507:
Start preparing for migration to a more recent version of Window 10 to maintain support and take advantage of the new features. If you have automated servicing plans in place (either ConfigMgr or WSUS) prepare to use the in-place servicing.
If you are running 1511:
You are on a supported version for the next 6 months (approx.) and do not need to do anything urgently. It is recommended that you prepare for the next wave of releases as this is an ongoing process and will need to be managed.
On any version:
No matter what version of Windows 10 you are using, the new servicing model is now in place and regular updates are required to maintain support. Microsoft products, such as ConfigMgr and WSUS, have built these updates into their toolset to help you easily move to this structure. If you haven’t already, now is the time to start looking at the strategies and process to keep up to the pace of these releases.
Make sure you subscribe to this blog for more updates on Windows 10. To learn more about how Data#3 can help with your migration visit data3.com.au/windows-10