The following article is a step by step upgrade guide on how to upgrade your current version of SCCM Current Branch to SCCM 1806. The announcement for Current Branch 1806 for System Center Configuration Manager can be found here and was made on July 31st 2018. To install the SCCM 1806 upgrade, you must have installed at least SCCM CB 1706, 1710 or 1802 and cannot proceed if you are still running SCCM 2012. The entire upgrade process can be done mostly from within the console. Additionally, it is important to stay up-to date with your overall infrastructure so you have a seamless upgrade experience.

Note: You must install this update first on primary sites. Further more pre-existing secondary sites should be manually updated.

SCCM 1806 New Features and Fixes

Lots of new features have been added within this update and you can read more about the SCCM 1806 updates here but the biggest one being CMPivot which is handy in building real-time script capability. CMPivot is a new in-console utility that provides access to realtime state of devices in your environment.

New Features

Get and Stay Current

Improvements to phased deployments

  • You can now create phased deployments for applications.
  • Phased deployments now have a native monitoring experience.
  • You can create a phased deployment with manually configured phases for a task sequence.
  • You can now configure the rollout in each phase of a phased deployment to happen gradually.

Improved Windows Software Update Services (WSUS) maintenance – Use the WSUS cleanup wizard to decline updates that are expired according to the supersedence rules defined on the software update point component properties.

Deploy software updates without content – You can now deploy software updates to devices without first downloading and distributing content to distribution points. This is useful when you are dealing with extremely large update content, or when you always want clients to get content from the Microsoft Update cloud service.

New software updates compliance report – The Compliance 9 – Overall health and compliance report lets you filter compliance results for a specific software update group by “healthy” clients.

Product lifecycle dashboard – The new product lifecycle dashboard shows you the state of the Microsoft Lifecycle Policy for Microsoft products installed on devices managed with Configuration Manager. You can also see information about Microsoft products in your environment, supportability state, and support end dates.

Third-party software updates – You can subscribe to partner catalogs in the Configuration Manager console and publish the updates to WSUS using the new third-party software updates feature. You can then deploy these updates using the existing software update management process.

Cloud Powered

Improvements to co-management – this release includes the following improvements to co-management

  • You have three new workloads available to transition to Intune using co-management: device configuration, Office 365 deployments, mobile apps.
  • When you switch a co-management workload, the co-managed devices automatically synchronize MDM policy from Microsoft Intune.
  • Co-management now supports connecting more than one Configuration Manager environment to the same Intune tenant.

Cloud management dashboard – The new cloud management dashboard provides you with a centralized view for cloud management gateway (CMG) usage. Additionally, you can use the CMG connection analyzer for real-time verification to aid troubleshooting.

Download content from a CMG – Previously, you had to deploy a cloud distribution point and CMG as separate roles. A CMG can now also serve content from Azure storage to clients.


Site server high availability – High availability for a standalone primary site server role allows you to install an additional Configuration Manager site server in passive mode. A site server in passive mode is available for immediate use, when needed.

Uninstall application on approval revocation – After enabling the optional feature Approve application requests for users per device, when you deny the request for the application, the client uninstalls the application from the user’s device.

Custom tab for webpage in Software Center – You can use client settings to create a customized tab to open a webpage in Software Center. This allows you to show content to your end users in a consistent, reliable way.

Partial download support in client peer cache to reduce WAN utilization – Client peer cache sources can now divide content into parts. These parts minimize the network transfer to reduce WAN utilization.

Enable distribution points to use network congestion control – Windows Low Extra Delay Background Transport (LEDBAT) is a feature of Windows Server to help manage background network transfers. For distribution points running on supported versions of Windows Server, you can enable an option to help adjust network traffic so that clients only use network bandwidth when it’s available.

Configure a remote content library for the site server – You can now relocate the content library to another storage location to free up hard drive space on your central administration or primary site servers or to configure site server high availability.

View the currently signed on user for a device – You can see a column for the currently logged on user now displayed by default in the Devices node of the Assets and Compliance workspace.

