We have a new Baseline Version SCCM 2103 is now available and I feel it is the perfect day to blog about the installation guide.
Also, refer more to the features released in SCCM 2103 as I am going to blog them separately in a day.
SCCM 2103 is the first release this year under the new branding Microsoft Endpoint Configuration Manager
Few Things to be remembered before you opt for this Upgrade
- Check out the Pre-requisites before starting.
- Check out supported Operating System
- Check out the supported SQL version.
- Check out the Database Compatibility level, using SQL query:
SELECT name, compatibility_level FROM sys.databases
|SQL Server version||Supported compatibility levels||Recommended level|
|SQL Server 2019||150, 140, 130, 120, 110||150|
|SQL Server 2017||140, 130, 120, 110||140|
|SQL Server 2016||130, 120, 110||130|
|SQL Server 2014||120, 110||110|
This Blog is broadly classified into 2 categories:
SCCM SITE Backup
Before going with the actual upgrade at the enterprise level, one should follow a few more steps so that in case if something goes wrong, it can be reverted.
Before I start with the upgrade make sure that I have the latest SMS Site Backup. To do that I shall start the “SMS_SITE_BACKUP” service on CAS (if you have) or else Primary Server.
You can check smsbkup.log to confirm if the backup completed successfully.
SCCM Reports Backup
I do manage many customize reports, so I intend to take a backup before I process to actual upgrade. Here we are using Powershell Script, Please feel free to test it out.
Also, find the link below and make sure to download and rename it to .ps1 before using, Script Name SCCMReports_Export. You need to provide the report server name and folder path where you want to export the data as shown below.
- Stop Maintenance Tasks
- Make sure that there is no Maintenance task running during the upgrade process, hence disabling them.
- Similarly, can take a backup of SCCM DBSUS DBReport server database backup using SQL Management studio.
- Early update ring
- At this time, version 2103 is released for the early update ring. To install this update, you need to opt in. The following PowerShell script adds your hierarchy or standalone primary site to the early update ring for version 2103:
- Version 2103 opt-in script Microsoft digitally signs the script and bundles it inside a signed self-extracting executable. Let’s Extract it so that we can execute it.
Open a Windows PowerShell session as administrator.
Run the EnableEarlyUpdateRing2103.ps1 script, using the following syntax:
EnableEarlyUpdateRing2103.ps1 <SiteServer_Name> | SiteServer_IP>
We can See now 2103 listed in Updates and servicing.
Let’s begin with the pre-requisites check, but make sure you execute this on the top infra server in the hierarchy. If you have CAS then do start with it, or begin with the Primary server in case of no CAS.
Upgrade package content is replicated first across the hierarchy in order to run the pre-requisites. Navigate to MonitoringOverviewUpdates and Servicing Status to check the Pre-Req status.
As expected MS wants to warn every client about moving to HTTPS for communication.
Check out Depreciated features too.
On Successful Completion of Prerequisites, you are good to proceed with Upgrade
Next Phase i.e Upgrade blog to be released tomorrow.