Let’s check How to Upgrade SCCM Server to 2103 Version and prerequisites of the 2103 version. Microsoft released the latest version of Microsoft Endpoint Manager Configuration Manage. The 2103 version of the Configuration Manager is the opt-in version (you need to use PowerShell to enable it).
This step-by-step guide provides all the details that you require to perform SCCM Server Upgrade to 2103. I have predicted the release dates of ConfigMgr 2010 in the previous post. You can check ConfigMgr 2010 Release Date Predictions | SCCM. But I didn’t do the prediction for the 2103 version of ConfigMgr.
Why ConfigMgr 2103? Why not 2102 Production Version?
To better align with other releases within Microsoft Endpoint Manager (MEM), starting this year the ConfigMgr (a.k.a SCCM) current branch (CB) production version names will be 2103, 2107, and 2111.
- The release frequency will be every four months.
- Release at the same time of the year.
What is Opt-in Ring of ConfigMgr 2103
The Opt-in ring is the option given to organizations to get the newest version of Configuration Manager Current Branch using an opt-in PowerShell script.
Slow ring release of SCCM production will be available for all “online” versions of the service connection point. The General availability of the Configuration Manager 2103 version will be available within one (1) month after opt-in release.
NOTE! – The opt-in version is fully supported for production servers.
Prerequisites of 2103 Version
The following is a quick list of prerequisites for the Configuration Manager 2103 primary server upgrade. Make sure you have gone through all these 12 points before starting the upgrade of the SCCM 2103 production version.
- The following SCCM versions are supported for the upgrade to 2103.
- Install update 2103 at the top-level site of your hierarchy (CAS or Standalone Primary).
- SCCM version should have an online Service Connection Point.
- Evaluate Checklist – below section has more details.
- Upgrade to a supported version of Windows ADK 2004 (2004 is the only version supported for the 2103 version of SCCM). More details here.
- Evaluate SQL Requirements for SCCM 2103 Upgrade – here
- Evaluate Windows Server OS Requirements for ConfigMgr 2103 site server – here
- Evaluate Supported OS versions for clients and devices – here
- Evaluate Supported OS versions for ConfigMgr consoles – here
- Evaluate Recommended hardware – here
- Support for Windows features and networks – here
- Evaluate Support for virtualization environments – here
- Evaluate the Firewall Rules – More details here and here
NOTE! – Enable the site for HTTPS-only or enhanced HTTP – To improve the security of client communications, in the future Configuration Manager will require HTTPS communication or enhanced HTTP. Plan to configure the site for HTTPS only or to Use Configuration Manager-generated certificates for HTTP site systems.
2013 Version Upgrade Check List
The following are the high-level checklist provided by Microsoft. Before starting the Configuration Manager 2103 primary server upgrade in a production environment, let’s go through this list.
NOTE – If you have a secondary site that uses SQL Server Express Edition, this check warns if the version is earlier than SQL Server 2016 with service pack 2 (13.0.5026.0).
- All sites run a supported version of Configuration Manager
- Review the status of your product licensing
- Review Microsoft .NET versions
- Review the version of the Windows ADK for Windows 10
- Review SQL Server Native Client version
- Review file and data replication between sites
- Database replication
- File-based replication
- Install all applicable critical Windows updates
- Disable database replicas for management points at primary sites
- Set SQL Server AlwaysOn availability groups to manual failover
- Disable site maintenance tasks at each site
- Temporarily stop any antivirus software
- Back up customized files
- Plan for client piloting
- Plan to use service windows
- Review supported extensions
- Run the setup prerequisite checker (I recommend running prerequisite check 3-4 day before the production upgrade)
- Update sites
More detailed information about the ConfigMgr 2103 installation checklist is given below https://docs.microsoft.com/en.
Offline Scenario – SCCM Server 2103 Upgrade
To download the update when your service connection point is offline, use the service connection tool.
More details about the process are explained in the post SCCM Upgrade with an Offline Service Connection Point| ConfigMgr.
Download / Enable ConfigMgr Version 2103
Let’s go through the steps to initiate the download of the opt-in version of Configuration Manager 2103 using the PowerShell script. Once the update is downloaded, you can start the installation of the 2103 version of SCCM.
- This 2103 version of ConfigMgr is NOT generally available in all applicable ConfigMgr Consoles.
- To enable the early ring version of ConfigMgr 2103, use the PowerShell script.
- Download and Run the PowerShell command or here.
- Version 2103 opt-in script (EnableEarlyUpdateRing2103.exe)
- Download and Run the PowerShell command or here.
- Launch ConfigMgr console & navigate through \Administration\ Overview \Updates and Servicing.
- Check 2103 version update of ConfigMgr is already available or not?
- If not, click on the “Check for Updates” button from the ribbon menu.
- Click OK to continue.
- Configuration Manager 2103 update is available and Downloading.
NOTE! – Check the DMPDownloader.log to get more details. More details about the log files are available here.
EasySetupDownloadSinglePackage finishes downloading 41f02c4c-bb4b-4b8d-9299-059860339dab. Generating state message: 14 for package 00000000-0000-0000-0000-000000000000 searching for QFE packages in F:\Program Files\Microsoft Configuration Manager\EasySetupPayload\offline
Source Location of 2103 Update
You can see the downloaded file in the following location. You should NOT use these files to update. But this is just for educational purposes. F:\Program Files\Microsoft Configuration Manager\EasySetupPayload.
ConfigMgr 2103 Update Download is Stuck?
The update getting stuck during the downloading stage is a common scenario in enterprise organizations and LAB environments. This issue is mostly because of proxy or some other internet-related issues.
There are a couple of ways to fix this kind of issue if it’s not related to proxy and the internet. You can refer to the previous blog posts to solve Update Download stuck problems. More troubleshooting help on Configuration Manager 2103 Download stuck and upgrade issues here and here.
Log Files to Help Troubleshooting 2103
If you can’t see any lines related to redist to download, that means the download is not completed yet. Log files location – F:\Program Files\Microsoft Configuration Manager\Logs.
- DMPDownloader.log for SCCM 2103 source file download issues
- ConfigMgrSetup.log for Redist Files Download Issue
- CMUpdate.log for all the upgrade related activities
- If the update displays as Downloading and doesn’t change, review the hman.log and dmpdownloader.log for errors.
- The dmpdownloader.log may indicate that the dmpdownloader process is waiting for an interval before checking for updates. To restart the download of the update’s redistribution files, restart the SMS_Executive service on the site server.
- Another common download issue occurs when proxy server settings prevent downloads from
- For more information about installing updates, see In-console updates and servicing.
- For more information about current branch versions, see Baseline and update versions.
Start – ConfigMgr Server Upgrade to 2103
Once the download of SCCM version 2103 is completed successfully and the version 2103 update is Ready to Install, then you can then start the upgrade process.
- Right Click on the Update “Configuration Manager 2103” Update
- Select PreRequisite Check
- Once the Prerequisite Check is completed successfully proceed to the next step
- Right Click on the Update “Configuration Manager 2103” Update
- Click on Install Update to start the SCCM 2103 installation
NOTE! – Make sure you have completed the prerequisites checks steps two-three days before the actual upgrade to the 2103 version of ConfigMgr.
Update Stuck in Prerequisite Stage?
The Configuration Manager upgrade prerequisite check can take many hours, depending on your hierarchy/infra. When you have CAS and many primary servers, the 2103 update source files will be copied to primary servers.
NOTE! – Make sure you start the prerequisite checks 3-4 days before the production update/upgrade of SCCM infra.
You can check the status of the prerequisite checks from the monitoring node. More details about SCCM prerequisite checks here.
Features Included – Remove CAS server
Let’s continue with ConfigMgr 2103 update wizard:
- Click on the “Ignore any prerequisite check settings and install the update regardless of missing requirements” box
- Click on the Next button
- Select the features you want to enable after the upgrades from the Features Included in Update Pack page
- Enable “Remove Central Administration Site (CAS)” option
- Click on Next to continue
- Client Update Settings page configuration
- Upgrade without validating (Direct Production Upgrade)
- Validate in pre-production collection (Test the client before the upgrade)
- Click the NEXT button to continue
NOTE! – More details about client upgrade options are available in the following blog. SCCM Client Upgrade Promote Pre-Production Client to Production.
NOTE! – To take full advantage of new ConfigMgr features, after you update the site, also update clients to the latest version.
- Click on “I accept these License Terms and Privacy Statement“
- Click on the Next button to continue
Summary of update package installation Install Update Package Configuration Manager 2103 Prerequisite warnings will be ignored Turn on the following features: • Remove Central Administration Site Test new version of the client in production
- Click Next, and Next to continue
- Click on Close to continue to the installation process of 2103 and close the wizard.
SCCM 2103 Primary Server Update Status
Once you complete the Configuration Manager update wizard, the ConfigMgr 2103 upgrade process will kick start. And the updates and servicing node in the ConfigMgr console will show that the update is in the installing state.
You can start monitoring ConfigMgr 2103 upgrade from this stage.
- You can click on the link “Show Status” from related objects.
- Show status will show you the details about the installation status in the monitoring workspace.
- \Monitoring\Overview\Updates and Servicing Status\Configuration Manager 2103
- And check the log files referenced in the status to get more detailed information
Let’s also check the log snippets of CMUpdate.log to confirm everything is going well with the 2103 upgrade.
Successfully reported ConfigMgr update status (SiteCode=MEM, SubStageID=0xd0005, IsComplete=1, Progress=50, Applicable=1) File '\?\F:\Program Files\Microsoft Configuration Manager\CMUStaging\41F02C4C-BB4B-4B8D-9299-059860339DAB\SMSSetup\update.map.cab' is signed and trusted. Extracted \?\F:\Program Files\Microsoft Configuration Manager\CMUStaging\41F02C4C-BB4B-4B8D-9299-059860339DAB\SMSSetup\update.map Successfully reported ConfigMgr update status (SiteCode=MEM, SubStageID=0xd0005, IsComplete=2, Progress=100, Applicable=1) INFO: Setup detected an existing Configuration Manager installation. Currently installed version is 9040 Set working directory to the staging folder F:\Program Files\Microsoft Configuration Manager\CMUStaging\41F02C4C-BB4B-4B8D-9299-059860339DAB\SMSSetup CONFIGURATION_MANAGER_UPDATE service is starting… Microsoft Endpoint Configuration Manager v5.00 (Build 9049)
NOTE! – Don’t forget to check CMUpdate.log to get more detailed information about the ConfigMgr Primary server upgrades to 2103.
The following 5(Five) sections have been successfully completed as part of the 2103 installation.
- Download – Completed
- Replication – Completed
- Prerequisite Check – Completed with some warnings
- Installation – Completed
- Post Installation – Completed
Admin Console Upgrade to 2103 Version
The last step of the ConfigMgr 2103 installation is by upgrading the console of Primary servers & CAS server.
You need to make sure all your remote SCCM console installations are upgraded to the latest version. This is not critical if your remote SCCM console is already running with the n-1 version (where n = 2103 in this scenario). That means you can use the 2010 version of the console with the 2103 version of the primary server.
Boot Image Client Version
Default boot image client version seems to show the previous version (2010) even after the successful update of the primary server to the 2103 version. I have initiated the task “Update Distribution points” using the right-click option from the default boot image. This task helped to get the updated client version on the latest boot image.
Success: Update boot image: • Microsoft Windows PE (x64) Success: Update actions: • Add ConfigMgr binaries using Production Client version 5.00.9049.1008 • Disable Windows PE command line support Success: Boot image won't include drivers after the update. Optional components: • Scripting (WinPE-Scripting) • Startup (WinPE-SecureStartup) • Network (WinPE-WDS-Tools) • Scripting (WinPE-WMI)
SCCM 2103 Version Details
Following are the version details of Configuration Manager 2103.
- Client Version 5.00.9049.1008
- Full Site Version 5.00.9049.1000
- Site version 5.0.9049.1000
- Console Version 5.2103.1059.1700
Best Upgrade Guide ConfigMgr Primary Server to 2103 Version | SCCM | Prerequisites Endpoint Manager – Best Upgrade Guide ConfigMgr Primary Server to 2103 Version | SCCM | Prerequisites Endpoint Manager – YouTube