How to configure Automatic Client Upgrade for Configuration Manager 2012 R2 SP1 CU1


Microsoft recently released the Cumulative Update 1 which fixed a lot of bugs that was introduced with Configuration Manager 2012 R2 SP1. One of the nice features with Configuration Manager R2 SP1 CU1 is that it is now possible to Automatically Upgrade clients to the latest CU version. Automatic Client Upgrade was present before but it only worked for new builds of the client, i.e Service Packs.

One trick here to keep in mind is that when installing the Cumulative Update is that you need to update Automatic Updates in the Hierarchy Settings before you run the CU1 wizard.

If you don’t, you will not see this step in the wizard:


Automatic Client Upgrade Wizard SCCM 2012 R2 SP1 CU1


When selecting Automatically apply this happens:

  1. The latest client patch file is added to the Site Server
  2. Updates the content on all Distribution Points and on all Child Sites if you are running a CAS
  3. The Client Package will be upgraded on the Local Site. Note that you need to run the CU1 upgrade on all child sites as well if you have an hierarchy to make sure that the latest version is on all Management Points. This Client Package is used if there are no Distribution Points available during Client Installation.


This is how you enable Automatic Client Upgrade:

1. Select your Site and select Hierarchy Settings in the top ribbon.

SCCM 2012 R2 SP1 CU1 Hierarchy Settings Automatic Client Upgrade
2. Go to the Automatic Client Upgrade tab
3. Check Upgrade client automatically when new client updates are available and press OK in the window that pop ups

When enabling the Automatic Client Upgrade, Configuration Manager will create a Scheduled Task for each client machine that have a version number lower that the Latest Version property. The Schedule Task will be created with a random run interval, which means that all of the clients will not be updated at the same time, which could cause performance issues. Define during which interval the clients will be upgraded. 7 days is the default, which is usually fine, but change it according to your requirements.


Automatic Client Upgrade SCCM 2012 R2 SP1


Once you have configured the Automatic Client Upgrade, simply run through the CU1 installation wizard, and you will see the step where you can select Automatically Apply as I previously mentioned.

One confusion you might run in to is when you go back and check the Latest version property in the Automatic Client Upgrade tab again after the CU1 upgrade. This version will not be changed and will remain at the Configuration Manager R2 SP1 level.


Automatic Client Upgrade SCCM 2012 R2 SP1



Here is the TechNet article referencing this.

Powershell: Script for configuring collection update refresh settings in Configuration Manager 2012


Sometimes you might want to configure how collections update in Configuration Manager 2012. Accomplishing this for a few collections works fine using the GUI, but if you want to change collection update settings for hundreds, or thousands of collections at the same time, this won’t be an option.


Configuration Manager SCCM 2012 Collection Updates


If you need to do this, use this script :) It reads the collections IDs from a file called “collections.txt” that needs to be in the same folder as the script and then sets the necesserary options.

Collection options, i.e Incremental Updates, Scheduled Updates, are set using the collection property “refreshtype”. Depedning on what integer is set here, different options will be set. These are the available options:

6 = Incremental and Scheduled Updates
4 = Incremental Updates Only
2 = Scheduled Updates only
1 = Manual Update only

The script needs to be run with one of these set and also the type of collections that are defined in collections.txt. Valid options here are User or Device.

If you would want to configure device collections in collections.txt to only update on a schedule, you would run this command:

Note that if you tick the “Schedule a full update on this collection” it will set the value that is set to the collection object. If you have changed that value sometime in the past, it will use that value or if you have never changed it, it will use the default value “Occurs every 2 weeks on Thursday effective 2/1/1970 12:00 AM”.

Here is the output of the sciprt.

Powershell script to set Configuration Manager SCCM 2012 collection update


Download the script from the TechNet Library.
Source code:

Powershell: Export a list of all dependencies for a Configuration Manager 2012 Task Sequence

Here is a Powershell script I wrote the other day which exports a list of all dependencies for a specific Task Sequence to a CSV file.

How to run it:

1. Run the script using .\Export-Task_Sequence_Dependencies.ps1 -TSID “Task Sequence Package ID”
2. Open dependencies.csv to find the dependencies for the given Task Sequence.

Please provide any feedback you might have.

You can also find the script in the TechNet Gallery.

Powershell: Add Active Directory users to groups using a CSV file

posted in: Blog, Powershell | 0

This script simply adds the users specified in the Users column in to the groups specified in the Groups column in the CSV.

Grab the script and an example CSV from the TechNet Gallery.

Updated: Script to set Outlook 2010/2013 signature using information populated from Active Directory

posted in: Blog, Powershell | 2

I updated the Signature Script that I posted last year with some bug fixes and improvements.

You can download the *.zip file which includes the script and an example *.docx template from the TechNet Gallery.

Here is the script:

Powershell: Install hotfixes only if they are not installed

posted in: Blog, Powershell | 1

Powershell Logo

If you are trying to do a script based installation of several hotfixes, you will most likely see that the script will fail if the hotfix is already installed. Here is a way of solving it, so only hotfixes that are not installed will be applied.

Powershell: Dirty workaround to copy files to current user profile

posted in: Blog, Powershell | 2

Powershell Logo

It’s always quite a hassle if you want to copy a file to the current User Profile, if you are running a script via Configuration Manager, as the script is run in System context. Another way of going around this issue is to set “Install as User” for the Deployment Type. This is however only possible if you are installing an Application and the user also needs to be a local admin on the machine, which in most cases is not permitted.

If you want to copy files to the currently logged on user, you can use this workaround. This will copy the file to all User profiles, except for the Public one. This works great if only one person logs in to the computer, but might not work well if more than one person logs in, as the file will be copied to all profiles in C:\Users.

Powershell: Copy a file to a directory that does not exist

posted in: Blog | 0

Here’s just a short tip for you. If you want to copy a file to a folder that does not already exist, you can’t just run the regular command:


If you do, you will get this error:

Copy-Item: Could not find a part of the path ‘C:\NewFolder\file.txt’


Powershell Copy to non-existing folder error


Instead, you need to create the create the folder before copying the file. Use this nice one-liner :)

Error when accessing content directly from Distribution Point for OS Image during OSD


The other day I was at a customer and I ran in to this problem:


Empty location for package: _SMSTSBEN0004A


The problem here is related to how the OS Image gets downloaded/applied during the task sequence.


At this customer, the Task Sequence was set to Access content directly from the distribution point, which is an option I usually don’t set, because I prefer to download the image first to the client before applying it.


Keep in mind if you use this option, you need to check both these checkboxes:


1. Go to the Options tab of the Apply Operating System step in the Task Sequence to find the option Access content directly from the distribution point.



2. Go to Properties of the OS Image and go to the Data Access tab to find the option Copy the content in this package share on distribution points.



At the end of the day, I ended up with removing both of these check boxes. However, if you want to use this option, remember to check both of these check boxes.

SCUP 2011 permission error when connecting to local Update Server


I got this error the other day at a customer when setting up SCUP 2011:

Failed to connect to the update server. Check your update server configuration settings and try connecting again. Request for principal permission failed.”


SCUP 2011 error



The solution to this problem was to run SCUP 2011 elevated (Run as administrator).


1 2 3 4 17