ConfigMgr 2010 Known Issues Fixes | SCCM | Configuration Manager | Endpoint Manager

In this post, you will learn more about ConfigMgr 2010 known issues. The production version of 2010 is generally available. Let’s understand the fixes already issued for SCCM 2010.

The 2010 version is made available to all SCCM infrastructure with an online Service Connection Point. Also, you should have any of the following versions of ConfigMgr 1906, 1910, 2002, 2006.

Read More details about SCCM Support Life Cycle. You can learn details about the features of the ConfigMgr 2010 production version. Let’s get more details from Top 5 New Features of SCCM 2010 | ConfigMgr.

Patch My PC

**Updated on 21st April 2021

ConfigMgr 2010 Hotfix – KB Articles

Manage Engine

Let’s check the hotfixes released for ConfigMgr 2010 production version. I will try to update this list whenever Microsoft releases new hotfixes for 2010.

Related Posts – SCCM 1910 Known IssueSCCM 1906 Known Issues, SCCM 2002 known issues, and 2006 Known Issues.

1E Nomad

2010 Known Issues

Microsoft added a new known issue to the document (documented known issues) to the release notes. It’s a bit confusing though some of those known issues of SCCM 2010 are applicable only for the early ring (opt-in) version of 2010.

Updated on 21st April 2021 – Microsoft Released a large list of known issues with 2010 recently and those are fixed by the latest version of Configuration Manager (a.k.a SCCM) 2103.

  • Software Center Issues with 2010 – Exception caught in OnGetException, line 193, file X:\bt\1086721\repo\src\SoftwareCenterApplication\App.cs – Type http://Microsoft.SoftwareCenter.Client.Data.WmiException: , error code –2016410859. This is highlighted by Dieter Haiman on Twitter and Microsoft confirmed that this will be fixed in the 2010 Rollup update.

  • Another issue related to the notification issue mentioned above is with the Invoke-CMClientAction PowerShell cmdlet and other SDK methods if you don’t include a collection object or ID.
  • Site server in passive mode fails to update to SCCM version 2010 (As per documentation only applicable for opt-in version).
ConfigMgr 2010 Known Issues Fixes | SCCM
ConfigMgr 2010 Known Issues Fixes | SCCM
Fixes Included with ConfigMgr 2010 KB4594176 (only applicable to opt-in version of 2010)
After creating multiple orchestration groups, only the first group works as expected. Clients that belong to other orchestration groups beyond the first will receive the incorrect policy, resulting in unexpected results such as not installing software.
Users can only delete a collection if they have the Full Administrator security role, even if they own the collection and otherwise would have the authority to perform the deletion.
If you have a highly available site server, when you update to version 2010, the site server in passive mode fails to update. This issue is due to a change in the Microsoft Monitoring Agent (MMA) for Microsoft Defender Advanced Threat Protection. The required MMA files aren’t copied to all necessary locations.
The SCCM console terminates unexpectedly when viewing the preview of query results with a large result set.
The SCCM console terminates unexpectedly if there is a zero-byte ConsoleUsage-{date}-{time}.xml file under %USERPROFILE%\AppData\Local\Microsoft\ConfigMgr10. If this issue occurs, check for and delete the zero-byte file.
After onboarding to Desktop Analytics, The Importance value of apps does not appear in the Apps tab of the Microsoft Endpoint Manager admin center. Additionally, apps deployed with SCCM may not be listed on the Apps tab at all.
For version 2010 early update ring, if you use a PKI-based certificate for operating system boot media, configure it for SHA256 with the Microsoft Enhanced RSA and AES provider. For later releases, including globally available version 2010, this certificate configuration is recommended but not required. The certificate can be a v3 (CNG) certificate.
Device compliance status on the Software Update Dashboard may show an incorrect count of devices and incorrect compliance percentage.

Production Ready

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

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

No Blocker ConfigMgr 2010 Known Issues Fixes | SCCM
ConfigMgr 2010 Known Issues Fixes | SCCM

Issues Fixed with 2010 Version of ConfigMgr

The following is the list of issues fixed with the release of the ConfigMgr 2010 production version. This information is Microsoft shared with the KB article 4599442. All these issues were part of previous versions of ConfigMgr.

