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.

Related PostTop 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. There are two hotfixes released for 2103 while the last update of this post.

Patch My PC
  • The Hotfix KB10372804 to fix MBAM Agent API to escrow recovery keys issue.
  • Out of Band Hotfix KB10216365 to fix SQL always-on issue.
  • Latest Hotfix for SCCM 2103 – KB10036164 (Update Rollup).
  • First KB released for SCCM 2103 is KB9603111 (available in console).
  • 2nd KB KB9833643 for ConfigMgr 2103 (Out of Band).

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 that are included with ConfigMgr 2103. You can read more about this from Microsoft documentation.

📢✅Description
ADRADR fails on servers that do not have internet access after updating to 2010
Azure Migration ToolThe ExtendMigrateToAzure tool fails to add accounts to the local administrators’ group
CAS RemovalAdding a new DP to a package triggers the redistribution of that package to all DP’s after CAS removal
CAS RemovalThe Configuration.mof used with hardware inventory is not created on a primary site after removing CAS
ClientClient user policy namespaces are created on multi-user terminal servers even when explicitly disabled
ClientClients do not download package content over a metered connection
ClientComputers randomly don’t receive policy data based on computer variables (SMS_MachineVariable)
Client CacheNon-zero success codes, such as 3010 (restart pending) – The exit code is 3010, the execution status is FailureNonRetry
Cloud DPThe upload of more than 10 packages at one time to a cloud distribution point fails
CMPivotThe CMPivot feature incorrectly requires access to the default security scope
CollectionCollection Evaluator Performance Improvement
Co-ManagementCo-management workloads may be unexpectedly deployed to newly installed ConfigMgr clients.
Content LibraryMultiple improvements were made to the content library move and cleanup processes
DPOrphaned content may be left after deleting application revisions
Hotfix InstallationSCCM hotfixes that only update the admin console will no longer require a site reset.
Microsoft DefenderState messages generated by the on-premises ATP monitoring feature may fail to process on the site server
OSDOSD from boot media fail to retrieve content from a cloud DP if custom ports are defined
OSDThe SMS Agent Host (ccmexec.exe) incorrectly tries to resolve a site code when you use standalone media
ReportingThe Compliance 4 – report terminates unexpectedly
SQL ServerSQL Server TempDB may grow unexpectedly because Datawarehouse issues
SQL ServerImprovements were made to the SQL Server change tracking cleanup task.
SUPThe 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 to run following a computer restart
Task Sequence The Format and Partition Disk task sequence step fails when more than 99 disks are present
Task Sequence Various custom client settings may fail to apply if an operating system deployment task sequence fails to remove WMI instances
SCCM 2103 Known Issues – Fixes table | ConfigMgr

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 version 2103 update fail to import. The Import Task Sequence Wizard displays the following error –
    • One or more errors occurred result may be incomplete.
  • No data is shown in the Windows 10 servicing dashboard, even after completing the troubleshooting steps listed in the following support article. The Windows 10 servicing dashboard shows no data
  • The New-CMBootableMedia PowerShell cmdlet returns the error Could not find the SCCM UI installation directory after updating to version 2103.
  • SCCM Azure Active Directory (AAD) joined clients that are also using PKI issued certs can get into a high CPU utilization situation that impacts 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).
  • During reassignment from one site to another, clients are unable to evaluate policy or communicate via the notification channel. 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.
    • Other exception – Value was either too large or too small for an Int32.
  • After updating to SCCM current branch, version 2103, a backlog of .MEP (machine extended policy) files occurs in the PolicyPV inbox on the site server. This backlog also causes delays in 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 failed 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 a central administration site (CAS) is removed 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.
  • After removing a central administration site, packages are distributed to all distribution points (DP) when adding them to just a single new DP.
  • Failover from an active to a passive site fails in an environment with a large number of orphaned package status data records.

Issue #1 – Old Console Extensions

ConsoleYour 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. 
SCCM 2103 Known Issues – Console Extension

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

1E Nomad
  • Disable the option “Only allow console extensions that are approved for the hierarchy” to make the old-style console extensions to work again.
SCCM 2103 Known Issues Fixes | ConfigMgr
SCCM 2103 Known Issues Fixes | ConfigMgr

Issue #2 – Console Lock?

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

I can’t use the console until I close the Query Rule Properties Window as you see in the below picture. I have experienced this in the Namaste Techies show as well.

SCCM 2103 Known Issues Fixes | ConfigMgr
SCCM 2103 Known Issues Fixes | ConfigMgr

This SCCM 2103 known issue is not only related to collection, but it’s wider applicable for all parts of the console. For example, if you open up more than one nested Window from the console, it disables access to the console.

What 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 on the EDIT button, it opens up an additional Window #1.
  • If I go to any one of the actions and click on Add condition option, it opens up the additional Window #2 on top of Window #1.
  • Now the console is locked! You can access anything from the console until you close Windows #2.
SCCM 2103 Known Issues Fixes | ConfigMgr
SCCM 2103 Known Issues Fixes | ConfigMgr

Issue #3 – 2103 MP installation failed

Panu Saukko (Microsoft MVP) shared an issue on Twitter related to SCCM 2103 Management Point installation failed with the following error – LocalSystem’s decimal separator char 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. More details available in the Twitter thread.

Production Ready

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

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

Resources