[WinPartners] Windows 10 Current Business branch FYI

[Richard Edelson]

We've worked with Mcirosft and they released new 1511 and 1607 updates to the Enterprise build on WSUS, and they had us delete the originals that were not working. The new ones work in our test environment, but I want to give people a heads up that Microsoft requires that RTM systems first upgrade to 1511 and then to 1607. This can all be handled via WSUS, but machines will have to go through two upgrade iterations. This is not what I was looking for but it is what they have to offer us at the moment.

Richard



-----Original Message-----
From: winpartners-bounces at mit.edu [mailto:winpartners-bounces at mit.edu] On Behalf Of Brandon Mills
Sent: Tuesday, December 6, 2016 2:47 PM
To: winpartners <winpartners at mit.edu>
Subject: [WinPartners] Windows 10 Current Business branch FYI

This is just a quick FYI to anyone running Windows 10 and keeping themselves on Current Business Branch in regards to support. My understanding is, Microsoft supports non Long Term Servicing Branches of Windows 10 for at least 18 months, or the current 2 builds. Right now, the current 2 builds are 1607 and 1511. 1507, the initial release, will begin its 60-day grace period in January. The last updates for 1507 will be in March.

I just wanted to post this as a general FYI that, if you aren't on the Long Term Servicing Branch, you will have to upgrade your build of Windows 10 about every year and a half. This shouldn't be an issue with SCCM OS Updates and potentially updated builds being pushed via WSUS, but I feel like many might not understand the current support structure.

-- Brandon
_______________________________________________
winpartners mailing list
winpartners at mit.edu
http://mailman.mit.edu/mailman/listinfo/winpartners