The first upgrade for SCCM Current Branch (1511) is now available. This post is a complete step-by-step SCCM 1602 upgrade guide. If you’re looking for a complete SCCM 1511 installation guide, see our blog series which covers it all.

Installing SCCM upgrades is very important to your infrastructure. It adds new feature and fixes lots of issues, which some of them are important.

New Update and Servicing

Since SCCM 1511, Microsoft now release update pack differently than services packs and cumulative updates. Downloading and updating is made directly from the console. If you need to make a new SCCM installation, you can’t install SCCM 1602 directly. You need to install SCCM 1511 first and then apply SCCM 1602 from the console. SCCM 1511 is still the baseline version if you’re starting from scratch.

The update process seem quite easy but don’t get confused. Yes, it’s easy to apply, but these updates needs to be planned as much as you planned cumulative updates and service pack in the past. (During the installation process all SCCM services including SMS_Executive service are stopped)

As stated on the Configuration Manager Team blog,  the new servicing methods is designed to support the much faster pace of updates for Windows 10 and Microsoft Intune. (You can expect 3 or 4 of these updates per year). They also mentioned that they plan to support each version/update for 12 months before they require that customers upgrade to the latest one to continue support. This basically means that you can skip SCCM 1602 if you want and apply SCCM 1606 (fictional name) at release. The important thing to remember is to update before the 12 month end-of-support period.

New features and fixes

This update contains new features and applies the latest KB/fixes to fix known bugs.

  • Client Online Status
    • You can now view the online status of devices in Assets and Compliance. New icons indicate the status of a device as online or offline
  • Support for SQL Server AlwaysOn Availability Groups
    • Configuration Manager now supports using SQL Server AlwaysOn Availability Groups to host the site database
  • Windows 10 Device Health Attestation Reporting
    • You can now view the status of Windows 10 Device Health Attestation in the Configuration Manager console to ensure that the client computers have a trustworthy BIOS, TPM, and boot software
  • Office 365 Update Management
    • You can now natively manage Office 365 desktop client updates using the Configuration Manager Software Update Management (SUM) workflow. You can manage Office 365 desktop client updates just like you manage any other Microsoft Update
  • New Antimalware Policy Settings
    • New antimalware settings that can now be configured include protection against potentially unwanted applications, user control of automatic sample submission, and scanning of network drives during a full scan

Our favorite feature is Client Online Status which will greatly help operational tasks. A computer is considered online if it is connected to its assigned management point. To indicate that the computer is online, the client sends ping-like messages to the management point. If the management point doesn’t receive a message after 5 minutes, the client is considered offline.

SCCM 1602 upgrade guide

Before you begin SCCM 1602 Upgrade Guide

Downloading and installing this update is done entirely from the console. There’s no download link, the update will appear in your console.

If you’re running a multi-tier hierarchy, start at the top-level site in the hierarchy. After the top-level site upgrades, you can begin the upgrade of each child site. Complete the upgrade of each site before you begin to upgrade the next site. Until all sites in your hierarchy are upgraded, your hierarchy operates in a mixed version mode.

Before applying this update, We strongly recommend that you go through the upgrade check list provided on Technet.

In this post, we’ll be updating a standalone Primary Site Server, console and clients.

Before installing, check if your site is ready for the update :

  • Open the SCCM console
  • Go to Administration \ Cloud Services \ Updates and Servicing
  • In the State column, ensure that the update is Available

SCCM 1602 upgrade guide

If you’re not seeing the update, Microsoft has provided a PowerShell script to force the download. If you’re not in a hurry, just wait and it should appear in the next following days.

Refer to Dmpdownloader.log to see download progress :

SCCM 1602 upgrade guide

The update files gets saved in the EasySetupPayload folder in the Configuration Manger setup folder

SCCM 1602 upgrade guide

SCCM 1602 upgrade guide

Step 1 | SCCM 1602 Prerequisite check

Before launching the update, we recommend to launch the prerequisite check :

  • Open the SCCM console
  • Go to Administration \ Cloud Services \ Updates and Servicing
  • Right-click the Configuration Manager 1602 update and select Run prerequisite check

SCCM 1602 upgrade guide

  • Nothing will happen, the prerequisite check runs in the background. All menu options will be grayed out during the check
  • The one way to see progress is by viewing C:\ConfigMgrPrereq.log