Improvements to PXE-enabled distribution points – You now have the option to deploy PXE-enabled distribution point without Windows Deployment Services (WDS). This change allows you to use a client or server OS, including Windows Server Core as your PXE-enabled distribution point.

CMTrace installed with client – The CMTrace log viewing tool is now automatically installed along with the Configuration Manager client and added to the client installation directory.

Configuration Manager Toolkit – The Configuration Manager server and client tools are now included on the server. Find them in the CD.Latest\SMSSETUP\Tools folder on the site server.

Submit feedback from the Configuration Manager console – Send a smile! You can now directly tell the Configuration Manager team about your experiences by sending feedback from the Configuration Manager console.

Support for SCCM Current Branch Version

Make sure that you apply the Current Branch updates before you fall into an unsupported SCCM version as displayed in the diagram below. Additionally, you can read about the support end date of the prior versions on the following Microsoft Technet article.

Version  History

Version Availability Date Support End Date
1806 July 31, 2018 January 31, 2020
1802 March 22, 2018 September 22, 2019
1710 November 20, 2017 May 20, 2019
1706 July 31, 2017 July 31, 2018
1702 March 27, 2017 March 27, 2018
1610 November 18, 2016 November 18, 2017
1606 July 22, 2016 July 22, 2017
1602 March 11, 2016 March 11, 2017
1511 December 8, 2015 December 8, 2016

Windows and SQL Support

As a pre-requisite to installation / upgrade, make sure that you are running a supported Operating System and SQL version. Older builds of SCCM give a warning during the prerequisite check, but starting with version 1802 and onward you will receive an error which will prevent the installation from continuing. SCCM 1806 will continue to give you the same warning:

“1806 supports only Windows 2012+ and SQL 2012 SP3+”

SCCM 1806 Server Upgrade

If you have done previous upgrades, the steps to upgrade SCCM Configuration Manager 1806 remain almost the same.

Pre-Requisite Check

The SCCM 1806 update is not yet available for everyone within the console. If you don’t want to wait for the advertised release you would need to run the Fast-Ring script to make it appear in the console. The direct link for downloading the script from Technet can be found here. Once downloaded, follow the following steps to make the Update available within the console.
  1. Extract the downloaded file to C:\FastRingScript_1806\
  2. Launch PowerShell under an elevated command prompt
  3. Run the EnableFastUpdateRing1806.ps1 script below where SiteServer refers to the CAS or standalone primary site server
    • .\EnableFastUpdateRing1806.ps1 <SiteServer_Name|SiteServer_IP>

  4. Force a check for the update.
    • Go to Administration > Overview > Updates and Servicing
    • Right click “Check for Updates”.
    • On the following notification screen, Select OK.
    • Note: You may need to try “Check for Updates” more than once if the package is not downloaded on the first try.
  5. The new 1806 Update should now be available in the Configuration Manager Console.

Before launching the actual update, it is recommended to launch the prerequisite check first. The prerequisite checklist for the Microsoft Documentation can be found here.

  1. Open the SCCM console
  2. Navigate to Administration > Updates and Servicing
  3. Right-click the Configuration Manager 1806 update
  4. Select Run prerequisite check

Note: Nothing will actively happen on screen as the prerequisite check runs in the background and all the menus are unavailable during the check. Use the ConfigMgrPrereq.log to view progress of the prerequisite check.

  1. The prerequisite check monitoring can also be performed by navigating to Monitoring > Update and Servicing Status
  2. Right-click your Update Name and Select Show Status
  3. The process will first download .CAB file and will extract the file in the EasyPayload folder in your SCCM installation directory.
    • GUID : 5b823327-92d9-4908-a24c-8d8c6625f407
    • Note: It can take up to 15 minutes to extract all files
  4. When completed the State column will show Prerequisite check passed.
    • Note: This can also be verified in the C:\ConfigMgrPrereq.log

Launching the SCCM 1806 Update

At this point you should be able to perform the actual upgrade once the Prerequisite check has passed.

