- New features in Configuration Manager 2211
- Pre-update checklist
- Upgrade Configuration Manager to version 2211
- Monitor Configuration Manager 2211 upgrade progress
- Configuration Manager console upgrade
- Configuration Manager client package verification
- Configuration Manager client upgrade
- Client logs collections in Configuration Manager (SCCM) - Fri, Apr 7 2023
- Configuration Manager upgrade: New features and installation - Thu, Jan 12 2023
- Install Microsoft apps with Intune - Fri, Dec 23 2022
Before we go through the upgrade process, let's have a look at the new features in the 2211 release.
New features in Configuration Manager 2211
Improvement of cloud sync: You can view the cloud sync status for device members and user collections, and the dashboard shows the cloud sync status under monitoring\Overview\Collection Cloud Sync\Device collections, User Collection. The dashboard displays the mapped Azure AD groups, total member count, synced member count, status (success, failed, in progress), and last sync details.
Network Access Account (NAA) usage alert: There is a prerequisite warning added if the site is configured with an NAA account. If the site is configured with HTTPS or EHTTP, you can remove an unused NAA account.
Content migration for distribution point: You can now migrate the content from one distribution point to another using PowerShell cmdlets and monitor their status. The user security role should have the copy to distribution point permission, and the destination distribution point should be installed with the DP role before you begin content migration. Use the Start-CMDistributionPointMigration PowerShell cmdlet to start the migration:
Start-CMDistributionPointMigration -SourceDistributionPointName <FQDN for source distribution point> -DestinationDistributionPointName <FQDN for destination distribution point>
Features tab in the software center: The Features tab is now available in the software center on user machines. The admin can enable the Features tab in the client settings and must then mark the app as featured in the Software Center tab of the application properties. Currently, this feature is available for user collection deployment. If the application is deployed as an available app, it will appear in the Features tab.
Configuration Manager Console search experience enhancements: A hint text in the search bar now indicates the scope of a search that is performed on all nodes in the Configuration Manager console. When you perform a search that contains subfolders, all folders are searched by default, and you can narrow down the search by selecting the current node from the search toolbar. Select All objects in the search toolbar if you want to include all nodes.
Dark theme enhancements in Configuration Manager console: The optional dark theme has been a prerelease feature since 2203. It is now available for more dashboards, including the O365 Updates dashboard, the PCM dashboard, and the Health Attestation dashboard. To use this theme, select the arrow button from the top left of the ribbon, and choose the Switch Console theme. To return to the light theme, select the Switch Console theme again.
Duplicate entry removal for comanaged devices in the Intune portal: Currently, there are two separate entries for each device in the Intune portal. One entry is related to Configuration Manager, and the other is related to Intune. Intune is not aware of AAD ID devices coming from Configuration Manager. In the past, they merged only after the daily discovery runs and reported to Intune via CMG. This issue is now fixed, and devices coming from Configuration Manager will now appear after 30–40 mins in Intune.
Before you start to upgrade Configuration Manager, check whether your environment fulfills all the requirements:
- Supported version of Configuration Manager in all sites: CAS, primary sites, and secondary sites must be running the same version of Configuration Manager.
- Microsoft .NET version: .Net version 4.6.2 is required for site servers, site systems, and clients.
- Windows ADK Version: Check the supported versions of ADK in this Microsoft article, and update the site server before updating Configuration Manager. This automatically updates the default boot images.
- Review the site and hierarchy status: Go through the site and hierarchy status under Monitoring in the Configuration Manager console to see whether any issues are reported and, if so, fix them.
- Replication between sites: Check database and file-based replications and resolve issues in the backlog of the replication group, the link state, the sender.log, and despooler.log.
- Disable database replicas for management points: Primary sites will not upgrade if database replicas are enabled in the management point. Disable them before installing this update on the primary site.
- Set SQL Server Always On availability groups to manual failover: Set manual failover on the availability groups before installing the update. You can change to automatic once the site is updated.
- Disable site maintenance tasks: Configuration Manager has a list of scheduled maintenance tasks on the site. Disable the tasks before installing the update, or the update will fail if the maintenance task runs during the update.
- Backup of the site database: Back up all site databases before installing the update. You can use the backup to restore if the update fails.
Upgrade Configuration Manager to version 2211
If you fulfilled all the prerequisites and solved all the issues in the pre-update checklist, you are ready to upgrade Configuration Manager.
Download Configuration Manager
Launch the Configuration Manager console and navigate to Administration > Updates and Servicing. Select the Configuration Manager 2211 update, and right-click to download.
The Configuration Manager 2211 update is downloaded from the internet. Make sure you have internet access.
Go to Monitoring > Updates and Servicing Status, right-click the Configuration Manager 2211 update, and click Show status. You will see additional details about the download process. If there is any error during the download, you can find out why here.
Once the download is completed, the update state will show Ready to install. You can now run the prerequisite checks and proceed with installing the update. Right-click the update and select Run prerequisite check.
To monitor the process, click Show Status on the right side. Warning messages can be ignored. If errors appear, you must resolve the issue and rerun the process. You can also check the ConfigMgrPreReq.log and the Configuration Manager Server log.
Installation of the Configuration Manager 2211 update
Launch the Configuration Manager console and navigate to Administration > Updates and Servicing. Select Configuration Manager 2211 update, right-click, and select Install Update Pack.
The Configuration Manager 2211 update installation includes the Configuration Manager server updates, the Configuration Manager console updates, client updates, fixes for known issues, and new features. Select Ignore any prerequisite check warnings, and proceed with the installation. Click Next.
On the Features page, view a list of the new features available in this update and enable the required features. You can also do this after the update. To enable new features, navigate to Administration > Updates and Servicing > Features. You will see a list of features with status, feature type, and description.
On the Client update options page, select whether you want the clients to be upgraded without validating or validate the clients in the pre-production collection and then upgrade the remaining production clients (I have selected Upgrade without validating). Then click Next.
On the License Terms page, select I accept these License Terms and Privacy Statement, and click Next to continue.
On the Summary page, review the configured settings for the update installation, and click Next.
The update installation has been configured successfully, and you can click Close to complete the wizard.
Monitor Configuration Manager 2211 upgrade progress
To monitor the upgrade process, navigate to Monitoring > Updates and Servicing status, and right-click to show the status of the update. The detailed status includes stopping services, database, registry, and packages. This process will take approximately 30–45 minutes.
The upgrade process is completed, and the status moves to the installed state. You can also view the cmupdate.log in the Site Server to monitor the upgrade process. After this process, you will need to upgrade the Configuration Manager console, client packages, and production clients.
Open the Configuration Manager console and navigate to Administration > Site Configuration > Sites. Select the Primary site, and right-click Properties to verify the new version and build number displayed under the General tab. You should see Version - 5.00.9096.1000, Build Number - 9096.
Configuration Manager console upgrade
Once the Configuration Manager upgrade is completed, you need to upgrade the Configuration Manager console on the site server and other devices. You will see a message warning of such in the top ribbon. Refresh the console or close and open the Configuration Manager console. You will receive a prompt to start the upgrade process. Click OK.
The console upgrade is underway. It will take 2–3 minutes to download the new files and complete the installation. Check these logs for more information: C:\ConfigMgrAdminUISetup.log and C:\ConfigMgrAdminUISetupVerbose.log
Once the Configuration Manager console upgrade is completed, launch the console, go to the top left center, click the blue arrow, and then click About Configuration Manager to verify the new version. The version should now be 2211, the console version 5.2211.1061.1000, and the site version 5.0.9096.1000.
Configuration Manager client package verification
Launch the Configuration Manager console and navigate to Software library > Application Management > Package. Verify that the two client packages are updated. The packages need to be updated and distributed to distribution points before the Configuration Manager client upgrade starts.
Configuration Manager client upgrade
To enable auto upgrades for production clients, navigate to Administration > Site Configuration > Sites > Select Primary site. Click Hierarchy settings in the top ribbon, and then click the Client Upgrade tab. Enable Upgrade all clients in the hierarchy using production client, specify the number of days in which the auto upgrade should be completed (7 days by default), and click OK. Run the built-in report or create a collection query to verify the Configuration Manager client version upgrade progress.
Subscribe to 4sysops newsletter!
Once your clients are updated, your Configuration Manager upgrade is complete.
Want to write for 4sysops? We are looking for new authors.