SCCM 1602 upgrade guide

  • You can also monitor prerequisite check by going to Monitoring / Site Servicing Status, right-click your Update Name and select Show Status

SCCM 1602 upgrade guide

  • When completed the State column will show Prerequisite check passed

SCCM 1602 upgrade guide

Step 2 | Launching the SCCM 1602 update

We are now ready to launch the SCCM 1602 update

  • Right click the Configuration Manager 1602 update and select Install Update Pack

SCCM 1602 upgrade guide

  • On the General tab, click Next

SCCM 1602 upgrade guide

  • On the Features tab, select the features you want to update

SCCM 1602 upgrade guide

  • If you don’t select one of the feature now and want to enable it later, you’ll be able to so by using the console in Administration \ Cloud Services \ Updates and Servicing \ Features

SCCM 1602 upgrade guide

  • In the Client Update Options, select the desired option for your client update
    • This new feature allows to update only clients member of a specific collection. Refer to the Technet article for more details

SCCM 1602 upgrade guide

  • On the License Terms tab, accept the licence terms and click Next

SCCM 1602 upgrade guide

  • On the Summary tab, review your choices and click Next

SCCM 1602 upgrade guide

  • On the Completion tab, close the wizard. The whole process took a minute but the installation is not over, it has been initiated. For now on, no more GUI, you need to use log files to monitor the installation

SCCM 1602 upgrade guide

  • During installation, the State column changes to Installing

SCCM 1602 upgrade guide

  • You can  monitor installation by going to Monitoring / Site Servicing Status, right-click your Update Name and select Show Status…

SCCM 1602 upgrade guide

  • … or you can follow detailed installation progress in SCCM Installation Directory\Logs\CMUpdate.log

SCCM 1602 upgrade guide

  • Services are stopped

SCCM 1602 upgrade guide

  • When completed, you’ll notice the message There are no pending update package to be processed

SCCM 1602 upgrade guide

  • Refresh the Updates and Servicing node, the State column will be Installed

SCCM 1602 upgrade guide

Updating the consoles

The console now has an auto-update feature. At console opening, if you are not running the latest version, you will receive a warning and the update will start automatically.

  • Since all updates operations were initiated from the console, we didn’t close it during the process. We received a warning message when clicking certain objects. You will have the same message when opening a new console

SCCM 1602 upgrade guide

  • Click OK,  console update will starts automatically

SCCM 1602 upgrade guide

SCCM 1602 upgrade guide

  • Wait for the process to complete. You can follow the progress in C:\ConfigMgrAdminUISetup.log and C:\ConfigMgrAdminUISetupVerbose.log. Once completed, the console will open and you’ll be running the latest version.

SCCM 1602 upgrade guide

SCCM 1602 upgrade guide



After setup is completed, verify the build number of the console. If the console upgrade was successful, the build number will be 5.0.8355.1000. You can also notice that Version 1602 is stated.

SCCM 1602 upgrade guide


  • Go to Administration \ Site Configuration \ Sites
  • Right-click your site and select Properties
  • Verify the Version and Build number

SCCM 1602 upgrade guide


The client version will be updated to 5.0.8355.1000 (after updating, see section below)

SCCM 1602 upgrade guide

SCCM 1602 client Package distribution

You’ll see that 2 client update packages are created :

  • Navigate to Software Library \ Application Management \ Packages

SCCM 1602 upgrade guide

  • Select both package and initiate a Distribute Content to your distribution points

Boot Images

Boot images are automatically updated during setup. See our post on upgrade consideration in large environment to avoid this if you have multiple distribution points.

  • Go to Software Library / Operating Systems / Boot Images
  • Select your boot image and check the last Content Status date. It should match your setup date

Updating the Clients

Our preferred way to update our clients is by using the Client Upgrade feature.

  • Open the SCCM Console
  • Go to Administration / Site Configuration / Sites
  • Click the Hierarchy Settings in the top ribbon
  • Select Client Upgrade tab
  • The Upgrade client automatically when the new client update are available checkbox has been enabled
  • Review your time frame and adjust it to your needs

SCCM 1602 upgrade guide

Monitor SCCM client version number

SCCM Reports Client Version

You can se our SCCM Client version reports to give detailed information about every clients versions in your environment. It’s the easiest way to track your client updates.

SCCM 2012 - System Health Configuration Manager SS


You can also create a collection that targets clients without the latest client version. I use it to monitor which client haven’t been updated yet.

