The following article is a step by step upgrade guide on how to upgrade your current version of SCCM Current Branch to SCCM 1810. The announcement for Current Branch 1810 for System Center Configuration Manager can be found here and was made on November 27st 2018. To install the SCCM 1810 upgrade, you must have installed at least SCCM CB 1710, 1802 or 1806 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 1810 New Features and Fixes
Lots of new features have been added within this update and you can read more about the SCCM 1810 updates here. In this release Microsoft has focused on simplification of the Configuration Manager infrastructure with added functionality to make it easier to stay up to date with Windows and Office. Microsoft continues to introduce new cloud powered value with improvements to co-management and new options to apply Conditional Access to ConfigMgr managed PCs.
The big feature that I am excited about is the next set of enhancements to site server high availability. Historically you could add redundancy to most of the roles in Configuration Manager by having multiples of these roles in your environment. The site server was an exception. In Configuration Manager version 1806, high availability for the site server role added an additional site server in passive mode for standalone sites. Update 1810 adds hierarchy support so Central administration sites and child primary sites can now have an additional site server in passive mode. The site server in passive mode can be on-premises or cloud-based in Azure.
This feature brings the following benefits
- Redundancy and high availability to the site server role.
- You can more easily change the hardware or operating system of the site server.
- You can more easily move your site server to Azure IaaS.
Get Current/Stay Current
- Specify the drive for offline OS image servicing – Now you can specify the drive that Configuration Manager uses when adding software updates to OS images and OS upgrade packages.
- Task sequence support for boundary groups – When a device runs a task sequence and needs to acquire content, it now uses boundary group behaviors similar to the Configuration Manager client.
- Improvements to driver maintenance – Driver packages now have additional metadata fields for Manufacturer and Model which can be used to tag driver packages for general housekeeping.
- Phased deployment of software updates – You can now create phased deployments for software updates. Phased deployments allow you to orchestrate a coordinated, sequenced rollout of software based on customizable criteria and groups.
- Management insights dashboard – The Management Insights node now includes a graphical dashboard. This dashboard displays an overview of the rule states, which makes it easier for you to show your progress.
- Management insights rule for peer cache source client version – The Management Insights node has a new rule to identify clients that serve as a peer cache source but haven’t upgraded from a pre-1806 client version.
- Improvement to lifecycle dashboard – The product lifecycle dashboard now includes information for System Center 2012 Configuration Manager and later.
- Windows Autopilot for existing devices task sequence template – This new native Configuration Manager task sequence allows you to reimage and re-provision an existing Windows 7 device into an AAD joined, co-managed Windows 10 using Windows Autopilot user-driven mode.
- Improvements to co-management dashboard – The co-management dashboard is enhanced with more detailed information about enrollment status.
- Required app compliance policy for co-managed devices – You can now define compliance policy rules in Configuration Manager for required applications. This app assessment is part of the overall compliance state sent to Microsoft Intune for co-managed devices.
- SMS Provider API – The SMS Provider now provides read-only API interoperability access to WMI over HTTPS.
- Site system on Windows cluster node – The Configuration Manager setup process no longer blocks installation of the site server role on a computer with the Windows role for Failover Clustering. With this change, you can create a highly available site with fewer servers by using SQL Always On and a site server in passive mode.
- Configuration Manager administrator authentication – You can now specify the minimum authentication level for administrators to access Configuration Manager sites.
- Improvements to CMPivot – CMPivot now allows you to save your favorite queries and create collections from the query summary tab. Over 100 new queryable entities added, including for extended hardware inventory properties. Additional improvements to performance.
- New client notification action to wake up device – You can now wake up clients from the Configuration Manager console, even if the client isn’t on the same subnet as the site server.
- New boundary group options – Boundary groups now include two new settings to give you more control over content distribution in your environment.
- Improvements to collection evaluation – There are two changes to collection evaluation scheduling behavior that can improve site performance.
- Approve application requests via email – you can now configure email notifications for application approval requests.
- Repair applications – You can now specify a repair command line for Windows Installer and Script Installer deployment types.
- Convert applications to MSIX – Now you can convert your existing Windows Installer (.msi) applications to the MSIX format.
- Improvement to data warehouse – You can now synchronize more tables from the site database to the data warehouse.
- Support Center – Use Support Center for client troubleshooting, real-time log viewing, or capturing the state of a Configuration Manager client computer for later analysis. Find the Support Center installer on the site server in the cd.latest\SMSSETUP\Tools\SupportCenter folder.
Deprecated features and operating systems
Starting on August 14, 2018, the hybrid mobile device management feature is deprecated.
Support for System Center Endpoint Protection (SCEP) for Mac and Linux (all versions) ends on December 31, 2018. Availability of new virus definitions for SCEP for Mac and SCEP for Linux may be discontinued after the end of support.
Classic service deployments in Azure are now deprecated in Configuration Manager. Start using Azure Resource Manager deployments for the cloud management gateway and the cloud distribution point.
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||Availability Date||Support End Date|
|1810||Nov 27, 2018||May 27, 2020|
|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 1810 will continue to give you the same warning:
“1810 supports only Windows 2012+ and SQL 2012 SP3+”
SCCM 1810 Server Upgrade
If you have done previous upgrades, the steps to upgrade SCCM Configuration Manager 1810 remain almost the same.
The SCCM 1810 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.
- Extract the downloaded file to C:\FastRingScript_1810\
- Launch PowerShell under an elevated command prompt
- Run the EnableFastUpdateRing1810.ps1 script below where SiteServer refers to the CAS or standalone primary site server
- Force a check for the update.
- The new 1810 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.
- Open the SCCM console
- Navigate to Administration > Updates and Servicing
- Right-click the Configuration Manager 1810 update
- 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. You might also get a warning for TLS 1.2 support. In those occurrences a higher version of SQL Server Native Client was required. Use the ConfigMgrPrereq.log to view progress of the prerequisite check.
- The prerequisite check monitoring can also be performed by navigating to Monitoring > Update and Servicing Status
- Right-click your Update Name and Select Show Status
- The process will first download .CAB file and will extract the file in the EasyPayload folder in your SCCM installation directory.
- When completed the State column will show Prerequisite check passed.
Launching the SCCM 1810 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.
- Navigate to Monitoring > Update and Servicing Status
- Right-click the Configuration Manager 1810 update and Select Install Update Pack
- On the General tab, Click Next
- 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.
- 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.
- 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.
- 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.
- The wizard will prepare the configuration. No action is needed at this step.
- The following screen will display a summary of the update package. Select Next to close the wizard.
- During installation, the State column changes to an Installing state.
- Navigate to Monitoring > Updates and Servicing Status
- Right-click your Update Name and Select Show Status
- Open the SCCM log SCCM Installation Directory\Logs\CMUpdate.log to monitor the overall update.
- When completed, you’ll notice the message There are no pending update package to be processed in the log file.
- The last step should show as Installation Succeeded.
- 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.
Please refer here about specific log details.
SCCM 1810 Client Upgrade
Outdated consoles when opened should pop up a warning for a new console being available.
- Click OK to proceed
- The console should display the downloading files notification.
- The installation progress bar should display while the client installs
Note: You can follow the progress within:
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 – 1810
- Console – 5.1810.1075.1300
- Site Version – 5.0.8740.1000
- Navigate to Administration > Site Configuration > Sites
- Right-click your site and Select Properties
- Verify the Version and Build number
SCCM 1810 Client Package Distribution
Usually there are 2 client packages that are updated:
- Configuration Manager Client Package
- 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.
- 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.8740.1003
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.
where SMS_R_System.ClientVersion != '5.00.8740.1003'
You can read more about Client version reporting in SQL here.