to answer Damon's original question, I got the following information confirmed from the PG,
*"This update with the new classification “Upgrade” can be sync’d down from WSUS after the hotfix is applied if the “Upgrade” classification is checked explicitly. However, only vNext client 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 vNext, the install will fail. OSD Upgrade Task Sequence is still the recommended way to upgrade to Windows 10 via the current versions of ConfigMgr (excluding vNext) as these versions actually do not support Windows 10 upgrade via Software Update Management.”* On Fri, Nov 13, 2015 at 11:29 AM, Michael Niehaus < [email protected]> wrote: > There’s no way to change the time. You can however use the “Disk Cleanup > Wizard” (run it elevated) to remove it sooner. > > > > Thanks, > > -Michael > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Jerousek, Jeff > *Sent:* Friday, November 13, 2015 8:52 AM > *To:* [email protected] > *Subject:* RE: [mssms] Re: Windows 10 Upgrade to version 1511, 10586? > Confused > > > > Does anyone know where this is located? > > > > We would like to change the amount of time. > > > > Thanks, > > Jeff Jerousek > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Russ Rimmerman > *Sent:* Friday, November 13, 2015 10:14 AM > *To:* [email protected] > *Subject:* RE: [mssms] Re: Windows 10 Upgrade to version 1511, 10586? > Confused > > > > I believe it’s 28 days (at least it was in 8.1, assuming it’s the same in > 10.) > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Jason Sandys > *Sent:* Friday, November 13, 2015 8:29 AM > *To:* [email protected] > *Subject:* RE: [mssms] Re: Windows 10 Upgrade to version 1511, 10586? > Confused > > > > There is an automatic maintenance task that will delete windows.old after > 2 two weeks (I think that’s the time frame – Mike can certainly correct me > here). > > > > J > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *John Aubrey > *Sent:* Friday, November 13, 2015 6:26 AM > > *To:* [email protected] > *Subject:* RE: [mssms] Re: Windows 10 Upgrade to version 1511, 10586? > Confused > > > > I was just thinking about this. It’s a 1-2 hour update that will change a > bunch of stuff. Then we have to deal with the Windows.Old folder. One of > our big programs we use here has taken the approach of supporting what the > current build is at the time of release. This is fine if we upgraded it > every couple years, but we upgrade to 2 or 3 service packs a year. We have > the big yearly one that keeps us up with our suppliers and customers as far > as versions, and the SP are to fix all the issues. This is going to > suck….. > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Michael Niehaus > *Sent:* Friday, November 13, 2015 2:19 AM > *To:* [email protected] > *Subject:* RE: [mssms] Re: Windows 10 Upgrade to version 1511, 10586? > Confused > > > > You would need to create a new image, or you deploy the old one and then > upgrade it (each time). > > > > You can’t install 10240, upgrade it to 10586 (1511), then sysprep it – > sysprep will detect the upgraded OS and fail. > > > > Thanks, > > -Michael > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Johns, Damon (DoJ) > *Sent:* Thursday, November 12, 2015 11:13 PM > *To:* [email protected] > *Subject:* RE: [mssms] Re: Windows 10 Upgrade to version 1511, 10586? > Confused > > > > Hi Michael, > > > > Thanks for the response, if you have created a custom Windows 10 Build > 10240 reference image I assume that you cannot deploy this servicing build > using an in place upgrade with a task sequence using the Microsoft ISO… I > almost don’t need to ask, but I would like to be absolutely sure. > > > > Thanks, > > Damon > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Michael Niehaus > *Sent:* Friday, 13 November 2015 5:56 PM > *To:* [email protected] > *Subject:* RE: [mssms] Re: Windows 10 Upgrade to version 1511, 10586? > Confused > > > > 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 > <https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fblogs.technet.com%2fb%2fconfigmgrteam%2farchive%2f2015%2f06%2f16%2frevised-content-for-the-win10-in-place-upgrade-via-task-sequence-for-configmgr.aspx&data=01%7c01%7cruss.rimmerman%40microsoft.com%7c3709d63355c74d3bfad408d2ec36f37e%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=G8%2bBr8HhzkWFfhZWDghpNWUiNuQUIwNEXK3Mhc9PaaM%3d> > ). > > > > 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] <[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 > <https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fblogs.technet.com%2fb%2fconfigmgrteam%2farchive%2f2015%2f10%2f14%2fnow-available-october-update-for-system-center-configuration-manager-tp3-.aspx&data=01%7c01%7cruss.rimmerman%40microsoft.com%7c3709d63355c74d3bfad408d2ec36f37e%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=ou807RWQ4NRELsIl2pX4i7KYP62F%2bT27LLbHMqK7eOY%3d>.* > > *May I add to the list that SCCM vNext has itself a “feature upgrade” like > mechanism > <https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fblogs.technet.com%2fb%2fconfigmgrteam%2farchive%2f2015%2f09%2f23%2fnow-available-update-for-system-center-config-manager-tp3.aspx&data=01%7c01%7cruss.rimmerman%40microsoft.com%7c3709d63355c74d3bfad408d2ec36f37e%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=nJo7oB%2b5fmcJzrQZ7Mid57c20Vz4efJTHlxw5Nb2bR4%3d> > 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://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2ftwitter.com%2fjarwidmark%2fstatus%2f663877026852417537&data=01%7c01%7cruss.rimmerman%40microsoft.com%7c3709d63355c74d3bfad408d2ec36f37e%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=ZItFnQ1R%2bAsTcIOkRuQ9hPLRJ%2bsy2jfT%2f58po2iXko0%3d>… > * > > *…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 > <https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fwww.osd-couture.com%2f2015%2f10%2fwindows-threshold-as-service-what-does.html&data=01%7c01%7cruss.rimmerman%40microsoft.com%7c3709d63355c74d3bfad408d2ec36f37e%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=7KI0TNqN5Z6LLMKdJ%2bDYwcflUy48WLdk7wzkCbQdtDQ%3d> > > > > > > > ------------------------------ > > > 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. > > > > > > > ------------------------------ > > > 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. > > > > > > > > > > > > > >
