SCCM 1810 Known Issues and FIXES

13
SCCM 1810 Known Issues

I’m trying to help SCCM community with this list of known issues which are already fixed (well, most of them) with the latest slow version of SCCM 1810. Microsoft can fix the critical issues on the fly with new cloud connected updates and servicing. Let’s checkout the list of SCCM 1810 Known Issues.

*****Last updated on 23rd Feb 2019

[Related Post – List of SCCM 1806 Known Issues – Documented]

Contents

List of SCCM 1810 KBs or Roll UP

  • SCCM 1810 KB4487768 – Error “Conversion failed” when you upgrade to Configuration Manager version 1810.
  • SCCM 1810 KB4486457 – Update rollup for SCCM 1810 – 30+ SCCM 1810 known Issues are FIXED in the KB 4486457.
  • SCCM 1810 KB4490575 – Fix – Update installations stop responding or never show completion in SCCM.
  • SCCM 1810 KB4490434 – Fix – Duplicate user discovery columns are created in SCCM

Issues Fixed with SCCM 1810

Most of the known issues of SCCM 1806 are fixed in 1810 version of SCCM. The following KB gives you an idea about fixes in SCCM 1810 version. More details available in Microsoft KB Articles Mentioned below:

How to Fix SCCM 1810 Known Issues?

 First of all known issue means, these are already documented issues within Microsoft and by the SCCM community. Microsoft is already providing a list of urgent issues in the SCCM release notes here.

As I mentioned above, Microsoft already identified fixes for most of the SCCM 1810 Known Issues listed below. But, the best approach to fix the issue is to raise a support case with Microsoft. If the issue is known, then Microsoft won’t charge you for the support case.

Also, Microsoft will provide a workaround to fix the known issue. This will also help Microsoft to include the fix in the SCCM 1810 hotfix or rollup update.

My recommendation is to install and update your SCCM infrastructure with latest KB or HotFix. Also, use the workarounds which you get from Microsoft support and community members to solve the problem which could block your upgrade.

I would recommend to test all the upgrade and all the features in pre production or staging environment before upgrading the SCCM production environment.

List of SCCM 1810 Known Issues

The following list which is already known to Microsoft SCCM (SCCM 1810 Known Issues) support team. I try to keep this SCCM known issue list updated whenever I get time. Also, to help SCCM admins and community, report any new issues you find with SCCM 1810 which are not listed here.

  1. SCCM 1810 download got stuck and can’t proceed further? Do you have similar issue?
    • I would recommend reading this post to get more details about fixing the SCCM upgrade download issues. 
  2. Do you have SCCM 1810 Prerequisite check errors or warning? Microsoft has already documented all the details related to SCCM 1810 errors and warning. Checkout the list of SCCM 1810 Known Issues to get more details.
    • I would recommend reading the document here.
  3. SCCM 1810 won’t get installed because Prerequisite check keeps failing on “Pending system restart”. So checkout your all remote site system servers (Remote SQL etc..) whether there is any restart pending. The following registry keys will help you to understand restart pending status on SCCM servers. More details here.
    • HKLM:Software\Microsoft\Windows\CurrentVersion\Component Based Servicing\RebootPending
    • HKLM:SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired
    • HKLM:SYSTEM\CurrentControlSet\Control\Session Manager, PendingFileRenameOperations
    • HKLM:Software\Microsoft\ServerManager, CurrentRebootAttempts
  4. SCCM 1810 console All Devices (\Assets and Compliance\Overview \Devices) tab does not point to HOME tab in the ribbon menu. Instead, it’s opening Endpoint protection.
  5. SCCM 1810 opt-in ring has an Automatic Deployment Rule (ADR) related issue. After SCCM 1810 upgrade the existing ADRs are automatically shifting to No Deployment package “Clients download content from peers or the Microsoft cloud“.
    • If you have selected any-other options like Select a Deployment Package or Create a new Deployment Package in your ADR, then after the SCCM 1810 upgrade it will automatically change to No Deployment package option.
  6. Package replication/distribution failed after SCCM 1810 upgrade – Failed to copy C:\Program Files\Microsoft Configuration Manager\bin\x64\ccmcore.dll to \DistributionPoint\SMS_DP$\sms\bin\ccmcore.dll. GLE = 32
  7. SCCM 1810 Reports – No data is displayed when running the report Software 06A and drill down to the next level. Checkout the list of SCCM 1810 Known Issues and upcoming hotfix releases to get more details.
  8. The “User Nameattribute is changed after SCCM 1810 upgrade. This is already fixed in the latest version of SCCM 1810 slow ring.
  9. Collections that have incremental updates has a known issue with SCCM 1810 Powershell commandlet parameters New-CMSchedule with -DurationInterval and -DurationCount.
    • Error Message is similar to following -> *** [22018][245][Microsoft][SQL Server Native Client 11.0][SQL Server]Conversion failed when converting the nvarchar value ‘D’ to data type int.
    • Resolution details – here
  10. Unable to send update on component PolicyTargetEvalNotify_iud after upgrade to SCCM 1810 (known issues). More details about by this issue is explained by Paul in this blog post here.

