February 12, 2016
Posted by on
SCCM CB (Currently 1511) supports new Windows 10 Servicing model. There is an option to create a Custom Servicing Plan an deploy it to a collection od Windows 10 Computers.
This approach is similar to Automatic Deployment Rule for regular updates. It will automatically download and put the new builds in a Deployment package.
There is a huge surprise though: Custom Servicing Plan will download/distribute to DPs all versions of the build (different languages and Windows Editions) regardless the language you selected during the Servicing Plan creation. Each build is currently ~2GB, so it will be significant amount overall. Not sure why MS decided to to that and where is their QC. Probably it is a part of a new policy when products are pushed to the market half-backed and tuned-up after.
At this point I would recommend do not use servicing plans, but just a right-click necessary build in build list, download/distribute this and only this build to deployment package/DP and deploy it to a collection the same way we do for regular updates.
Kent Agerlund also suggested to Decline all unnecessary builds in WSUS manually, in this case you should be able to use Custom Servicing Plans.