Use the offline servicing ability described in one of those links to patch your wim
Sent from my phone, please excuse any typo's as a result. > On 12 Aug 2016, at 22:25, Miller, Todd <[email protected]> wrote: > > Thanks Niall, those links will come in handy, I’m sure. > > I tried using the media creation tool to build an Update ISO to import into > the OS Upgrade Packages, but SCCM refuses it. It looks like it might only > accept ISOs from the MVLS site - and not the ISO media creation tool, so I > will be stalled out waiting for the MVLS keeper to download the updating > enterprise ISO. > > > > From: [email protected] [mailto:[email protected]] > On Behalf Of Niall Brady > Sent: Friday, August 12, 2016 3:14 PM > To: [email protected] > Subject: Re: [MDT-OSD] Testing upgrade to Windows 10 1607 > > hi Todd, in case you haven't seem them the following should help > > How can I use the Upgrade Task Sequence in System Center Configuration > Manager (Current Branch) ? > How can I use servicing plans in System Center Configuration Manager (Current > Branch) to upgrade Windows 10 devices ? > A deeper look at the Upgrade task sequence in System Center Configuration > Manager (Current Branch) > > > On Fri, Aug 12, 2016 at 9:47 PM, Miller, Todd <[email protected]> wrote: > I have Windows 10 1511 Enterprise deployed to a couple of computers in my > environment. I would like to test the two different methods of getting > Windows 10 feature updates out to clients to figure out how we are going to > handle updating Win 10 every few months. > > For the servicing method, I am a little cautions because I just got servicing > created and now there are 16 different updates listed. I am only interested > in one – “Upgrade to Windows 10 Enterprise version 1511, 10586 – en-us, > Volume”. I don’t know how to remove all these other entries that I am not > interested in. there are entries for the other editions and also the EN-GB > flavoured language (haha) as well as the “N” versions for most. Before I > turn on servicing plans, I want to avoid downloading all those other > versions. I saw something Kent posted on his blog that he has a couple > hundred instances in there and they all started downloading (or would have). > I read a suggestion to go into WSUS and decline the update versions/editions > that I don’t need before setting up a servicing plan. What about in a couple > of months when 1607 comes into WSUS? I don’t want to have to constantly > remember to turn those off? Do I need to have servicing enabled in order to > see the version information in the servicing dashboard? I like the > dashboard, but I think I am unlikely to use servicing plans and will favor > Task Sequences. > > For the Task Sequence method, I was looking at this blog entry… > https://osddeployment.wordpress.com/2016/08/05/how-to-upgrade-windows-10-1607-with-sccm-1606-inplace-task-sequence/ > And will try to implement it that way – looks straight forward. > > I think I will need to use the TS method as there are compatibility checks > and offers to postpone required before I update a client system. I at least > want to look at the servicing method though, so I am familiar with the road > not taken. > > On a side note - I think it is hilarious and frustrating how Microsoft only > made it to the second Windows 10 update before the marketing folks abandoned > the numbering/naming system. This recent feature update is not being > marketed as Windows 10 v1607, but Windows 10 “Anniversary Update.” Will all > the feature updates going forward be named or will we just have an > inconsistent devil may care attitude towards versioning the OS and what we > use to refer to these updates? This really matters because now there is a > mix of terms used by software vendors and customers on the web announcing > compatibility and discussing issues. It also screws up web searches when you > are looking for information… What articles do I miss when searching for 1607 > and the blog author uses the term “Anniversary Update” instead and vis > versa? > > > Notice: This UI Health Care e-mail (including attachments) is covered by the > Electronic Communications Privacy Act, 18 U.S.C. 2510-2521 and is intended > only for the use of the individual or entity to which it is addressed, and > may contain information that is privileged, confidential, and exempt from > disclosure under applicable law. If you are not the intended recipient, any > dissemination, distribution or copying of this communication is strictly > prohibited. If you have received this communication in error, please notify > the sender immediately and delete or destroy all copies of the original > message and attachments thereto. Email sent to or from UI Health Care may be > retained as required by law or regulation. Thank you. > > > > Notice: This UI Health Care e-mail (including attachments) is covered by the > Electronic Communications Privacy Act, 18 U.S.C. 2510-2521 and is intended > only for the use of the individual or entity to which it is addressed, and > may contain information that is privileged, confidential, and exempt from > disclosure under applicable law. If you are not the intended recipient, any > dissemination, distribution or copying of this communication is strictly > prohibited. If you have received this communication in error, please notify > the sender immediately and delete or destroy all copies of the original > message and attachments thereto. Email sent to or from UI Health Care may be > retained as required by law or regulation. Thank you.
