Microsoft has released a second SCCM version for 2021. SCCM 2107 has been released on August 2nd, 2021. Don’t forget SCCM has had a new branding since 1910 – now called Microsoft Endpoint Configuration Manager (MEMCM). This post is a complete step-by-step SCCM 2107 upgrade guide, meaning that if you want to upgrade your existing SCCM/MEMCM installation to the latest SCCM/MEMCM updates, this post is for you.
If you’re looking for a comprehensive SCCM installation guide to build a new server, refer to our blog series which covers it all.
You won’t be able to install SCCM 2107 if you are running SCCM 2012. Well, that’s an odd phrase! Thank you current branch naming.
SCCM 2107 is not a baseline version. This means that if you’re downloading the source from Volume Licensing, SCCM 2103 will be the starting version of your new SCCM site and you’ll have to apply this update afterward.
At the time of this writing, SCCM 2107 is available in the Early update ring. You must run the opt-in script to see it appear in the console. We’ll cover that in the Installation section.
To install SCCM 2107 as an update, you must have installed
Keeping your infrastructure up to date is essential and recommended. You will benefit from the new features and fixes, which some of them can apply to your environment. It’s easier than ever to upgrade since Microsoft has implemented the servicing model directly from the console.
SCCM 2107 Upgrade Guide – New Features and Fixes
SCCM 2107 includes an incredible amount of new features and enhancements in the site infrastructure, content management, client management, co-management, application management, operating system deployment, software updates, reporting, and configuration manager console. This release is packed with interesting features to try.
You can consult the What’s new in version 2107 of System Center Configuration Manager Technet article for a full list of changes.
Here’s our list of favourite features. Microsoft brings together SCCM/MEMCM and Intune into a single console called Microsoft Endpoint Manager admin center. We’ll do blog posts on the most interesting feature in the coming weeks :
- Select VM size for CMG
- External Notification
- Support for Windows Server 2022 and the ADK for Windows 11
- Custom properties for devices
- Hardware inventory for client log settings
- Support for macOS Big Sur
- Implicit uninstall of applications
- Enhanced code editor
- Download Power BI report templates from Community hub
Support for SCCM Current Branch Versions
Ensure to apply this update before you fall into an unsupported SCCM version. Read about the support end date of the prior version of the following Technet article.
Windows and SQL Support
Before installing, make sure that you are running a supported Operating System and SQL version. Older SCCM version was giving a warning during the Prerequisite check but 2107 is giving an error that prevents the installation from continuing.
SCCM 2107 supports only Windows 2012+ and SQL 2012 SP3+.
The support lifecycle for SQL Server 2012 ends on July 12, 2022. Plan to upgrade database servers in your environment, including SQL Server Express at secondary sites.
Important InfoVersion 1906 client requires SHA-2 code signing support.
Due to weaknesses in the SHA-1 algorithm and to align to industry standards, Microsoft now only signs Configuration Manager binaries using the more secure SHA-2 algorithm. The following Windows OS versions require an update for SHA-2 code signing support:
Windows 7 SP1
Windows Server 2008 R2 SP1
Windows Server 2008 SP2
Before you Begin – SCCM 2107 Upgrade Guide
Downloading and installing this update is done entirely from the console. There’s no download link, the update will appear on your console once the Service Connection Point is synchronized.
If you’re running a multi-tier hierarchy, start at the top-level site in the hierarchy. After the CAS upgrade, you can begin the upgrade of each child site. Complete the upgrade of each site before you begin to upgrade the next site. Until all sites in your hierarchy are upgraded, your hierarchy operates in a mixed version mode.
Before applying this update, we strongly recommend that you go through the upgrade checklist provided on Technet. Most importantly, initiate a site backup before you upgrade.
There’s a couple of new important prerequisite check in this SCCM 2107 release :
Important InfoConfiguration Manager now requires Microsoft .NET Framework version 4.6.2 for site servers, specific site systems, clients, and the console. Before you run setup to install or update the site, first update .NET and restart the system. If possible in your environment, install the latest version of .NET version 4.8.
Starting in this release, Configuration Manager now uses the Microsoft Visual C++ 2015-2019 redistributable version 14.28.29914.0. If the VCRedist doesn’t already exist, it automatically installs.
Before you update to version 2107, if you restrict internet access, confirm that the site system that hosts the service connection point role can communicate with the following internet endpoint: configmgrbits.azureedge.net . This endpoint was already required, but
its use is expanded in this release. The site system can’t download version 2107 or later unless your network allows traffic to this URL.
The prerequisite check will verify all that for you :
In this post, we will update a stand-alone primary site server, consoles, and clients. Before installing, check if your site is ready for the update:
- Open the SCCM console
- Go to Administration \ Updates and Servicing
- In the State column, ensure that the update Configuration Manager
2107 is Ready to install
- If it’s not available, right-click Updates and Servicing and select Check for Updates
WarningThe SCCM 2107 update is not yet available for everyone. If you need it right away you can run the Fast-Ring script and the update will show up.
- 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 Dmpdownloader.log or by going to Monitoring / Updates 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.
- It can take up to 15 minutes to extract all files.
SCCM 2107 Upgrade Guide
Step 1 | SCCM 2107 Prerequisite Check
Before launching the update, we recommend launching the prerequisite check first. To see the prerequisite checklist, see the Microsoft Documentation
- Open the SCCM console
- Go to Administration \ Updates and Servicing
- Right-click the Configuration Manager 2107 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
- If you have any warnings, follow the recommendation to fix the issue in the bottom pane
- The check if HTTPS or Enhanced HTTP is enabled will probably pop for a lot of you. We release a full blog post on how to fix this warning. For now, this is supported until Oct 31, 2022.
- When completed the State column will show Prerequisite check passed
- Right-click the Configuration Manager 2107 update and select Install Update Pack
Step 2 | Launching the SCCM 2107 Update
We are now ready to launch the SCCM 2107 update. At this point, plan about 45 minutes to install the update.
- On the General tab, click Next
- On the Features tab, 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 clients members of a specific collection. Refer to our pre-production client deployment post for more details
- On the License Terms tab, accept the license terms and click Next
- On the Summary tab, review your choices, click Next and close the wizard on the Completion tab
The whole process took a minute but the installation begins on the back end.
- During installation, the State column changes to Installing
- We suggest you monitor the progress, by navigating to Monitoring / Updates and Servicing Status, right-click your Update Name and select Show Status
Unfortunately, the status is not updated in real-time. Use the Refresh button to update the view.
- Open the SCCM update log SCCMInstallationDirectory\Logs\CMUpdate.log with CMTrace
Important InfoWe’ve done numerous SCCM upgrades. Some installation start a couple of minutes after you complete the wizard but we’ve seen some installation starts after a 10 minutes delay. Do not reboot or restart any services during this period or your update can be stuck in “Prerequisite check passed” status. There’s actually no officially documented methods by Microsoft to fix that. Patience is the key!
- 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 Name and select Show Status, the last step will be Installation Succeeded
- Refresh the Updates and Servicing node in Administration, the State column will be Installed
Updating the Outdated Consoles
As a previous update, the console has an auto-update feature. At the console opening, if you are not running the latest version, you will receive a warning and the update will start automatically.
- Since all updates 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. You can follow the progress in C:\ConfigMgrAdminUISetup.log and C:\ConfigMgrAdminUISetupVerbose.log. Once completed, the console will open and you’ll be running the latest version
After setup is completed, verify the build number of the console. If the console upgrade was successful, the build number will be 9058 and the version is now Version 2107. Notice the new Endpoint Configuration Manager branding!
- Go to Administration \ Site Configuration \ Sites
- Right-click your site and select Properties
- Verify the Version and Build number
Upgrade SCCM 2107 Clients
The client version will be updated to 5.00.9058.100x (after updating, see the section below)
SCCM 2107 Client Package distribution
You’ll see that the 2 client packages are updated:
- Navigate to Software Library \ Application Management \ Packages
- Check if the update is successful, otherwise, select both packages and initiate a Distribute Content to your distribution points
Boot images will automatically update during setup. See our post on upgrade consideration in a large environment to avoid this if you have multiple distribution points.
- Go to Software Library / Operating Systems / Boot Images
- Select your boot image and check the last Content Status date. It should match your setup date
SCCM 2107 Upgrade Guide – Upgrade Clients
Our preferred way to update our clients is by using the Client Upgrade feature: (You can refer to our complete post documenting this feature)
- Open the SCCM Console
- Go to Administration / Site Configuration / Sites
- Click the Hierarchy Settings in the top ribbon
- Select Client Upgrade tab
- The Upgrade client automatically when the new client update is available to the checkbox is enabled
- Review your time frame and adjust it to your needs
Reconfigure SQL Server AlwaysOn availability groups
To complete SCCM 2107 Upgrade Guide, if you use an availability group, reset the failover configuration to automatic. For more information, see SQL Server AlwaysOn for a site database.
Reconfigure any disabled maintenance tasks
If you 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.
SCCM 2107 Upgrade Guide – Monitor SCCM Client Version Number
SCCM Reports Client Version
You can see our SCCM Client version reports to give detailed information about every client version in your environment. It’s the easiest way to track your client updates.
In conclusion, you can create a collection that targets clients without the latest client version because is very useful when it comes to monitoring a non-compliant client.
Here’s the query to achieve this: (You can also refer to our Set of Operational Collection Powershell Script which contains this collection)
select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.ClientVersion != '5.00.9058.1008'
Pingback: DEPLOY, REFRESH AND UPGRADE WINDOWS 11 SCCM / MEMCM - Hidden Shard Blog
Pingback: DEPLOY, REFRESH AND UPGRADE WINDOWS 11 SCCM / MEMCM
I bought your guide about MECM operating system upgrade, but I couldn’t find any guidance about the following scenario :
MECM version is 2010 (may be 2103/2107 soon) on all hierachies.
CAS and DP will remain unchanged during the migration (same name, same IP). Primary server will get a new name and a new IP address.
– Current hierachy : CAS + Primary (old) + DP, all running WS 2012 R2, remote SQL Server running SQL 2014 / WS 2012 R2
– Future hierachy : CAS + Primary (new) + DP, Primary running WS 2019, CAS and DP still running WS 2012 R2, SQL database now colocated on primary and running SQL Server 2019.
I plan to migrate using migration jobs. Is it the right approach ? Since only the primary server is modified, I’m having doubts about this.
Is it supported to migrate SQL data from an older version to a newer using this method ? I couldn’t find documentation indicating if migration jobs are agnostic regarding SQL Server version (I know the backup/restore scenario isn’t).
A SQL Server in-place upgrade is also possible, but I feel it is better to avoid it, because 1) that’s another migration 2) the current SQL database is huge (200+ Go), so the upgrade itself could take hours.
Let me know what you think.
Please contact us at firstname.lastname@example.org. Sounds like a complex scenario that could use our expertise with a support time bank to assist you with the best solution.