Jump to content


anyweb

First Major Update for Windows 10 Available Today - Windows 10 version 1511

Recommended Posts

If you logon to MSDN or the Microsoft Volume License websites you'll see some new downloads available for Windows 10, namely:

These downloads are for the Threshold 2 release of Windows 10, now called Version 1511 (using the following convention YY//MM). Full details about what these new releases contain are listed in the blog post from Terry Myerson here.

 

You'll notice that the LTSB media isn't updated, and that's what you'd expect for the Long Term Servicing Branch.

 

Note: You may need to install this update on your WSUS or SUP infrastructure to see the upgrade category. https://support.microsoft.com/en-us/kb/3095113

 

Corporate domain joined pc's can be Current Branch or Current Branch for Business depending on how you want them to 'update' and how often, see this post for details https://technet.microsoft.com/.../mt598226%28v=vs.85%29.aspx

 

If you have defer upgrades selected in Windows update advanced options, then your pc's are using CBB (current branch for business) with an approx 4 month gap after today's release in terms of needing to upgrade.

 

Defer receiving feature upgrades for a period of approximately four months after Microsoft makes them available publicly, to provide IT administrators with time to perform pre-deployment testing and provide feature upgrades releases with additional time-in-market to mature. For more information, see Deferred feature upgrade installation with Current Branch for Business (CBB) servicing.

 

 

 

If you attempt to update Windows Home, Pro or Enterprise via Windows Update today you'll see the update as long as you are on Current Branch (CB)

 

updating to 1511.png

 

Can I deploy this via ConfigMgr ?

 

This update with the new classification “Upgrade” can be sync’d down from WSUS after the hotfix is applied (linked above) if the Upgrade classification is checked explicitly. However, only ConfigMgr vNext clients can complete the end to end installation successfully since this Windows 10 Upgrade is in a different format and requires special handling on the client side. Without ConfigMgr vNext, the install will fail.

Using an OSD Upgrade Task Sequence is still the recommended way to upgrade to Windows 10 via the current versions of ConfigMgr (excluding ConfigMgr vNext) as these versions actually do not support Windows 10 upgrade via Software Update Management.

 

cheers

niall

Share this post


Link to post
Share on other sites

it does not appear to be available for Server 2008 R2 currently, I do not know if it will be either, we have to wait for Microsoft to confirm this via their anticipated blog post, as a workaround, you can fire up a SUP/WSUS on Server 2012R2 and apply the hotfix to that server.

Share this post


Link to post
Share on other sites

I believe it is still rolling out, i.e. in progress, so if you've applied the hotfix listed above, and if the upgrade category is not showing up then have some patience

Share this post


Link to post
Share on other sites

If you logon to MSDN or the Microsoft Volume License websites (not availble there yet, is due November 16th according to this post on Technet) you'll see some new downloads available for Windows 10, namely:

These downloads are for the Threshold 2 release of Windows 10, now called Version 1511 (using the following convention YY//MM). Full details about what these new releases contain are listed in the blog post from Terry Myerson here.

 

You'll notice that the LTSB media isn't updated, and that's what you'd expect for the Long Term Servicing Branch.

 

Note: You may need to install this update on your WSUS or SUP infrastructure to see the upgrade category. https://support.microsoft.com/en-us/kb/3095113

 

Corporate domain joined pc's can be Current Branch or Current Branch for Business depending on how you want them to 'update' and how often, see this post for details https://technet.microsoft.com/.../mt598226%28v=vs.85%29.aspx

 

If you have defer upgrades selected in Windows update advanced options, then your pc's are using CBB (current branch for business) with an approx 4 month gap after today's release in terms of needing to upgrade.

 

 

If you attempt to update Windows Home, Pro or Enterprise via Windows Update today you'll see the update as long as you are on Current Branch (CB)

 

attachicon.gifupdating to 1511.png

 

Can I deploy this via ConfigMgr ?

 

This update with the new classification “Upgrade” can be sync’d down from WSUS after the hotfix is applied (linked above) if the Upgrade classification is checked explicitly. However, only ConfigMgr vNext clients can complete the end to end installation successfully since this Windows 10 Upgrade is in a different format and requires special handling on the client side. Without ConfigMgr vNext, the install will fail.

 

Using an OSD Upgrade Task Sequence is still the recommended way to upgrade to Windows 10 via the current versions of ConfigMgr (excluding ConfigMgr vNext) as these versions actually do not support Windows 10 upgrade via Software Update Management.

 

cheers

niall

 

Niall,

 

Not sure if you are aware, but the 1511 update is now available for download via the VLSC and can be found as an additional option under Windows 10 Enterprise download selection

 

Regards

 

Leon

Share this post


Link to post
Share on other sites



×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.