Here’s the query to achieve this: (You can also refer to our Set of Operational Collection Powershell Script which contains this collection)

[pastacode lang=”sql” message=”” highlight=”” provider=”manual” manual=”select%20SMS_R_SYSTEM.ResourceID%2CSMS_R_SYSTEM.ResourceType%2CSMS_R_SYSTEM.Name%2CSMS_R_SYSTEM.SMSUniqueIdentifier%2CSMS_R_SYSTEM.ResourceDomainORWorkgroup%2CSMS_R_SYSTEM.Client%20from%20SMS_R_System%20where%20SMS_R_System.ClientVersion%20!%3D%20’5.00.8355.1000′”/]

Happy updating ! 🙂

Comments (57)


05.22.2017 AT 03:12 PM
I am super late to the updating of my SCCM and just updated to SCCM 2012 r2 sp1 CU 4, now everything I have search for says that SCCM 1511 must be installed first before getting to the current branch. The issue is I cannot find a download for 1511 and in my VLSC it only has the current branch 1702. Any suggestions? Thank you

Mike C

08.24.2016 AT 02:14 PM
I've upgraded to 1602 and everything went well. This past weekend though all of the servers have upgraded their client to the latest version. I have "Do not upgrade servers" checked in the Client Upgrade tab in the Hierarchy Settings Properties and also have "servers" unchecked in the Client Push Installation Properties. Any ideas on where to check why the clients are upgrading?

David Guirl

08.23.2016 AT 05:08 PM
Regarding "Updating the Consoles" ... check all Site Systems, MP's, etc for consoles and upgrade them!!!! and then remove them!!! TL😀R I would like to share my experience with a menacing problem with clients not performing hardware inventory and falling out of active client state. 3 months after opening a ticket with Microsoft, and 1 week after getting an SEE on board, we discovered that our MP was having WMI issues. The reason for this was because some loving administrator that I inherited SCCM from installed a Console on the MP server. Our MP server is separate from our Primary Site server. This caused the client to not update because the console was not updated (I didn't realize I needed to update it). This caused a domino effect and a mismatched version between the Primary Site and the MP begun showing the WMI errors... long story short, clients couldn't get the policy to run Inventories, and therefore became Inactive, then moved to Client=None... So once we discovered this, we upgraded the console on the MP, it in turn upgraded the client (a reboot was required for the upgraded console) and voila! Now I have a bunch of clients to repair and can move on with my life!!

Marc Graham

07.16.2016 AT 01:02 AM
*I am using unofficial acronyms to facilitate less typing* I have a question around Automatic Client Upgrade (ACU) and Pre-Prod Client Upgrade (PPCU). Should ACU be enabled before PPCU? If ACU is enabled and you upgrade, won't the production client version become the newest version? Or, is the behavior that when you enable PPCU it inhibits ACU until the new client version is promoted via PPCU? What is the best practice on this as I am preparing for an upgrade which includes almost 100k clients

Chris Bakke

07.11.2016 AT 12:49 PM
Great article. We have completed the update at may customer sites. We noticed after 1511 and subsequent upgrade we have had to redploy PXE to get that working again. Any ideas on this. It is a simple process. Uncheck PXE on the DP wait for uninstall then recheck PXE and install. After everything is fine.

Nicholas Baldwin

07.13.2016 AT 01:36 PM
I cant seem to get PXE to work 🙁 I am on update 1602 Console V: 5.0.5355.1306 Site V: 5.00.8355.1000 I did 1511 yesterday and PXE was working great, ran the update last night and now PXE is broke. PC doesn't see PXE connection. I have tried "turning PXE off" and waited a hour even rebooted the server. Anything else I can try? Thanks Nick

Jonathan Lefebvre

07.14.2016 AT 07:48 AM
Hi Nicholas, I've seen in previous updates that an Update Distribution point on Boot images was mandatory. Normally, the update should trigger this automatically. Problem is, some drivers are preventing the update on the Boot images and the process goes in error without clear notice to you. I suggest you try to Update boot images and see if you have any errors. If you have any, those errors occured while you did the update. Hope this help! Jonathan

Nicholas Baldwin