Note: The overall upgrade takes about 40 – 60 minutes to perform. The upgrade in my lab upgraded took close to 46 mins. Keep in mind the actual process kick off can take over 10 minutes post completing the wizard. Do not reboot or restart any services during this period or your update will be stuck in “Prerequisite check passed” status.

  1. Navigate to Monitoring > Update and Servicing Status
  2. Right-click the Configuration Manager 1806 update and Select Install Update Pack
  3. On the General tab, Click Next
  4. On the Features tab, check-boxes on the features you want to enable during the update.
    • Note: If you don’t select one of the features now and want to enable it later, you’ll be able to so by navigating to the console Administration > Updates and Servicing > Features.
  5. In the Client Update Options, select the desired option for your client update.
    • Note: This option allows updating only clients member of a specific collection.
  6. On the License Terms tab, accept the license terms, Select the Software Assurance expiration date and Click Next.
    • Note: To learn more about Software Assurance on how it may apply to you environment check the Microsoft link here.
  7. On the Summary tab, review your choices, click Next and close the wizard on the Completion tab.
    • Note: The whole process takes less than a minute, but the installation silently begins in the back end and may take upto 10 minutes to start the update.
  8. The wizard will prepare the configuration. No action is needed at this step.
  9. The following screen will display a summary of the update package. Select Next to close the wizard.
  10. During installation, the State column changes to an Installing state.
  11. Navigate to Monitoring > Updates and Servicing Status
  12. Right-click your Update Name and Select Show Status
    • Note: The status is not updated in real time. Use the Refresh button to update.
  13. Open the SCCM log SCCM Installation Directory\Logs\CMUpdate.log to monitor the overall update.
  14. When completed, you’ll notice the message There are no pending update package to be processed in the log file.
  15. The last step should show as Installation Succeeded.
  16. Refresh the Updates and Servicing node in Administration, the State column will show as Installed.

Certain log files found in SCCM Installation Directory\Logs can be used for monitoring the overall process by using CMTrace.

  1. CMUpdate.log
  2. dmpdownloader.log
  3. hman.log
  4. distmgr.log
  5. distmgr.log
  6. sitecomp.log
  7. smsexec.log
  8. rcmctrl.log

Please refer here about specific log details.

SCCM 1806 Client Upgrade

Version Verification

Console version

Outdated consoles when opened should pop up a warning for a new console being available.

  1. Click OK to proceed
  2. The console should display the downloading files notification.
  3. The installation progress bar should display while the client installs

Note: You can follow the progress within:

  • C:\ConfigMgrAdminUISetup.log
  • C:\ConfigMgrAdminUISetupVerbose.log

Once completed, the console should open and you should be running the latest version

  • Click on core Console Menu
  • Select About Configuration Manager
  • Verify the Version, Console and Site Version
    • Version – 1806
    • Console – 5.1806.1074.1200
    • Site Version – 5.0.8692.1000

Server side

  • Navigate to Administration > Site Configuration > Sites
  • Right-click your site and Select Properties
  • Verify the Version and Build number
    • Version – 5.0.8692.1000
    • Build – 8692

SCCM 1806 Client Package Distribution

Usually there are 2 client packages that are updated:

  1. Configuration Manager Client Package
  2. Configuration Manager Client Piloting Package
  • Navigate to Software Library > Application Management > Packages
  • Check if the update was successful else select both packages and initiate Distribute Content to your distribution points.

Client  version

  • Open the SCCM Console
  • Navigate to Administration > Site Configuration > Sites
  • Click the Hierarchy Settings in the top ribbon
  • Select Client Upgrade tab
  • Check the Upgrade all client in the hierarchy using the production client and Automatically distribute client installation package to distribution points that are enabled for prestaged content.
  • Use the SCCM collection definition or Client version reporting in SQL as shown below to monitor your upgrade progress.

Note: Client upgrades over a large fleet will take time to upgrade but the older clients will continue to work with the upgraded server until then.

Client version – 5.00.8692.1003

Boot Images

Boot images will automatically update during this setup.

  • Navigate to Software Library > Operating Systems > Boot Images
  • Select your boot image and check the last Content Status date. They should match your setup date of upgrade.


SCCM Collection

SQL Reporting

You can read more about Client version reporting in SQL here.