The following article is a step by step upgrade guide on how to upgrade your current version of SCCM Current Branch to SCCM 1902. The announcement for Current Branch 1902 for System Center Configuration Manager can be found here and was made on March 27th 2019. To install the SCCM 1902 upgrade, you must have installed at least SCCM CB 1710, 1802, 1806, 1806 or 1810 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 1902 New Features and Fixes
Lots of new features have been added within this update and you can read more about the SCCM 1902 updates here.
- Cloud Management Gateway (CMG) can be associated with boundary groups – Cloud Management Gateway deployments can now be associated with boundary groups to allow clients to default or fallback to the CMG for client communication according to boundary group relationships.
- Stop cloud service when it exceeds threshold – Configuration Manager can now stop a cloud management gateway (CMG) service when the total data transfer goes over your limit.
- Improvements to application approvals via email – When users request applications from Software Center, the email notification will now include their comments.
Configuration Manager console
- Improvements to Configuration Manager console – Based on customer feedback aka the Cabana sessions at the Midwest Management Summit (MMS) Desert Edition 2018, this release includes several improvements to the Configuration Manager console.
- View recently connected consoles – You can now view the most recent connections for the Configuration Manager console. The view includes active connections and those that recently connected.
- View first monitor only during Configuration Manager remote control session – When connecting to a client with two or more monitors, a remote tools operator can now choose between seeing all monitors and the first monitor only.
- Search device views using MAC address – you can now search for a MAC address in a device view of the Configuration Manager console.
- Replace toast notifications with dialog window – When deployments need a restart or software changes are required, you now have the option of using a more intrusive dialog window to replace toast notifications on the client
- Configure default views in Software Center – You can now customize your end user’s default application layout and default application filter in Software Center.
- Improvements to task sequence media creation – When you create task sequence media, you can now customize the location that the site uses for temporary storage of data and add a label to the media.
- Improvements to Run PowerShell Script task sequence step – The Run PowerShell Script task sequence step now allows you to specify a timeout value, alternate credentials, a working directory and success codes.
- Import a single index of an Operating System Image – When importing a Windows image (WIM) file to Configuration Manager, you can now specify to automatically import a single index rather than all image indexes in the file.
- Progress status during in-place upgrade task sequence – You now see a more detailed progress bar during a Windows 10 in-place upgrade task sequence.
- Client Health Dashboard – You can now view a dashboard with information about the client health of your environment. View your client health, scenario health, common errors along with breakdowns by operating system and client versions.
- Specify a custom port for peer wakeup – You can now specify a custom port number for wake-up proxy.
- Run CMPivot from the central administration site – Configuration Manager now supports running CMPivot from the central administration site in a hierarchy.
- Edit or copy PowerShell scripts – You can now Edit or Copy an existing PowerShell script used with the Run Scripts feature.
- Dedicated monitoring for phased deployments – Phased deployments now have their own dedicated monitoring node, making it easier to identify phased deployments you have created and navigate to the phased deployment monitoring view.
- Improvement to phased deployment success criteria – Specify additional criteria for the success of a phase in a phased deployment. Instead of only a percentage, these criteria can now also include the number of devices successfully deployed.
- Integration with analytics for Office 365 ProPlus readiness – Use Configuration Manager to identify devices with high confidence that are ready to upgrade to Office 365 ProPlus.
- Additional languages for Office 365 updates – Configuration Manager now supports all supported languages for Office 365 client updates.
- Office products on lifecycle dashboard – The product lifecycle dashboard now includes information for installed versions of Office 2003 through Office 2016.
- Redirect Windows known folders to OneDrive – Use Configuration Manager to move Windows known folders to OneDrive for Business. These folders include Desktop, Documents, and Pictures.
- Optimized image servicing – When you apply software updates to an OS image, there’s a new option to optimize the output by removing any superseded updates.
- Specify thread priority for feature updates in Windows 10 servicing – Adjust the priority with which clients install a feature update through Windows 10 servicing.
- Management insight rules for collections – Management insights has new rules with recommendations on managing collections. Use these insights to simplify management and improve performance.
- Distribution Point Maintenance Mode – You can now set a distribution point in maintenance mode. Enable maintenance mode when you’re installing software updates or making hardware changes to the server.
- Configuration Manager Console Notifications – To keep you better informed so that you can take the appropriate action, the Configuration Manager console now notifies you when lifecycle and maintenance events occur in the environment.
- In-console documentation dashboard – There is a new Documentation node in the new Community workspace. This node includes up-to-date information about Configuration Manager documentation and support articles.
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|
|1902||March 27, 2019||September 27, 2020|
|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 1902 will continue to give you the same warning:
“1902 supports only Windows 2012+ and SQL 2012 SP3+”
SCCM 1902 Server Upgrade
If you have done previous upgrades, the steps to upgrade SCCM Configuration Manager 1902 remain almost the same.
The SCCM 1902 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_1902\
- Launch PowerShell under an elevated command prompt
- Run the EnableFastUpdateRing1902.ps1 script below where SiteServer refers to the CAS or standalone primary site server
- Force a check for the update.
- The new 1902 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 1902 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.
- GUID : 4588eaf0-7848-419e-9fad-9e9a25763f38
- Note: It can take up to 15 minutes to extract all files. The approximate download size of this update is 2.22 GB.
- When completed the State column will show Prerequisite check passed.
Launching the SCCM 1902 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 1902 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 1902 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 – 1902
- Console – 5.1902.1085.1500
- Site Version – 5.0.8790.1000
- Navigate to Administration > Site Configuration > Sites
- Right-click your site and Select Properties
- Verify the Version and Build number
SCCM 1902 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.8790.1005
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.8790.1005'
You can read more about Client version reporting in SQL here.