07.14.2016 AT 10:37 AM
Thanks Jonathan for the reply but none of those options have worked 🙁 I have even now deleted and recreated/uploaded the Boot.WIM and still will not boot to PXE. I have not added drivers into the mix either, not yet (haven't needed drivers with this new WinPE10) Have tested this on 3 laptops now, 1 of which is brand new out of the box. I am wondering if this latest update broke PXE. because it worked before that. date released was 5/27/16 so I assume it would have been fixed if that was the case. Rebooted the host server. I have ran out of ideas that is why I am posting here which is a first for me. I normally find all the answers here without having to post. Thanks Nick


07.26.2016 AT 03:42 PM
Did you get this worked out?? Did you log on to the Distribution point you are trying to pxe boot to and verify Windows Deployment Services is still installed? I've seen that happen before and Config Manager won't reinstall it so you have to do it manually. Just a thought....


06.21.2016 AT 06:01 AM
Great Guide! as always. My enviroment is now at 1602. Everything seems to work just fine...But i cannot use "Serving Plans" under "Windows 10 Servicing" to select Updates as its not showing any on the Preview Updates. I do see 265 items under 'All Windows 10 Updates'. Snippet of Ruleengine.log: The rule resulted in no updates being found. Skip deployment creation or update... SMS_RULE_ENGINE 6/21/2016 12:57:36 PM 936 (0x03A8) Enforcing Create Deployment Action SMS_RULE_ENGINE 6/21/2016 12:57:36 PM 936 (0x03A8) Create Deployment Rule Action XML is: WKM00043truefalse7Days0HoursCheckedUncheckedUncheckedfalsefalsefalsefalsetruetruetruefalsefalsetruefalse02WeeksfalseHideAlltrue1falsefalse SMS_RULE_ENGINE 6/21/2016 12:57:36 PM 936 (0x03A8) Invalid boolean value SMS_RULE_ENGINE 6/21/2016 12:57:36 PM 936 (0x03A8) The rule resulted in no updates being found. Skip deployment creation or update... SMS_RULE_ENGINE 6/21/2016 12:57:36 PM 936 (0x03A8) Please advise.


05.11.2016 AT 08:00 AM
I have a multi-site hierarchy (CAS/multiple primaries/multiple secondary servers) and want to upgrade the primary sites in a controlled way. I believe service windows on the site servers is the answer and I could set the service window to say 5 mins to prevent the update from applying. Once I'm ready to update a particular site I would change the service window to a timeframe that would be sufficient for the installation to complete Would that work?


05.09.2016 AT 08:30 AM
Has anyone had issues getting WinPE peer caching working? I set the peer cache client setting and variables on a collection and push the download wim task to machine A. When Machine B pxe's it finds machine A (Adding Peer Content Server : http://machineA) and verifies the wim is there. However when it does its Prioritized Locations it adds the http://machineA and the mcs://sccmserver and in the end choses the SCCM server to pull from. Is there a setting where I can force it to use the Peer Cache first and then fall back to the dist point if it can't find the wim? The CAS.log on the MachineA and the smsts.log on MachineB shows everything is good, its just that MachineB picks the Dist point rather than the Peer Cache on MachineA? Thanks!

selim atmaca

04.29.2016 AT 09:08 AM
Thanks for this great post. Worked without any problems.

Stephanie Machicek

04.27.2016 AT 02:37 PM
Thank you so much for providing your upgrade guides. We follow them during every upgrade. I have a question about a feature that we are not seeing with the 1602 upgrade. Per this article (, Software Center is now supposed to have an Application tab. Which sounds like application catalog could no longer be needed. We are not seeing the Application tab. Have you or anyone noticed this? We were wondering if there was some configuration setting we needed to set in order to see the tab. We use application catalog extensively so we do have user-available apps. If someone has the answer or can point us in the right direction, it would be appreciated.

Stephanie Machicek

04.27.2016 AT 02:53 PM
Well we just figured out the answer. In Client Settings | Computer Agent | check "Use new Software Center."

Benoit Lecours

04.28.2016 AT 06:29 AM
That's it ! We documented it in this blog post :


04.26.2016 AT 03:03 PM
I am running into an issue where the upgrade completes successfully, but are running into issues with the management point keeps going to a critical state. The root of the problem appears to be that the UALSVC and SMS Agent Host services keep stopping. If I restart the services, the MP comes back to an OK state for about an hour, then they stop. Has anyone else run into this issue. I really want to apply the 1602 update, but unfortunately this issue is preventing me from completing the upgrade.


07.14.2016 AT 05:13 PM
I have this same issue after upgrading to 1602 hotfix. SMS agent host service keeps stopping and MP goes to critical after that. If i start it again, it comes online. Any fixes found for this? PLease let me know


06.06.2016 AT 07:26 AM
Hi, Encountered the same behavior after upgrading a 1511 site to 1602... check sitecomp.log and have a look if there are any remaining bootstrap tasks that fail and get retried peroidically. In my case this was the case and when it was trying to stop the winmgmt service and the dependant ones (like ccmexec), tmlisten (the TMicro Office Scan Listener) couldn't be stopped and the operation errored out..... resulting in a retry after some time. My "solution" was keeping an eye on the sitecomp.log, restarting the sitecomp service and killing tmlisten.exe at the time it wanted to stop it.


04.29.2016 AT 01:46 AM
Hello John, I encounter the same problem. Do you have solved this issue? Thx.

Abhishek Kumar

04.21.2016 AT 06:02 AM
Hi Keywan, Did you get the solution for Waiting for changes to the “C:\Program Files\Microsoft Configuration Manager\inboxes\” directories, updates will be polled in 600 seconds


04.20.2016 AT 09:02 AM
From tomorrow i'm gonna lose weight. Summer is comming girls! Who starts with me? I found a good method in google and want to give it a try, simply search in go0gle: fitMarikka advices - burn fat

Victor Lam

04.13.2016 AT 03:11 PM
Great guide, regarding boot image. i do not see any new boot image being add. how should i determine if i have latest boot image?

Jonathan Lefebvre

04.15.2016 AT 10:09 AM
Hi Victor, It doesn't create a new Boot Image. It updates the default boot images (x86 and x64). Have a look in this post for details about the boot images updates. Under the section : Automatic Package Updates and Distribution Jonathan


04.12.2016 AT 02:02 PM
Just upgraded to 1602. Regarding the client packages and having them distributed to your DP, when I go to Distribute Content and go to Content Destination and Add Distribution Point, I don't see my DP. What could be the issue here?


04.13.2016 AT 04:16 PM
Well I guess the client packages had already been distributed, as client updates are happening. Guess that's the reason why I didn't see the DP. Must have automatically happened as I didn't do this myself.

Jonathan Lefebvre

04.15.2016 AT 10:16 AM
Hi Joerockt, The client package is by default distributed to all DP. That is why you don't see your DP when you go to Add Distribution Point. You can see which DP as a package distributed to under Monitoring / Distribution Status / Content Status / . After the upgrade to 1602, the client package trigger an automatic Update Distribution Point on the client package. You can have more details on automatic packages update in this post : Thanks Jonathan


04.05.2016 AT 09:13 PM
Hi, I've just updated to 1602 and want to start taking advantage of the automatic client upgrade feature. I want to do this for both workstations and servers, however I want to confirm that the client upgrade will only during the maintenance windows defined for our servers. I see in the notes on the Client Upgrade tab that it states the upgrade will only occur during the maintenance window - however have you tested that this definitely occurs? Thanks

Benoit Lecours

04.06.2016 AT 11:23 AM
Yes, ACU is taking MW into account. Use the Pre-Production collection to test it.


04.07.2016 AT 07:47 PM
Thanks Benoit, does it only schedule the client update to occur during a maintenance window or does it schedule it randomly (within the time frame you specify) and it just holds the install until the next maintenance window? I want to make sure all servers update, not just those where the scheduled time happens to co-incide with the maintenance window.


03.30.2016 AT 01:07 PM
The docs were upgraded on the 14th. You only need to run the update on the CAS. The important bit: "It installs at the central administration site (if you have one), and at primary sites automatically. You can control when each primary site server is allowed to update its infrastructure by using Service Windows for site servers." Source:


03.30.2016 AT 03:14 AM
Hi, A quick check, is .net 4.5.2 still the prerequisite for win7 client? Or . Net 4.6.1? Thanks, Yeo

Ben JohnsonWY

03.24.2016 AT 06:58 PM
What if your network with SCM is not on the Internet? Sigh.

Benoit Lecours

03.24.2016 AT 08:45 PM
You can use the service connection tool for that.


06.03.2016 AT 10:36 AM
Yeah, that's not a good solution. I have SCCM systems that I can NOT transfer information, any information, from them to an internet connected machine. How do we go about getting SCCM updates? Is there no way to just download the entire 1602 update as an ISO?