With ConfigMgr 2012 or 2012 R2, you can deploy this using a task sequence (http://blogs.technet.com/b/configmgrteam/archive/2015/06/16/revised-content-for-the-win10-in-place-upgrade-via-task-sequence-for-configmgr.aspx).
With ConfigMgr vNext, you can deploy it using Software Updates, but behind the scenes it will install the same way (in-place upgrade). The same will be true of WSUS (with the needed hotfix) in the next couple of weeks. Thanks, -Michael From: [email protected] [mailto:[email protected]] On Behalf Of Johns, Damon (DoJ) Sent: Thursday, November 12, 2015 10:10 PM To: [email protected] Subject: RE: [mssms] Re: Windows 10 Upgrade to version 1511, 10586? Confused Even more confused now! Does this mean I can deploy the current November release using Software Updates or is an in place upgrade or new reference image required? It would be nice if there was some clarification from Microsoft prior to its release! Cheers Damon Config Manager Patch management in Config Manager is performed with software update, but this feature will only allow you to deploy servicing updates. Feature upgrades must be deployed through the inplace upgrade task sequence. So here too, you are at full control and can deploy new build when ever you want. As I told above, this situation will only persist for the Threshold release because Microsoft will only support the first two release of Windows 10 on Config Manager. Future releases will only be supported on SCCM vNext (this also means that SCCM vNext should be available somewhere during the next 8 months!) and will allow to apply feature upgrades without using a task sequence in a new functionality called Windows 10 servicing<http://blogs.technet.com/b/configmgrteam/archive/2015/10/14/now-available-october-update-for-system-center-configuration-manager-tp3-.aspx>. May I add to the list that SCCM vNext has itself a “feature upgrade” like mechanism<http://blogs.technet.com/b/configmgrteam/archive/2015/09/23/now-available-update-for-system-center-config-manager-tp3.aspx> to allow faster delivery of new functionality, with (of course) end of support times… so if Windows 10 annual upgrade was not enough for you, you should really love to know that SCCM vNext must at list be refreshed every 12 month<https://twitter.com/jarwidmark/status/663877026852417537>… …Ok, I suppose some of you may ask if there is not something a bit less… disruptive… yes there is (sort of)… http://www.osd-couture.com/2015/10/windows-threshold-as-service-what-does.html ________________________________ CONFIDENTIALITY NOTICE AND DISCLAIMER The information in this transmission may be confidential and/or protected by legal professional privilege, and is intended only for the person or persons to whom it is addressed. If you are not such a person, you are warned that any disclosure, copying or dissemination of the information is unauthorised. If you have received the transmission in error, please immediately contact this office by telephone, fax or email, to inform us of the error and to enable arrangements to be made for the destruction of the transmission, or its return at our cost. No liability is accepted for any unauthorised use of the information contained in this transmission.
