Windows Servicing Plans vs Task Sequences

On Twitter I asked the following to David James (Director of Engineering, ConfigMgr, Microsoft) and Johan Arwidmark (CTO @ TrueSec): https://twitter.com/DevSecNinja/status/1024927840138145793 For example, I have 3 device collections in SCCM that I call: “Windows 10 Feature Updates - Test” “Windows 10 Feature Updates - Pre-Production” “Windows 10 Feature Updates - Production” With ADRs, that’s quite simple. Just add the deployment to the Software Update Group in SCCM and you’re done. But I was wondering if that is supported in the Servicing Plan scenario too, as with a Servicing Plan you define the amount of days it will take after a build release, before SCCM will deploy the feature update to the collection. ...

04-08-2018 · 2 min · Jean-Paul van Ravensberg

Lock screen image not showing - Windows 10 1703

Recently I was trying to apply a lock screen image with a GPO. I distributed the image to the C:/Windows/Web/Wallpaper directory and configured the Windows 10 GPO to that location. After running the Windows 10 Task Sequence successfully, the default lock screen image came up. I was using a large image from the client so that it still looks good on bigger screens. I’ve found out that after resizing the image back to 1080P, the image was applied successfully after locking the machine. ...

10-09-2017 · 1 min · Jean-Paul van Ravensberg

Which Windows ADK version to use with Configuration Manager 1511?

I had some issues with the newest Windows ADK (1511) with Configuration Manager 2012 R2 SP1 CU2. As of yesterday, it’s possible to download the newest version of Configuration Manager: 1511. Because I had issues with the newest ADK, I’ve asked Microsoft on Technet if we still need to use the older ADK (10.0.26624.0) or if we can use the newest 1511 version of the ADK: [ ](/images/2015/12/adkversion.png) Check the post mentioned in the image above to download the right ADK version when you are going to use the new Configuration Manager 1511.

09-12-2015 · 1 min · Jean-Paul van Ravensberg

SCCM - Unable to connect to WMI (root\ccm) on remote machine

Problem The following error occurs in the ccm.log when doing a remote client install: Unable to connect to WMI (root\ccm) on remote machine “COMPUTER” Solution Allow the following rules in Windows Firewall: Outbound and inbound: File and Printer Sharing Inbound: Windows Management Instrumentation (WMI)

28-12-2014 · 1 min · Jean-Paul van Ravensberg