[Fix] List of SCCM 1806 Known Issues – Documented

5
SCCM 1806 known Issues

Microsoft released a couple of update rollups (hotfixes) for the latest production version of SCCM 1806. In this post, we will see the SCCM 1806 known issues and how to fix those known issues. The Video tutorial will help you to understand how to install SCCM 1806 hotfix. SCCM 1806 known issues are already fixed by Microsoft SCCM team.

[Related Post – How to Upgrade SCCM Infra to 1806 Production Version and SCCM 1806 New Features Changes a Video Walkthrough]

Fix to SCCM 1806 Known Issues?

Microsoft already released two hotfixes to fix all the documented known issues for the 1806 version of SCCM. So all the issues highlighted in the post are already fixed with the latest hotfixes or the latest version of 1806.

SCCM updates and servicing is intelligent enough to filter out unwanted updates hotfixes from your SCCM console. So most probably if your SCCM  environment requires an update, it would be visible in your SCCM console.

Updated on 2nd Oct 

Microsoft released another hotfix for SCCM 1806.

https://support.microsoft.com/en-us/help/4465865/software-updates-do-not-download-in-configmgr-if-wsus-is-disconnected

How to Confirm Hotfix is Required for SCCM Environment?

You can confirm whether the SCCM 1806 hotfix is required for your environment by comparing the SCCM updates and servicing package guide. To verify which wave build is installed, look for a package GUID by adding the Package GUID column to the details pane of the Updates and Servicing node in the SCCM console.

SCCM 1806 Known Issues

List of SCCM 1806 Known Issue

Following list provides SCCM 1806 Known issues. I will try to update it whenever Microsoft releases new hotfixes.

  1. After the WDS-less PXE responder service is configured after an upgrade to SCCM 1806, it may reject PXE-boot requests from clients when the management point (MP) is remote.
  2. Task sequences that have a restart action before an Install Packages action may fail.
  3. Unable to delete a secondary site. After the deletion action, the site remains in either an “active” or “deleting” state
  4. CMPivot cannot run a PowerShell script that contains a command to retrieve a registry entry if the registry contains a NULL value.
  5. The SCCM console crashes if you create or edit an ADR and set the deployment package to “No deployment package.”
  6. CMPivot is missing the “not like” operator.
  7. CMPivot fails to run a PowerShell script that contains a command to retrieve a registry entry if the registry value contains a NULL.
  8. Ccmexec crashes continuously when Pull DPs are installed.
  9. OfflineServicingMgr fails to find the content library location when the Content Library is on a Universal Naming Convention (UNC) path.
  10. OfflineServicingMgr leaks handle and cause a decrease in performance if it fails to find the content library location on a UNC path.
  11. When you edit an existing co-management policy, instead of the changes being saved, the policy is reset to the default state of No AutoEnroll, all workloads set to SCCM, and pilot collection is empty.
  12. CRP certificate revocation is processing slowly and is blocking the main thread in SMS_CERTIFICATE_MANAGER.
  13. On upgrade, if you have any deployments that require approvals that reference built-in CIs created before 1706, you will see significant SQL I/O and high CPU utilization on the MPs as the CIs and deployments are updated.
  14. Phased Deployment Status Wizard shows multiple rows for the same phase with inconsistent data when a collection has machines spread across multiple sites.
  15. Count of AADJoined and HybridAADJoined may be incorrect on the Co-Management dashboard.
  16. Excessive client request time-outs on the cloud management gateway.
  17. After an upgrade to 1806, the performance of the site may be decreased with high I/O and CPU use by sp_UpdResPolicyMap_PolicyAssignment.
  18. Super peers may fail to download partial content when the management point is remote.
  19. State message component SMS_STATE_SYSTEM reported as critical because of a backlog of Script state messages with no output data reported as corrupt.
  20. Download fails when you use CCM client Delta Download channel to download express updates full files.
  21. The process MP_GetSuperPeerContentLocations stored proc may cause decreased SQL performance and block threads.
  22. Pull DPs may fail to be upgraded because MOFCOMP silently fails when Distribution Manager run it. If the Pull DPs are not upgraded, content cannot be downloaded.
  23. The online client status chart on the CMG Dashboard does not aggregate hourly data correctly from multiple MPs.
  24. When you create an SRM based CMG or CDP by using an existing resource group, the region of the resource group is used to create the resources regardless of the region that you specified.
  25. DP upgrade fails If PXE without WDS enabled.
  26. CMPivot returns NULL if any registry entity values are NULL.
  27. BCP for BGB_NetworkInfo live data fails if there is a duplicate subnet for the same IP address and same client.
  28. CMG HTTP listener stops because of an HttpListenerException.
  29. After WDS-Less PXE is enabled, some clients may not start Task Sequence Wizard because a password is incorrectly expected when multiple clients start at the same time. SMSTS.log shows that the password is incorrect even though the wizard not displayed and no password is set.
  30. On a passive site server, the state message files in the management point staging folder may not process.
  31. The WDS-less PXE responder service, configured after upgrade to SCCM 1806, may reject PXE-boot requests from clients when the management point (MP) is remote.
  32. AtomicUpdate and BundledUpdate metadata used for delta download can get truncated. This causes Unified Update Platform (UUP) updates not to be downloaded.
  33. When the SCCM generated certificate option is selected for the site, and a client fails to download content because it does not have the client public key infrastructure (PKI) certificate if the client is restarted it will still fail to download content even if token-based content locations are available.
  34. After the 1806 upgrade, SCCM clients fail to send client or Management Point (MP) communication status Fallback Status Point (FSP) messages.
  35. When content that downloads from delta download or CMBITSMgr, the optimal content location is not chosen for all content within a package.
  36. Some client state messages may not be sent, resulting in some reports such as co-management, Windows Upgrade for Business and deployment upgrade reporting being out of sync.
  37. An Internet-only AAD-joined device cannot register if an MP was removed from cloud management gateway.
  38. Task sequences that have a restart action before an Install Packages action may fail.
    Unable to delete a secondary site. After the deletion action, the site remains in either an “active” or “deleting” state.
  39. After you update to SCCM, version 1806, software updates do not download. This failure occurs only in environments that use Windows Server Update Services (WSUS) on a disconnected (air gapped) network.
  40. For software updates that contain express installation files, SCCM synchronizes the Express.cab file and distributes it to the client. This behavior occurs even if the client does not require the Express.cab file for a given deployment.

Resources

1806 Slow Ring – https://support.microsoft.com/en-us/help/4459354/interoperability-update-for-system-center-configuration-manager

1806 Fast Ring – https://support.microsoft.com/en-gb/help/4346645/update-for-system-center-configuration-manager-version-1806-first-wave

https://support.microsoft.com/en-us/help/4465865/software-updates-do-not-download-in-configmgr-if-wsus-is-disconnected

5 COMMENTS

  1. hi sir,i am try to install the sccm client in a test machine but the sccm client is not installed in a test machine.i tried many ways but the sccm client is not installed in a test machine.please help me on this sir

    thanks
    babitha

  2. Hi Anoop,

    Can you please guide me how I can fix KB4465865 installation error?
    When I am trying to install Hotfix Rollup on SCCM 2016 (1806) facing following error:
    Failed to apply update changes 0x80004005
    Error information persisted in the database.
    ERROR: Failed to process configuration manager update.

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.