ConfigMgr 2010 Known Issues Fixes | SCCM
ConfigMgr 2010 Known Issues Fixes | SCCM
  • The Set-CMStatusFilterRule and Get-CMStatusFilterRule PowerShell cmdlets return different results when used with the same -name parameter.
  • SCCM incorrectly uses the site system installation account for a remote site system to connect to the SQL Server database.
  • The serial number of a device is blank when viewed from device properties in the SCCM console.
  • Users without the Notify resource permission can select the Client Notification option for a device in the SCCM console. After clicking Client Notification in this scenario an exception is displayed in the console. After updating to SCCM version 2010 the option is now unavailable when the Notify resource permission is missing.
  • In an environment with a mix of HTTP and HTTPS MPs, clients may persist an incorrect or unreachable fallback location for task sequence policy retrieval.
  • Task sequences and driver packages are unexpectedly imported into their respective root folder instead of the selected folder in the SCCM console.
  • Task sequences may time out after a computer restart while waiting for the SMS Agent Host service (CCMExec.exe) to start and verify WMI performance counter data.
  • The keyboard combination of control and backspace inserts a character instead of deleting an entire word as expected in the SCCM console.
  • Collection updates may be delayed in large environments that collect frequently changing hardware inventory data, such as recently used applications. This occurs due to triggers on the CollectionNotifications table that run when processing hardware inventory.
  • Members of a software update group are not displayed in the SCCM console after clicking the View Required button.
  • Automatic deployment rules (ADRs) may not process or deploy as expected under the following conditions.
  • Multiple deployments are associated with an existing ADR.
  • The site has a certificate registration point.
  • Installation of software updates can trigger an unexpected reboot of a computer.
  • Package updates may fail in an SCCM hierarchy configured for high availability. This can occur if a package update is completed on the central administration site (CAS) while a primary site is performing a failover from active to passive mode.
  • Changes to the How many days… setting on the Deployment Ring tab in the properties of a servicing plan do not take effect.
  • The New-CMApplicationDeployment PowerShell cmdlet does not allow you to set an installation deadline for superseded applications.
  • The Next maintenance window field in the software center does not display the correct value when clients have overlapping maintenance windows.
  • CMPivot terminates unexpectedly when creating a query that has a where clause referencing a non-existent or invalid object.
  • Changes to a nested task sequence do not propagate to the parent task sequence if the package name contains a comma.
  • SCCM clients installed on Windows Server 2016 computers that are joined to Azure Active Directory may fail to communicate with HTTP MPs.
  • The Configurations tab of the SCCM control panel applet hangs and does not display results on Windows 10 ARM64 devices.
  • The Workspace ID and Workspace Key values are in opposite locations between the Microsoft Defender Advanced Threat Protection (MDATP) onboarding windows and the Microsoft Defender Security Center console. This can lead to copy/paste errors during the onboarding process.
    Synchronization of Microsoft Surface Drivers with a software update point takes longer than expected.
  • Custom SDK scripts using the SWbemObjectEx.Put_ or SWbemObjectEx.Delete_ methods may cause the WMI Provider Host Process (wmiprvse.exe) to terminate unexpectedly.
  • Error After migrating a site database server to new hardware. ConfigMgrDataWarehouse.Log for more details.
  • Deploying an uninstall action for an application group fails if the apps within the group have different revisions. The CIAgent.log will contain a VersionInfoTimedOut error entry when this occurs.
  • After a computer reboot following the installation of an application or software update, users may receive an additional notification of a pending reboot. This occurs on computers that are not joined to Azure Active Directory if they change from an Internet to Intranet location after the initial reboot.
  • The SCCM Health Evaluation task (ccmeval.exe) may run during an in-place operating system upgrade task sequence. If this occurs, the task sequence fails and the client is left in provisioning mode.
  • The smspxe.log is now updated to record which MP a DP is communicating with during the PXE boot process. This information assists with troubleshooting installation and upgrades issues.
  • The -AllowFallBack parameter of the New-CMTaskSequenceDeployment PowerShell cmdlet does not work as expected.
  • Installation of a site in passive mode fails under the following conditions.
    • The site database is using SQL AlwaysOn.
    • The SCCM database is using a named instance of SQL and a custom port for communication.
    • The site in active mode is using a default instance of SQL for the SCCM database.
  • Tenant attach device experience and device actions won’t work when running a non-English operating system date/time format.
  • The SMS Executive service (smsexec.exe) consumes more memory than expected and may terminate when the SMS_NOTIFICATION_MANAGER component processes a large number of .BLD files from the \inboxes\ folder.