SCCM 1906 Known Issues – List of Fixes

6
SCCM 1906 Known Issues

SCCM 1906 is in slow ring now and SCCM 1906 update will be available for all SCCM infrastructure with online Service Connection Point. Also, you should have versions SCCM 1806 or SCCM 1810, or SCCM 1902. In this post, you will learn more about SCCM 1906 known issues.

Related PostsSCCM 1902 known issues & SCCM 1810 Known Issues

Introduction

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

NOTE! – These issues are not blockers for SCCM 1906 production upgrade

List of SCCM 1906 KBs

  • KB4516430 (Fixes issues for SCCM 1906 Fast ring)
  • KB4514258 – Summary of changes in SCCM 1906
  • KB4515740 – Custom security roles lose folder permissions
  • KB4517137 – Computer hangs at “Just a moment” in a debug deployment for a SCCM task sequence

Subscribe to this Blog via eMail

Join 15,687 other subscribers

SCCM 1906 Known Issues – Not Fixed Yet?

There are some known issues which SCCM 1906 as per the Microsoft documentation. Some of them are just warning so that you can just ignore and/or perform workaround as mentioned below.

  • Peter blogged about the SCCM 1906 Azure AD Group Discovery bug. More details on his blog post – https://morethanpatches.com/2019/09/10/configuration-manager-aad-group-discovery-bug/
  • SCCM 1906 Setup prerequisite warning on domain functional level on Server 2019
    • When installing the update SCCM 1906 in an environment with domain controllers running Windows Server 2019, the prerequisite check for domain functional level returns the following warning: –
    • [Completed with warning]:Verify that the Active Directory domain functional level is Windows Server 2003 or later
    • Workaround
      • Ignore the warning.
  • Azure AD user discovery and collection group sync don’t work after site expansion
    • If you then expand a standalone SCCM primary site to a hierarchy with a SCCM CAS, you’ll see the following error in SMS_AZUREAD_DISCOVERY_AGENT.log:
    • Could not obtain application secret for tenant xxxxx. If this is after a site expansion, please run "Renew Secret Key" from admin console.
    • Workaround
      • Renew the key associated with the app registration in Azure AD. For more information, see Renew secret key.
  • Ben (@RealBenBruno) updated me about the issue with SCCM 1906 & AirWatch Co-existence on Windows 10 device. They have been engaged with Microsoft techs for over a month about this. Ever since updating to 1902 and even 1906, if you are running a 3rd party mdm (we are using AirWatch) SCCM disables it’s own deployments and software center.

Fixed SCCM 1906 Known Issues with latest Patches

Following are the known issues fixed with SCCM 1906 (SCCM 1906 Known Issues) slow ring version. More details available KB4516430.

SCCM 1906 Known Issues - Sample Issues
SCCM 1906 Known Issues – Sample Issues
  • Users in custom security roles no longer have access to folders in the SCCM console.
  • The SQL view vDCMDeploymentNonCompliantRuleDetailsPerClientMachine is an incorrect version after reinitializing site replication. This affects reporting of device compliance details in the SCCM console.
  • If the update to SCCM 1906, fails during the Upgrade SCCM database or Copy files steps, the installation retry will fail. This occurs if Azure Active Directory User Discovery is configured in the environment. An error resembling the following is recorded in the CMUpdate.log.
    • Violation of UNIQUE KEY constraint ‘AADDiscovery_Settings_Ex_AK’. Cannot insert duplicate key in object ‘dbo.AADDiscovery_Settings_Ex’.
  • Administrators are unable to disable the TLS 1.1 protocol after updating to version 1906.
  • The Summarize Installed Software Data fails with errors resembling the following recorded in the smsdbmon.log file.
    • Message Title – Cannot insert duplicate key row in object ‘dbo.INSTALLED_SOFTWARE_DATA_Summary’ with unique index ‘INSTALLED_SOFTWARE_DATA_Summary_idx_ByCode’.
  • The client registration process fails if the database contains duplicate client key data. This duplication may occur if the client’s certificate changes.
  • When using CMPivot from inside the SCCM console, a new client job is created after you refine a query and run it again. This can delay results being returned, and is more resource intensive on client devices.
  • The Reassign Shared Distribution Point Wizard may fail with an unhandled exception, generating the following error text in the console.
    • The given key was not present in the dictionary.
  • Changes to the Enabled status of site maintenance task are not shown in the Site Maintenance properties window without closing and reopening the window.
  • The Connection Health dashboard in the Desktop Analytics Servicing node takes longer than expected to display results.
  • Alerts are displayed in English in the Monitoring node of the SCCM console even when another alert language setting is specified.

