SCCM 2103 Known Issues Fixes | ConfigMgr | Configuration Manager

In this post, you will learn more about SCCM 2103 known issues. The production version of 2103 is generally available. Let’s understand the fixes already issued with the 2103 version. You can check out our 2103 upgrade guide.

The latest version of ConfigMgr 2103 contains fixes and feature improvements. As I always say, this is not an all-inclusive list of changes and fixes included in the 2103 version.

However, the list of fixes documented below is most relevant for SCCM admins as per the Microsoft production team.

You can learn more about the new features of the SCCM 2103 production version. Let’s get more details from the Top 5 New Features of SCCM 2103 | ConfigMgr. You can learn more about ConfigMgr Slow Ring Vs. Fast Ring (Opt-in version) Details.

Related Post – Top 5 New Features of SCCM 2103 | ConfigMgr.

SCCM 2103 Hotfixes

Let’s check the hotfixes released for the Configuration Manager 2103 production version. I will try to update this list whenever Microsoft releases new hotfixes for 2103. Two hotfixes were released for 2103 during the last update of this post.

• The Hotfix KB10372804 will fix the MBAM Agent API to escrow recovery keys issue.
• Out of Band Hotfix KB10216365 is used to fix the SQL always-on issue.
• Latest Hotfix for SCCM 2103 – KB10036164 (Update Rollup).
• The first KB released for SCCM 2103 is KB9603111 (available in the console).
• 2nd KB KB9833643 for ConfigMgr 2103 (Out of Band).
• Client Update KB10589155.
• Tenant Attach Fix KB10582136.

SCCM 2103 Fixes

The following are the SCCM known issues fixed with the Configuration Manager (a.k.a SCCM) 2103 version. This is not an all-inclusive list of fixes included with ConfigMgr 2103. You can read more about this from Microsoft documentation.

SCCM known issues	Description
ADR	ADR fails on servers that do not have internet access after updating to 2010
Azure Migration Tool	Client user policy namespaces are created on multi-user terminal servers even when explicitly disabled.
CAS Removal	The ExtendMigrateToAzure tool fails to add accounts to the local administrators’ group.
CAS Removal	State messages generated by the on-premises ATP monitoring feature may fail to process on the site server.
Client	The Configuration.mof used with hardware inventory is not created on a primary site after removing CAS.
Client	Clients do not download package content over a metered connection
Client	Custom client settings may fail to apply if an operating system deployment task sequence fails to remove WMI instances.
Client Cache	The upload of more than 10 packages at one time to a cloud distribution point fails.
Cloud DP	Multiple improvements were made to the content library move and cleanup processes.
CMPivot	The CMPivot feature incorrectly requires access to the default security scope
Collection	Collection Evaluator Performance Improvement
Co-Management	Co-management workloads may be unexpectedly deployed to newly installed ConfigMgr clients.
Content Library	Various custom client settings may fail to apply if an operating system deployment task sequence fails to remove WMI instances.
DP	Orphaned content may be left after deleting application revisions
Hotfix Installation	SCCM hotfixes that only update the admin console will no longer require a site reset.
Microsoft Defender	The SMS Agent Host (ccmexec.exe) incorrectly tries to resolve a site code when you use standalone media.
OSD	OSD from boot media fail to retrieve content from a cloud DP if custom ports are defined
OSD	The Format and Partition Disk task sequence step fails when more than 99 disks are present.
Reporting	The Compliance 4 – report terminates unexpectedly
SQL Server	SQL Server TempDB may grow unexpectedly because Datawarehouse issues
SQL Server	Improvements were made to the SQL Server change tracking cleanup task.
SUP	The synchronization process fails on a remote software update point (SUP)
Task Sequence	A command defined in the SMSTSPostAction task sequence variable runs twice after a device restart.
Task Sequence	Task sequences may fail or take longer than expected following a computer restart.
Task Sequence	Task sequences may fail or take longer than expected to run following a computer restart.
Task Sequence	The Configuration.mof used with hardware inventory is not created on a primary site after removing CAS.

SCCM 2103 Known Issues

Microsoft added a new known issue to the document (documented known issues) to the 2103 release notes. I’ll keep the list of SCCM 2103 known issues updated. Also, if you want to highlight some known issues, please add them to the comments section below.

Latest Known Issues of SCCM 2103

• Task sequences/task sequence steps created before installation of the version 2103 update fail to import. The Import Task Sequence Wizard displays the following error –
  • If one or more errors occur, the result may be incomplete.
• The Windows 10 servicing dashboard shows no data, even after completing the troubleshooting steps listed in the following support article.
• The New-CMBootableMedia PowerShell cmdlet returns an error. After updating to version 2103, I could not find the SCCM UI installation directory.
• SCCM Azure Active Directory (AAD) joined clients using PKI-issued certs, which can experience high CPU utilization and impact the end-user. This occurs because of an issue with the SMS Agent Host (ccmexec.exe) attempting to continually renew the “self-prove” token with the Management Point (MP).
• Clients cannot evaluate policy or communicate via the notification channel during reassignment from one site to another. Errors resembling the following are recorded in the ccmexec.log file.
  • Error registering hosted class ‘{Class_GUID}’. Code 0x80040111.
