How to Upgrade SCCM Current Branch v1806
This document is a step by step SCCM 1806 upgrade guide. SCCM 1806 is released and available for general public. The SCCM 1806 upgrade guide contains the steps to upgrade configuration manager current branch to SCCM 1806. This is probably the 9th release of current branch.
There have been lot of features introduced with every release of configuration manager current branch. SCCM 1806 update also comes with some great features and fixes.
As it’s a known fact that updates and hotfixes are always available right in the console. SCCM 1806 update is available as an in-console update. To install SCCM 1806 update, it must be running one of these versions of SCCM 1706, 1710, or 1802.
As mentioned earlier SCCM 1806 comes with new features. While it’s not only new features but it also includes enhancements or fixes reported in previous releases of current branch versions. I will list down some of the best SCCM 1806 features and we will then proceed with installation steps.
- Site server high availability feature
- Uninstall application on approval revocation
- New Custom tab for webpage in Software Center
- Deploy PXE-enabled distribution point without Windows Deployment Services
- CMTrace is now installed along with client agent
- Configuration Manager Toolkit is now included
- View Currently logged-on user
- Feedback can be submitted from console
- Network congestion control for distribution points
- Partial download support in client peer cache
- Feature to configure remote content library for the site server
- Improvements to phased deployments
- Improved WSUS maintenance
- Deploy software updates without content
- New software updates compliance report
- Deploy third-party software updates
- Improvements to co-management
- New product life-cycle dashboard
1806 supports only Windows 2012+ and SQL 2012 SP3+ versions.
|SCCM version||Supported SQL Server Versions||Role|
|CB v1806||SQL Server 2017: Standard, Enterprise
SQL Server 2016 SP2: Standard, Enterprise
SQL Server 2016 SP1: Standard, Enterprise
SQL Server 2016: Standard, Enterprise
SQL Server 2014 SP3: Standard, Enterprise
SQL Server 2014 SP3: Standard, EnterpriseSQL Server 2012 SP3: Standard, Enterprise
SQL Server 2012 SP4: Standard, Enterprise
|A central administration site
A primary site
A secondary site
Support for SCCM Current branch.
When a site installs this update, Configuration Manager automatically installs .NET Framework 4.5.2. When this prerequisite isn’t already installed, the site installs it on each server that hosts one of the following site system roles:
- Management point
- Service connection point
This installation can put the site system server into a reboot pending state and report errors to the Configuration Manager component status viewer. Additionally, .NET applications on the server might experience random failures until the server is restarted.
The version of the Windows 10 Assessment and Deployment Kit (ADK) should be supported for Configuration Manager version 1806.
Before starting an update on a site, resolve all operational issues for the site server, the site database server, and site system roles that are installed on remote computers. A site update can fail due to existing operational problems.
Before installing an update for Configuration Manager, install any critical OS updates for each applicable site system. These servers include the site server, site database server, and remote site system roles. If an update install requires a restart, restart the applicable servers before starting the upgrade.
Configuration Manager can’t successfully update a primary site that has a database replica for management points enabled. Before installing an update for Configuration Manager, disable database replication.
Before installing the update, disable any site maintenance task that might run during the time the update process is active. For example, but not limited to:
- Backup Site Server
- Delete Aged Client Operations
- Delete Aged Discovery Data
When a site database maintenance task runs during the update installation, the update installation can fail. Before disable a task, record the schedule of the task so that it can restore its configuration after the update has been installed.
Before updating a site, stop antivirus software on the Configuration Manager servers.
Before installing an update on a site, back up the site database at the Primary site. This backup ensures a successful backup to use for disaster recovery.
2.2. SCCM 1806 Upgrade
Open the SCCM console and go to Administration > Updates and Servicing. If you don’t find the update 1806, click Check for updates button. Once the update is available, download the update.
- If the update is not downloading, click on the button Download on the upper node. The update state will change to Downloading
- You can follow the download in log or by going to Monitoring / Updates and Servicing Status, right-click your Update Name and selectShow Status
- The process will first download .CAB file and will extract the file in the EasyPayloadfolder in your SCCM installation directory.
- GUID: 5b823327-92d9-4908-a24c-8d8c6625f407
- It can take up to 15 minutes to extract all files.
Before launching the update, we recommend launching the prerequisite check first.
- Open the SCCM console
- Go to Administration \ Updates and Servicing
- Right-click the Configuration Manager 1806 update and select Run prerequisite check
- Nothing will happen, the prerequisite check runs in the background and all menu are unavailable during the check
- One way to see progress is by viewing C:\ConfigMgrPrereq.log
- You can also monitor prerequisite check by going to Monitoring / Update and Servicing Status, right-click your Update Name and select Show Status
- When completed the State column will show Prerequisite check passed
We are now ready to launch the SCCM 1806 update. At this point, plan about 45 minutes to install the update.
- Right-click the Configuration Manager 1806 update and select Install Update Pack
- On the General tab, click Next
- On the Featurestab, checkboxes on the features you want to enable during the update
- Don’t worry, if you don’t select one of the features now and want to enable it later, you’ll be able to so by using the console Administration \ Updates and Servicing \ Features
In the Client Update Options, select the desired option for your client update
- This option allows updating only client’s member of a specific collection.
- On the License Termstab, accept the license terms and click Next
- On the Summarytab, review your choices, click Next and close the wizard on the Completion tab
The whole process can take up to a minute, but the installation begins on the back end.
- We suggest you monitor the progress, by navigating to Monitoring / Updates and Servicing Status, right-click your Update Nameand select Show Status
The status is not updated in real time. Use the Refresh button to update.
- Open the SCCM log SCCM Installation Directory\Logs\CMUpdate.log with CMtrace.
- When completed, you’ll notice the message There are no pending update package to be processed in the log file
- Monitoring / Updates and Servicing Status, right-click your Update Nameand select Show Status, the last step will be Installation Succeeded
- Refresh theUpdates and Servicing node in Administration, the State column will be Installed
As a previous Cumulative update, the console has an auto-update feature. At console opening, if the console is not running the latest version, we will receive a warning and the update will start automatically.
- Since all update’s 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
- Click OK, console restart and update will start automatically
- Wait for the process to complete. The process can be followed here inC:\ConfigMgrAdminUISetup.log and C:\ConfigMgrAdminUISetupVerbose.log. Once completed, the console will open, and you’ll be running the latest version.
Once successful installation of current Branch 1806 on the Primary server, Management Points and IBCM servers should get updated on their own as per the process.
After setup is completed, verify the build number of the console. If the console upgrade was successful, the build number will be X and the version is now Version 1806.
Beginning with 1802, this is a new version nomenclature for the console. The console will no longer include the main build number (8634). The last 2 numbers refer to the admin console build number. For example, in Configuration Manager version 1806 the initial site version is 5.0.8692.1000, and the initial console version is 5.1806.1074.1200. The build (1074) and revision (1200) numbers may change with future hotfixes to the 1806 release.
- Go to Administration \ Site Configuration \ Sites
- Right-click your site and select Properties
- Verify the Versionand Build number
The client version will be updated to 5.00.8692.1003.
There will be 2 client packages would be updated:
- Navigate to Software Library \ Application Management \ Packages
- Check if the update is successful, otherwise, select both packages and initiate a Distribute Contentto your distribution points
Boot images will automatically update during setup.
Go to Software Library / Operating Systems / Boot Images
- Select your boot image and check the lastContent Status date. It should match your setup date.
Once site has completed update a primary site, reconfigure the database replica for management points that you uninstalled before you updated the site.
If there are any disabled database maintenance tasks at a site before installing the update, reconfigure those tasks. Use the same settings that were in place before the update.
If there was any in use third party extensions like Right Click Tool, to Configuration Manager, update them to the latest version to support Configuration Manager version 1806.
Use the Update Distribution Points action for any boot image that you use, whether its a default or custom boot image. This action makes sure that clients can use the latest version. Even if there isn’t a new version of the Windows ADK, the Configuration Manager client components may change with an update. If you don’t update boot images and media, task sequence deployments may fail on devices.
Plan to test a new Configuration Manager client version in a pre-production collection before upgrading the rest of the site with it. Once this is done, only devices that are part of the test collection are upgraded. Once the upgrade is successful, we can promote the client, which makes the new version of the client software available to the rest of the site.
There are 3 basic steps to testing clients in pre-production.
- Configure automatic client upgrades to use a pre-production collection.
- Install a Configuration Manager update that includes a new version of the client.
- Promote the new client to production.
To configure automatic client upgrades to use a pre-production collection.
- Set up a collectionthat contains the computers you want to deploy the pre-production client to.
- In the Configuration Manager console open Administration> Site Configuration > Sites and choose Hierarchy Settings.
On the Client Upgrade tab of the Hierarchy Settings Properties:
- Select Upgrade all clients in the pre-production collection automatically using pre-production client
- Enter the name of a collection to use as a pre-production collection
Once upgrade is successful, the installation of SCCM agents on all Endpoints can be started.
This space describes the issues that are fixed and additional hotfixes that are included in the current update rollup for Microsoft System Center Configuration Manager current branch, version 1806.
An update is available to administrators who opted in through a PowerShell script to the first wave (early update ring) deployment for SCCM current branch, version 1806. You can access the update in the Updates and Servicing node of the SCCM console. There are separate SCCM 1806 Hotfixes available for slow and fast rings.
This update KB 4346645 does not apply to sites that downloaded version 1806 on August 10, 2018, or a later date.
An update is available to address important upgrade-related issues for SCCM current branch, version 1806. The issues that are described in this article apply only to sites that upgraded to version 1806 before August 24, 2018.