Issues Fixed with SCCM 1906 Upgrade

The following SCCM 1906 fixes are the top reasons for upgrade SCCM 1906. Let’s check out the list of Fixes coming with SCCM 1906.

SCCM 1906 known issues will be discussed in the above section of this blog post.

SCCM Console

The following issues are fixed in SCCM 1906 production version. These were known issues of the previous versions of SCCM.

SCCM 1906 Known Issues - Console Fixes
SCCM 1906 Known Issues – Console Fixes
  1. The SCCM console can terminate with an unhandled exception when using a non-English console to edit the Site System Status Summarizer database thresholds.
  2. The Office 365 Client Management node in the console may generate an exception when trying to add items to a new device collection. Exception text resembling the following is displayed.
    • Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException​ Not found , property = ResourceType​
  3. The Bulletin ID column is replaced with Article ID on default Software Update views in the SCCM console.
  4. The Management Insights dashboard may incorrectly show Long Term Servicing Branch (LTSB) or Long Term Servicing Channel (LTSC) versions of Windows 10 as unsupported.
  5. The SCCM console may terminate unexpectedly when there are nested folders in the Packages node. This occurs when selecting the top level folder after searching for data, such as a deployment package, in the lower level folder. An exception resembling the following is displayed on screen.
    • System.NullReferenceException: Object reference not set to an instance of an object.
    • at
    • Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObjectBase.get_Item(String name)

SCCM 1906 Software Update Fixes