• The report Compliance 4 – Updates by vendor month year does not contain expected data.
• App usage data is stale or unavailable for devices in the Desktop Analytics portal in the Microsoft Endpoint Manager admin center. This only affects notebook computers that run for multiple days without restarting. An error resembling the following is recorded in the SensorManagedProvider.log file on affected devices.
  • Another exception is that the value was too large or too small for an Int32.
• After updating to SCCM’s current branch, version 2103, a backlog of MEP (machine-extended policy) files occurs in the PolicyPV inbox on the site server. This backlog also delays processing site reassignment data.
• Devices upgrade to the 2103 version of the SCCM client faster than expected after promoting the upgrade from pre-production. In addition, the WebView 2 client component is installed repeatedly.
• State message processing hangs when encountering a corrupt file instead of discarding the file as expected. Errors resembling the following are recorded in the statesys.log file. –
  • Thread ‘State Message Processing Thread #0″ id:14888 terminated abnormally.
• State message processing fails for some cloud management gateway (CMG) messages. Errors resembling the following are recorded in the statesys.log file.
  • SQL MESSAGE: dbo.spProcessStateReport – Error: Record 1 returned an ‘invalid record’ return code and failed processing with error 8115.
• A new SCCM console extension created for the community hub for version 2103 will fail to load if a prior console extension modifies the same node with the same action.
• The SQL Server move process fails after a highly available site is passed over to the passive site server. This occurs due to a certificate problem that resembled the following in the ConfigMgrSetup.log file.
  • ERROR: Failed to decrypt SQL Server machine serialized pfx certificate (LastError=0)
• The Wake on LAN feature does not function as expected after removing a central administration site (CAS) due to a missing site control property value.
• The SMS Agent Host service may terminate unexpectedly due to a policy agent issue.
• CMPivot queries do not run on computers configured with the Japanese system locale.
• When a central administration site is removed, packages are distributed to all distribution points (DP) when added to a new DP.
• Failover from an active to a passive site fails in an environment with many orphaned package status data records.

Issue #1 – Old Console Extensions

Issue #1	Old Console Extensions
Console	Your old-style console extensions will stop working when you enable Only allow console extensions that are approved for the hierarchy option. You can’t use the unapproved extensions until you approve from the new Console Extension node.

The above console extension SCCM 2103 known issue will apply only if you have enabled the following check box from the hierarchy settings properties. You can get more details in Microsoft Docs.

• Disable the option “Only allow console extensions approved for the hierarchy “ to make the old-style console extensions work again.”

Issue #2 – Console Lock?

I have seen some issues with the usability of the admin console/accessibility. The console gets locked when you open more than one nested window.

As you can see in the picture below, I can’t use the console until I close the Query Rule Properties Window. I also experienced this at the Namaste Techies show.

This SCCM 2103 known issue is related to the collection and applies to all parts of the console. For example, opening more than one nested Window from the console disables access to it.

What do I mean by more than one nested Window? Let’s take an example to explain it better.

• If I select a Task Sequence and click the EDIT button, Window #1 opens.
• If I go to any of the actions and click on the Add condition option, it opens Window #2 on top of Window #1.
• Now the console is locked! You can access anything from the console until you close Windows #2.

Issue #3 – 2103 MP installation failed

Panu Saukko (Microsoft MVP) shared an issue on Twitter related to the SCCM 2103 Management Point installation, which failed with the following error: LocalSystem’s decimal separator character was “,” instead of “.”! And there was one decimal value in the MOF file.

Panu got it working by changing the decimal separator, but it took some time to figure out what was wrong. The Twitter thread has more details.

Production Ready

This post is to help SCCM admins easily go through a list of SCCM 2103 Known Issues production versions. Most highlighted issues are collected via social media channels and Microsoft documentation.

NOTE! – These known issues are not blockers for the SCCM 2103 production upgrade.

Resources

• Release notes – Configuration Manager | Microsoft Docs
• Top 5 New Features of SCCM 2103 | ConfigMgr
• SCCM 2103 is Generally Available | End of Opt-in Phase | ConfigMgr

We are on WhatsApp. To get the latest step-by-step guides and news updates, Join our Channel. Click here –HTMD WhatsApp.

Author

Anoop C Nair has been Microsoft MVP for 10 consecutive years from 2015 onwards. He is a Workplace Solution Architect with more than 22+ years of experience in Workplace technologies. He is a Blogger, Speaker, and Local User Group Community leader. His primary focus is on Device Management technologies like SCCM and Intune. He writes about technologies like Intune, SCCM, Windows, Cloud PC, Windows, Entra, Microsoft Security, Career, etc.