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:
When selecting Automatically apply this happens:
- The latest client patch file is added to the Site Server
- Updates the content on all Distribution Points and on all Child Sites if you are running a CAS
- 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.
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.
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.
- How To Install .NET Framework 3.5 on Windows Server 2012-2016 and Windows 10 971,576 views
- Issue with mounting new ISO files from TechNet in Windows 8 and Windows 8.1 Preview 64,140 views
- Solve SCCM Error “sending with winhttp failed; 80072ee7” in Windows PE 32,466 views
- How To Enable PXE on Gen2 Hyper-V VMs for Legacy Boot 110,907 views
- Force Specific Sites to Always Run in Compatibility Mode Using GPO 146,238 views
- How to change between a Full Installation (GUI) and Server Core in Windows Server 2012 64,562 views
- Issue With DHCP and WDS on the Same Server 12,578 views
- Issue Starting Virtual Machine from ISO in Hyper-V 7,677 views
- BitLocker Status Check Using Powershell or the Command Line 121,273 views
- Use Diskpart to Create a Bootable Windows 10 USB 30,592 views
About the author
Daniel Classon works as a Senior Consultant at Mansoft, focusing on Microsoft Configuration Manager, Windows 10 and Powershell
OMG, how did I not know this?!?! https://t.co/EjKcxI9nkB
Are you working with Enterprise Mobility + Security? One stop shop for all the documentation right here. Bookmark now! :-) https://t.co/bf3C1fhoQk #sccm #configmgr #msintune #azuread #MFA #WDATP #AIP #ATA
Check out the new Console Connections node! That's a lot of #ConfigMgr console versions connecting to our site right there!
New Blog Post: Detect Strings in Text Files using Powershell Detection Methods in SCCM: https://t.co/IZNk0Q8tOi #ConfigMgr #SCCM