Windows 10 Servicing in ConfigMgr 1511

Playing around with Windows 10 Servicing in ConfigMgr 1511 is kind of cool. But having said that; you might want to know the consequences of creating custom servicing plans. A servicing plan is basically an automatic deployment rule with a twist. The twist being (right now), you are unable to filter on the updates being downloaded. Regardless of the Windows 10 versions and languages the servicing plan will always download all 256 Windows 10 versions. Each version is about 2 GB….do the math. Contentlibrary will explode in size, if you selected all remote distribution points; the Network team will not be happy (as in, not at all).



If you like me (in my test), create a custom servicing plan, you might get an error like this, saying that you ran out of disk space!!!!!


So how do we work around this? For now; I personally download the update directly from the console. Right click your win10 enterprise x64 and download it to a package. Remember to apply this ConfigMgr hotfix or you might run into a cert issue when downloading.

By | 2016-01-12T01:37:56+00:00 January 12th, 2016|Configuration Manager (SCCM), General info|25 Comments

About the Author:

Kent Agerlund
Microsoft Regional Director, Enterprise Mobility MVP. Microsoft Certified Trainer and Principal consultant. I have been working with Enterprise client management since 1992. Co-founder of System Center User Group Denmark in 2009. Certified MCITP: Enterprise Administrator, MCSA+Messaing, and much more. Member of: Microsoft Denmark System Center Partner Expert Team The Danish Technet Influencers program System Center Influencers Program.


  1. Sandy January 13, 2016 at 22:52 - Reply

    How about the “language” tab, is it possible use language filter?

  2. Kent January 14, 2016 at 2:17 - Reply

    in 1511 there are no options to filter. Filtering (declining) can be done in WSUS

  3. Tom January 14, 2016 at 22:25 - Reply

    Just to clarify – you are saying not to use the “Servicing Window” feature, just download the upgrade you need to a Deployment package and deploy it directly to a collection…?

  4. Kent January 14, 2016 at 23:08 - Reply

    that’s what I have been doing all week in my win10 project. Downloaded win10 1511 into a software update group and deployed it as a normal update – works just fine.

    • Sandy January 15, 2016 at 14:42 - Reply

      I tried deploy it as normal updates, but it never showed up in Software Center. Jason Sandys comments that cannot deploy upgrades as Norman updates, must use servicing plan.

      • Sandy January 15, 2016 at 14:44 - Reply

        Norman–>normal. Auto correct is terrible in my phone.

  5. Tom January 14, 2016 at 23:40 - Reply

    Thanks, makes sense. I just wanted to make sure there wasn’t some way to trick it to get just the upgrade you needed into the servicing plan without the rest…

  6. John January 21, 2016 at 20:50 - Reply

    I can’t get this to work as a regular windows update. Was there anything special that you did?

  7. John January 21, 2016 at 21:42 - Reply
  8. Rodrigo Fronza January 25, 2016 at 12:28 - Reply

    Hello, Kent
    I wonder in this case when doing this upgrade, the overall one Windows folder called Windows.old, it is cleared by a scheduled task?
    Grateful for your attention.


  9. […] Agerlund hat in seinem Blog auf ein interessantes Problem […]

  10. Oliver January 31, 2016 at 23:29 - Reply

    Hi, i created a Service plan and noticed that everytime my WSUS synced i got a new Software Update Group with the same Content. Anybody else has seen this ?

  11. […] Watch out if you start enabling the Windows 10 Servicing functions. I imagine many people will discover this “issue” when they realise they have suddenly run out of disk space! Best approach is to manually download […]

  12. Steve February 6, 2016 at 2:55 - Reply

    If you would like to use the custom servicing plan and don’t want download all upgrade of Windows 10 Edition, go to the WSUS console and decline all upgrade edition that you don’t need. After that, the custom servicing plan only download the upgrade and language that I need.

  13. Shane February 10, 2016 at 4:15 - Reply

    BEFORE you enable the Upgrades classification on your Software Update Point in ConfigMgr CB v1511+ for syncing in ConfigMgr… go into the WSUS console (yes WSUS, the one that points to your top level SUP).

    Then open “Update files and Languages”
    Then go to the “Update Files and Languages” tab.
    By default this will be set to “Download updates in all languages”
    Change it to only the languages you need.

    Then enable the Upgrades classification in ConfigMgr.
    Then only the languages you selected in WSUS will be sync’d with ConfigMgr

    As per above, if you’ve already sync’d and all languages sync’d into ConfigMgr, you have to go into WSUS and decline the Upgrades you don’t want.

  14. […] Agerlund also suggested to Decline all unnecessary builds in WSUS manually, in this case you should be able to use Custom […]

  15. […] in earlier releases were that Windows 10 Servicing was downloading all upgrade packages and distributing those to distribution poi…. So it downloads 256 times about 2GB package and distributes it to all distribution points.. eh, […]

  16. Oleksiy Shtanko April 20, 2016 at 20:34 - Reply

    I have this problem — under “All Windows 10 Updates” I have only EN-US and EN-GB versions of updates and upgrades to Windows 10, altough in Site Role “Sofware Update” I have selected Russian (or Ukrainian or any other, result is the same).
    How can I fix this?
    My WSUS-server is controlled by SCCM and, as I see it, when I add languages to Site Role they should synchronize to my WSUS, right? But on my WSUS-server there are only English ticked under Options, no matter what combination of settings I chose and how many times I’ve synchronized it.

  17. Brent April 22, 2016 at 7:20 - Reply

    I was able to get my custom servicing plan created with only 2 updates in it, by specifying a Language and Title search criteria.

    What I wanted was on the Windows 10 Enterprise en-us upgrades.

    My search criteria is:
    Language: English
    Title: Enterprise OR – N OR – en-gb

  18. Kent April 22, 2016 at 9:52 - Reply

    Filtering has been improved in 1602, I also recommend that you filter on “Required”

  19. Philippe M. April 28, 2016 at 16:27 - Reply

    Hi all,

    And what about Multilanguage ?
    I mean, My Wim is natively built with En-US and inside in (with DISM) I put Fr-FR and En-GB.
    What happend if I send an upgrade on computers. Multilanguage still there or should I select a specific stuff in Service plan ?

    • Sumit Batra September 5, 2016 at 18:01 - Reply

      Hi Philippe,

      Were you able to find out how to deploy the upgrade on machine with Language pack like yours, I am struggling to deploy the upgrade as part of Windows 10 servicing, any help would be much appriciated.

      many thanks

  20. Ann May 11, 2016 at 11:22 - Reply

    Has anybody been able to run through this process yet? I have v1602 and created the service plans, this have evaluated and recognised updates that are required, it has downloaded the upgrades and distributed the package out to the DP’s but this is as far as it has got. Anyone know why it may not have created my deployment or suggestions on where to look? my deployment schedule on the service plan is for ASAP with a deadline of 7 days.

    Many thanks

  21. Alenat August 18, 2016 at 22:23 - Reply

    Thank you Brent. Put a bit more details for your idea how to limit languages /editions:

Leave A Comment