Following are the issues fixed in the SCCM 1906 production version.

  • The software update synchronization process takes longer than expected if the Include Microsoft Surface drivers and firmware updates option is enabled.
  • The downloading of software update content may fail with a hash mismatch error. This occurs if BranchCache is enabled on the site server, and the content for multiple update packages was uploaded to a cloud-based distribution point.
    • Errors resembling the following are recorded in the ContentTransferManger.log on the client.
    • CCTMJob::_ProcessContentInfo – failed to verify hash (….
    • CCTMJob:_ProcessContentInfo failed. (0x87d00217)
  • Phased deployments of software updates will fail if the Suppress Reboot option is enabled for both workstation and server operating systems. An error resembling the following is recorded in the sms_PhasedDeployment.log file. Note this entry is truncated for readability.
    • Exception: System.Data.SqlClient.SqlException (0x80131904): Parameter ‘@SuppressReboot’ was supplied multiple times.
  • Administrators are unable to move updates from one software update group to another if those updates are not downloaded directly, but instead distributed via BranchCache.
  • Synchronization of SUP in large environments may take much longer than expected due to inefficiencies in the SQL views and indexes used during the process.
SCCM 1906 Known Issues - Sample Picture SCCM Third-Party Software Updates
SCCM 1906 Known Issues – Sample Picture

SCCM 1906 Client Fixes

The following are the SCCM client known issues fixed with SCCM 1906 production release.

  • After removing the Application Catalog role from a site, clients may continuously request a non-existent policy from the management point. This occurs because the associated web service policy is not correctly tombstoned on the client.
  • DataTransferService Jobs may fail if the client computer restarts while the job is still running. This occurs due to a timing issue during computer shutdown that results in an incorrect status being returned for a Background Intelligent Transfer Services (BITS) job.
  • A client may become unmanaged if it has a wi-fi profile certificate installed, and the client is installed using the cloud management gateway.
  • After performing an in-place upgrade of the operating system from Windows Server 2012 R2 to Windows Server 2016, the SCCM Health Evaluation scheduled task no longer functions. Client check results are reported as failed, and attempts to run the task from Task Scheduler result in the following error.
    • An error has occurred for task SCCM Health Evaluation. Error message: A task or folder with this name already exists.
  • An automated deployment rule (ADR) for an update package may fail if software update synchronization is removing expired content from the same package.
  • Clients are unable to download content or policies after repeated historical download failures. The data transfer service (DTS) jobs are suspended but restarting the SMS Agent Host (ccmexec) service causes downloads to resume. When the client is in this state, errors resembling the following are recorded in the DataTransferService.log on the client.
    • DTS job {guid} BITS job {guid 2} failed to download source file {filename}.exe to destination {client cache filename} with error 0x80072EE7
  • Users are unable to search in Software Center when the client operating system is configured with the Japanese locale and calendar.
  • User Deployments are not visible in Software Center when the client communicates with a Management Point that uses a replica database.
  • A remote control session to a SCCM client will fail within a few seconds of connection. This occurs if the Teredo tunneling adapter is enabled on the client.
SCCM Client Health Issues - Sample Picture - SCCM 1906 Known Issues
Sample Picture – SCCM 1906 Known Issues

SCCM 1906 Site System Fixes

SCCM 1906 known issues are listed down. SCCM 1906 production version comes with following fixes for Site system servers.

  • The SMSDPProv.log contains false errors when enhanced HTTP mode is not enabled. In this scenario, the error “Failed to verify if the cert is sccm issued, 0x800b0109” is not indicative of a problem state and can be ignored.
  • The list of SMS Providers is inconsistent after promoting a passive site server to active. The failover process succeeds, but remote providers are not listed in WMI or the Registry on the recently promoted site server.
  • When custom client settings are used, changes to User Device Affinity (UDA) settings are not applied unless the “User device affinity usage threshold (minutes)” setting is also changed.
  • The SMS Executive service (smsexec.exe) may terminate unexpectedly when distributing multiple large (multi-gigabyte) packages at the same time to a pull distribution point.

SCCM 1906 Reporting Issues

SCCM 1906 fixes the slowness in the 2 default reports listed below.

  • The following reports may take significantly longer (hours) to run than expected because of an inefficiency in an associated SQL function
    • Software Distribution Content / All Active Content Distribution
    • Software Distribution – Content / Application Content Distribution Status

Resources

6 COMMENTS

  1. since i upgraded to 1906, i have to frequently restart WMI service on my SMSPROVIDER Servers in order to fix console crash issue.

    and i also can’t download software updates anymore (patchdownloader says :
    ERROR: DownloadContentFiles() failed with hr=0x80041013

  2. Hi,
    Are you a ware about the below:

    Current version: 1906
    Scenario: Bare-Metal deployment – PXE
    Windows 10 deployment task sequence finish successfully but then I notice the following issue on the client:
    1- SCCM agent is installed
    2- SCCM client not receiving any policy from SCCM
    3- SCCM client showing on console with No agent installed
    4- I found “unknown computer” record on console
    this issue didn’t occur when I’m using Task Sequence Media (USB)

  3. After upgrading 2 labs and Production to 1906 I noticed that the Details pane in Distribution Point Configuration Status takes a very long to load and occasionally comes back with no results (I believe the query is timing out)

    Sometimes when it does load it has lots of messages that did not show here prior to 1906 and they have no status icon. For instance it is getting Notification Server Messages

    The query shows in SQL as an Expensive Query. I was able to copy the actual query and run it directly in SQL Management Studio and it took 3 1/2 minutes to complete.

    Have you seen this behavior? Any idea if Microsoft is aware? I did send a frown this morning and am waiting to see if they reply.

    Query:
    select all SMS_DPStatusDetails.DPName,SMS_DPStatusDetails.ID,SMS_DPStatusDetails.InsString1,SMS_DPStatusDetails.InsString10,SMS_DPStatusDetails.InsString2,SMS_DPStatusDetails.InsString3,SMS_DPStatusDetails.InsString4,SMS_DPStatusDetails.InsString5,SMS_DPStatusDetails.InsString6,SMS_DPStatusDetails.InsString7,SMS_DPStatusDetails.InsString8,SMS_DPStatusDetails.InsString9,SMS_DPStatusDetails.LastStatusTime,SMS_DPStatusDetails.MessageCategory,SMS_DPStatusDetails.MessageFullID,SMS_DPStatusDetails.MessageID,SMS_DPStatusDetails.MessageSeverity,SMS_DPStatusDetails.MessageState,SMS_DPStatusDetails.NALPath,SMS_DPStatusDetails.PackageID,SMS_DPStatusDetails.SiteCode,SMS_DPStatusDetails.StatusMsgID from vSMS_DPStatusDetails AS SMS_DPStatusDetails where SMS_DPStatusDetails.NALPath = N'[“Display=\\\”]MSWNET:[“SMS_SITE=”]\\\’ OPTION(USE HINT(‘FORCE_LEGACY_CARDINALITY_ESTIMATION’))

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.