FIXED ISSUES with Rollup – SCCM 1810 Known Issues

  1. Synchronization of Office 365 updates may fail after you update to SCCM 1810. Errors messages that resemble one of the following are recorded in the WSyncMgr.log file:
    • ProcessFileManifest() failed to process O365 file manifest. Caught exception: System.Net.WebException: An exception occurred during a WebClient request.
    • ProcessFileManifest() failed to process O365 file manifest. Caught exception: System.UriFormatException: Invalid URI: The URI scheme is not valid.
  2. The SCCM DP upgrade process may fail. This causes a block of additional content distribution to that server.
  3. All superseded updates are removed and no are longer applicable on a client, even before expiration. This issue occurs even if the Do not expire a superseded software update until the software update is superseded for 3 months option is enabled.
  4. Performance improvements have been made to the Data Replication Service for device discovery data.
  5. The second and successive phases of a deployment start automatically after the success of the first phase, regardless of start conditions.
  6. Phased deployment deadline behavior settings are inconsistent between the Create Phased Deployment Wizard and the Phase Settings properties.
  7. When you run a Servicing Plan after you select a Product Category, the filter is not added correctly.
  8. The Cloud Management Gateway (CMG) content service is not created correctly when the CMG role is added after you update to SCCM 1810.
  9. The No deployment package option is selected after you change the properties of an Automatic Deployment Rule (ADR). After this update rollup is applied, affected ADRs can be re-created and their properties changes without any further issue.
  10. The SCCM Message Processing Engine (MPE) may not always process Active Directory discovery data when optional attributes are added.
  11. The Service Connection Tool (serviceconnection.exe) fails and you receive the the error message when you use the -connect parameter.
  12. A user without Full Administrator rights may be unable to create or edit Windows Defender ATP Policies, even when you add them to the Endpoint Protection Manager security role.
  13. The Prerequisite Installation Checker incorrectly gives the option to retry a site installation again. If a second retry is tried, the administrator must run the SCCM Update Reset Tool (CMUpdateReset.exe) to resolve the issue.
  14. Processing of .bld files by the SMS_Notification_Manager component takes longer than expected. This leads to delays in processing data and a backlog of files in the \inboxes\bgb.box folder.
  15. After you update to SCCM 1810, remote SQL providers who use Microsoft SQL Server 2014 or an earlier version may not always query the database.
  16. The Software Updates Patch Downloader component retries updates, up to three times. These retries fail and return error code 404.
  17. Windows Server 2016 updates are displayed incorrectly as available when you schedule updates to a Windows Server 2019 operating system image.
  18. Searching for a user’s first or last name, or full name, returns no results from the Overview section of the Assets and Compliance node of the SCCM console. This issue occurs even when full discovery data is available.
  19. After you enable support for express installation files, content may not always download from Windows Server Update Services (WSUS) servers in the following scenarios:
    • SCCM client installation through Software Update Point
    • Installing updates directly from WSUS
    • Windows Feature on Demand (FOD) or Language Pack (LP) acquisition
  20. After you update to SCCM 1810, device enrollment can overwrite Windows telemetry collection values that were previously set by Group Policy. This issue can cause value toggling between full and basic, for example, when Group Policy is applied.
  21. Hardware inventory is updated to include information about add-ins for Office365 and standalone Office products.
  22. Desktop Analytics deployment plans show a larger device count in the SCCM console than in the Desktop Analytics Portal.
  23. SCCM client setup may fail over a metered (for example, cellular) network connection. This may occur even if client policy settings allow for those connections.
  24. Client deployment cannot be fulfilled because use of metered network is not allowed.
  25. Client setup may fail because of SQL Server CE schema changes. Errors that resemble the following are recorded in the Ccmsetup-client.log on the client:
    • MSI: Setup was unable to compile Sql CE script file %windir%\CCM\DDMCache.sqlce. The error code is 80040E14.
  26. If an application is in a partly compliant state, and the client sees that a dependency is installed but the main application is not and requires re-enforcement, available deployment causes the following issues:
    • The application is displayed as required or past due even though the deployment is available and there is no supersedence relation.
    • Clicking Install has no effect.
  27. Sign in to Azure services fails when you use the Create Workflow in the Azure Services Wizard, even when correct credentials are used.
  28. SCCM setup may fail the prerequisite check during installation or an update of a site server. This issue occurs if the environment uses SQL Always On.
    • The “Firewall exception for SQL Server” rule shows a status of failed, and errors messages that resemble the following are recorded, even if the correct firewall exceptions are configured:
    • ERROR: Failed to access Firewall Policy Profile.
    • ERROR: Failed to connect to WMI namespace on
    • Firewall exception for SQL Server; Error; The Windows Firewall is enabled and does not have exceptions configured for SQL Server or the TCP ports that are required for intersite data replication.
  29. The alternative download server that is listed in the “Specify intranet Microsoft update service location” window is not propagated to the Group Policy settings on the client.
  30. The download of Office 365 updates, such as “Semi-annual Channel Version 1808 for x86 Build 10730.20264” or “Monthly Channel Version 1812 for x64 Build 11126.20196” may fail. No errors are logged in the Patchdownloader.log file. However, entries that resemble the following are logged in the AdminUI.log log:
    • (SMS_PackageToContent.ContentID={content_ID},PackageID='{package_ID}’) does not exist or its IsContentValid returns false. We will (re)download this content.
  31. Software update installations may stop responding or never return a completion status during task sequence execution or typical software updates management (SUM). This issue typically occurs when many updates are being installed, usually a mix of Office and Windows updates. FixedKB 4490575
    • Wait – Update (Site_73523994-7973-422C-A02B-F83A7A327F36/SUM_cca31bf2-b813-48d1-a4cd-ce317d024303) Progress: Status = ciStateDownloading, PercentComplete = 0, Result = 0x0 UpdatesDeploymentAgent
  32. After SCCM 1810, multiple duplicate columns may be created in the user discovery data table (User_DISC). If this occurs, features that rely on Active Directory User Discovery data, such as collection or query results, or user-targeted software deployments, may return incomplete or incorrect results. Fixed – KB4490434

Resources

Coming Soon…..

13 COMMENTS

  1. Hi Anoop,
    I have SCCM 1802 environment running and I recently upgraded from 1606 to 1802.

    Post upgrade, 50% of the clients machines stopped reporting in SCCM 1802 and machine was active, but, in SCCM client status says none..

    Fixing the cleint in each and every desktops practically not possible. is there any way to fix this issue from server end.

    Thanks,
    Sundar

    • Hi Sundar – Have you upgraded the client version to 1802 as well ? How did you upgrade the clients? If not upgraded the clients, then I would recommend testing that with some of the problematic clients.

      • Clients are getting upgrade automatically via client Push. The problem, clients are not installing all the discovered machines from environment. only half of the machines are upgraded with latest client. Machines which are reported with old clients, stopped reporting and not picking up the 1802 clients.

      • It is already fixed if you have the latest build (Client 8740.1012). I can only get to that build if i update now from SCCM 1806. But if you upgraded to the affected build (Client 8740.1004) via Fast Update Ring, there is no way to patch to the fixed Client Build 8740.1012.

  2. I’ve been seeing an odd issue since upgrading and hard to tell whether it’s 1810 related or coincidence – but nearly every time i do ‘update distribution points’ on a package, about 50% of my DPs will instantly changed to failed status with “Distribution Manager failed to connect to the distribution point” and the logs show error 0x40 trying to access the DP’s ADMIN$ share – but i can access them perfectly fine via windows explorer, and if i just select redistribute content it then works fine the 2nd time..

  3. The CMG content service is not created correctly when the CMG role is added after you update to SCCM 1810.
    What does the “content service” mean? Storage account in Azure?
    thank yoy

  4. Hi Sir ,

    We need your help or suggestions post installation of wsus role getting event I’d 507 and we are using SQL 2016 express versions on getting error
    A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. … The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections.

    Name pipe provided error 40 could not open SQL connention server

    Please suggest for resolution if you contact us it’s great help us..

      • After configuring wsus on 1806 version and ant the of post configurations we are getting these error and SUP is not yet configured @⁨Dinesh_G⁩

        Please contact :- 9766633800

  5. After configuring wsus on 1806 version and ant the of post configurations we are getting these error and SUP is not yet configured @⁨Dinesh_G⁩

    Contact 9766633800

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.