SCCM 1810 Known Issues and FIXES

40
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 7th April 2019 with new KBS released for SCCM 1810

[Related Post – SCCM 1902 Known Issues & SCCM 1902 Production Upgrade Step by Step Video Guide here]

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

SCCM 1810 Rollup Updates

  • Rollup Update #1 is replaced by following update KB4488598 – SCCM 1810 KB4486457 – Update rollup #1 for SCCM 1810
  • Rollup Update #2 – SCCM 1810 KB4488598 – Update rollup #2 for SCCM 1810. The following updates are included in this rollup update #2 KB4490575, KB4490434, and KB4487960

List of SCCM 1810 KBs

  • SCCM 1810 KB4487768 – Error “Conversion failed” when you upgrade to Configuration Manager version 1810.
  • 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
  • SCCM 1810 KB4494361 To Fix Issues related attaching SCCM 1810 CAS to a stand-alone primary site fails when two-factor authentication is enabled
  • SCCM 1810 KB4494362 – To Fix Issues related “Unable to send update on component PolicyTargetEvalNotify_iud” is repeatedly logged in Smsdbmon.log after you update to SCCM 1810
  • SCCM 1810 KB4495265 – To Fix Issues related to WINHTTP_CALLBACK_STATUS_FLAG_CERT_CN_INVALID when using a CMG as a cloud DP with third-party certificate
  • SCCM 1810 KB4494015 – Fix SCCM OSD task sequence doesn’t continue after Windows Setup or an in-place upgrade finishes
  • SCCM 1810 Known Issue – KB4498264 – Fix the Duplicate rows in DistributionContentVersion table after you reassign a DP in SCCM
  • KB4498259 – To fix Upgrade Readiness data is downloaded continuously in SCCM

SCCM 1806 Issues Fixed with 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.

Parallels Mac Management with SCCM
Advertisement

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 SCCM 1810 Rollup Update 2

  1. Client computers incorrectly report as being on an intranet when they receive a 404-redirect request from an internet-facing network.
  2. The PXE responder does not use the value set in the registry under HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\DP\RamDiskTFTPBlockSize for boot files in an operating system image.
  3. The “Send a smile” and “Send a frown” feedback options are updated to support TLS 1.2.
  4. After you use the “Send a smile” or “Send a frown” feedback options to include a screenshot from the SCCM console, the resulting .PNG file cannot be deleted until the console is closed.
  5. Feedback that was submitted through the UploadOfflineFeedback.exe tool does not include screenshots as expected.
  6. The OSDDoNotLogCommand task sequence variable does not affect the Command Line value printed in the smsts.log file.
  7. After promoting a passive site server, the default boot image refers to package source on the previously active site server. This can cause boot image packages to fail if the previously active server is no longer available.
  8. Windows Server 2019 updates are not shown in the wizard when scheduling updates for offline servicing of an operating system image.
  9. Notification messages displayed on a client computer by Restart Client feature (reboot coordinator) may show the incorrect local date/ time format.
  10. Pull-distribution points may fail to download package data, with errors resembling the following recorded in the PullDP.log file:
    • CPullDPPkgContJob::LoadContentJobFromXML() unable to read DP location or rank!
    • CPullDPPkgContJob::LoadContentJobFromXML() could not fully load job! Malformed or incomplete XML. Job has failed.
  11. This may occur because of intermittent network failures between the pull DP and the MP (management point).
  12. After selecting Devices from the Assets and Compliance section of the SCCM console, the view shows the Endpoint Protection tab instead of the home tab.
  13. A semicolon that is used to separate multiple email messages from the Approve application via email properties window is overwritten with a comma. This can prevent email messages from being sent to multiple recipients as expected.
  14. When you deploy an operating system image, the Configure network settings button is unavailable after you click the Back button following a task sequence error.
  15. The Software 06A – Search for installed software and Software 06B – Software by product name reports do not return data as expected after you update to SCCM 1810.
  16. The keyboard shortcuts for product feedback may not function as expected in German or other non-English input locales.
  17. Administrators cannot delete Windows Defender Exploit Guard policies after enabling them for client computers. An error entry that resembles the following is recorded in the ExploitGuardHandler.log file.
    • Delete not supported
  18. Operating system deployments may fail or take longer than expected when trying to download content from a distribution point in an environment using HTTPS and a PKI infrastructure. Error entries that resemble the following are recorded in the smsts.log file.
    • Note These entries are truncated for readability.
    • GetDPAuthDownloadToken() failed. 80090003
    • Unable to get the DP auth token from MP
    • Trying https://{distribution_point}/CCMTOKENAUTH_SMS_DP_SMSPKG$/{package_ID}.
    • Content source is a DP token auth capable, but DP auth token is not available
  19. Clients that are configured for internet-based client management may fail to run software distribution packages from a distribution point in a fast network boundary.
  20. Application content downloads that occur during deployment of a new operating system image installation fail to use the Windows PE Peer Cache as expected. This occurs even when the SMSTSPeerDownload and SMSTSPeerRequestPort task sequence variables are configured. Error entires that resemble the following are recorded in the DataTransferService.log file:
    • CCMHTTP] ERROR: URL=https://{host}:{port}/SCCM_BranchCache$/Content_{Content_GUID}, Port={port}, Options=480, Code=0, Text=CCM_E_BAD_HTTP_STATUS_CODE
    • Request to https://{host}:{port}/SCCM_BranchCache$/Content_{Content_GUID} failed with 401 – Access denied
    • GetDirectoryList_HTTP(‘https://{host}:{port}/SCCM_BranchCache$/Content_{Content_GUID}’) failed with code 0x80070005.
  21. The Message Processing Engine (MPE) that is used by the Run Scripts and CMPivot features cannot process Active Directory User data if there is an ampersand (&) in the OU path. Error entries tha resemble the following are recorded in the SMS_Message_Processing_Engine.log:
    • XML parsing: line 1, character 141, illegal name character
  22. Clients fail to download task sequence content from other peer-cache enabled computers. This casues content to be transferred from distribution points instead.
  23. After updating to SCCM 1810, the All Package and Program deployments to a specified computer report does not correctly display information for a specific program when selected.
  24. The client authentication certificate is not updated in Azure Storage when a cloud management gateway distribution point is installed CMG-DP is installed in a Central Administration Site (CAS) environment.
  25. Clients do not automatically wake using the wake on LAN feature when deadlines for mandatory software distribution, software update, or task sequence deployments are reached.
  26. After updating to SCCM 1810, the SMS Agent Host service (ccmexec.exe) may consume 100 percent of the CPU. Error sequences that resemble the following are repeated in the M365AHandler.log file:
    • Running: “C:\Windows\system32\CompatTelRunner.exe” -m:appraiser.dll -f:DoScheduledTelemetryRun ent
    • Executing command line: Run Appraiser
    • CreateProcess failed. Code(0x80070002)
    • Command line execution failed (80070002)
    • CommandLine.Execute() failed.
    • CM365ASystemTask:RunAppraiser() failed. 0x80070002.
  27. The Delete duplicate system discovery database maintenance task fails and returns error entries that resemble the following in the Smsdbmon.log file:
    • SMS_DATABASE_NOTIFICATION_MONITOR Description: Microsoft SQL Server reported SQL message 245, severity 16: [22018][245][Microsoft][SQL Server Native Client 11.0][SQL Server]Conversion failed when converting the nvarchar value ‘INFO: Processing SID={User_SID}, ItemKeyToKeep=’ to data type int. : spRemediateDuplicateSMSID ​
  28. The SMS State System component may return error status messages that resemble the following:
    • Microsoft SQL Server reported SQL message 547, severity 16: [23000][547][Microsoft][SQL Server Native Client 11.0][SQL Server]The MERGE statement conflicted with the FOREIGN KEY constraint “ClientOperationSummary_ClientOperation_FK”. The conflict occurred in database “ConfigMgr”, table “dbo.ClientOperation”
    • This occurs due to an error running a client notification-related stored procedure.
  29. The SMS Executive service (smsexec.exe) may terminate unexpectedly after Active Directory User Discovery runs if the site processes data that has an ampersand (&) in the name.
    • Note This crash is inconsistent and may not coincide with every run of Active Directory User Discovery.

Fixed Issues – SCCM 1810 Rollup Update 1

  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…..

40 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

  6. Hi, has anyone encountered the following issue?: I have updated SCCM from 1709 to 1810, then added the hotfix KB4488598, all done yesterday. Everything seemed fine until I tried to install a new Distribution Point today. I added it with exactly the same configuration as dozens before. When the process finished, the Servers and Site Systems entry was created with the Distribution point Role, but the DP did not show up in Distribution Points, Distribution Point Configuration Status, Component Status, SQL queries or the distmgr.log. It seems like it was never added to the database. When I open the properties of the Distribution Point Site System Role, I get 3 tabs less then usual: Schedule, Rate Limits and PullDP tabs are missing. I have tried all trivial troubleshooting steps, deleted and readded the role, the site system, rebooted the primary, etc. I tried with another computer added as DP, same effect. The Console is showing the correct version, so the upgrade worked. All older DPs replicate normally, but I did not try to reinstall any as I am quite sure that would not work either,
    Any suggestions are welcome. Thank you!

  7. Issue resolved itself. For those of you who get into the same situation: Wait a day before trying to add a DP after the upgrade. Not sure what was still going on, but 12-13 hours after the upgrade the DP started to install all of a sudden without any intervention from my side. I’ll test with another one next week, for now I am happy it works…

  8. Installed Rollup 2
    Still no updates in Schedule updates Wizard for Server 2019…

    Hotfix kb4490434 still remains visible as ready to install in console updates and servicing, is this still applicable when Rollup 2 is installed?

    • I can’t see this in my environment. It should not be visible if it’s not required. But the idea is you can check whether you need the KB 4490434 … analyse whether you are getting the issues on Server 2019 servers with discovery? If so, I think you need to apply or raise a support case with Microsoft.

  9. Hi Anoop,
    I was trying to upgrade my SCCM CB 1802 (Hotfix 2 installed) on 1810, but apparently its stuck in “Checking Prerequisites”.

    I have tried CMUpdateReset tool twice and rebooted server already but it didn’t make any difference.

    Under Update and Servicing Status it shows Content Replication succeeded.

    Don’t have MS Support available. Any help is appreciated.

  10. Thanks Anoop for reply: For 1810 Package GUID 454B3508-4387-4106-9441-283495DEC3EC related, I have only found below entries in hman.log (Some Errors found)

    Path is not found. Skip import metadata file of language 00000c04 for CM update 454B3508-4387-4106-9441-283495DEC3EC SMS_HIERARCHY_MANAGER 4/24/2019 3:52:45 PM 5816 (0x16B8)
    Path is not found. Skip import license file of language 00000c04 for CM update 454B3508-4387-4106-9441-283495DEC3EC SMS_HIERARCHY_MANAGER 4/24/2019 3:52:45 PM 5816 (0x16B8)
    Successfully saved Configuration manager update 454B3508-4387-4106-9441-283495DEC3EC

    Check CMU status… SMS_HIERARCHY_MANAGER 4/24/2019 3:53:05 PM 5816 (0x16B8)
    Successfully checking Site server readiness for update. SMS_HIERARCHY_MANAGER 4/24/2019 3:53:05 PM 5816 (0x16B8)

    Created notification file (454B3508-4387-4106-9441-283495DEC3EC.CMI) for CONFIGURATION_MANAGER_UPDATE SMS_HIERARCHY_MANAGER 4/24/2019 3:53:05 PM 5816 (0x16B8)
    There are update package in progress. Cleanup will skip this time. SMS_HIERARCHY_MANAGER 4/24/2019 3:53:05 PM 5816 (0x16B8)

    Created notification file (454B3508-4387-4106-9441-283495DEC3EC.CMI) for CONFIGURATION_MANAGER_UPDATE SMS_HIERARCHY_MANAGER 4/24/2019 4:03:12 PM 5816 (0x16B8)
    There are update package in progress. Cleanup will skip this time. SMS_HIERARCHY_MANAGER 4/24/2019 4:03:12 PM 5816 (0x16B8)
    Waiting for Configuration Manager Update changes for maximum 3600 seconds… SMS_HIERARCHY_MANAGER 4/24/2019 4:03:12 PM 5816 (0x16B8)

    Get update pacakge 454B3508-4387-4106-9441-283495DEC3EC, \\SCCM01.Techno.com\EasySetupPayLoad\454B3508-4387-4106-9441-283495DEC3EC SMS_HIERARCHY_MANAGER 4/24/2019 4:26:57 PM 5816 (0x16B8)
    Creating hash for algorithm 32780 SMS_HIERARCHY_MANAGER 4/24/2019 4:26:57 PM 5816 (0x16B8)
    Waiting for Configuration Manager Client Upgrade changes for maximum 3600 seconds… SMS_HIERARCHY_MANAGER 4/24/2019 4:27:02 PM 8892 (0x22BC)

    WARNING : Thread shutdown signalled SMS_HIERARCHY_MANAGER 4/24/2019 4:28:01 PM 5816 (0x16B8)
    Failed to hash file, Win32 error = 4294967294 SMS_HIERARCHY_MANAGER 4/24/2019 4:28:03 PM 5816 (0x16B8)
    Error: Failed to calculate hash of folder ‘\\SCCM01.Techno.com\EasySetupPayLoad\454B3508-4387-4106-9441-283495DEC3EC’ with error 0xfffffffe SMS_HIERARCHY_MANAGER 4/24/2019 4:28:03 PM 5816 (0x16B8)
    Failed to calculate hash SMS_HIERARCHY_MANAGER 4/24/2019 4:28:03 PM 5816 (0x16B8)
    Successfully reported ConfigMgr update status (SiteCode=IN2, SubStageID=0xb0001, IsComplete=4, Progress=100, Applicable=1) SMS_HIERARCHY_MANAGER 4/24/2019 4:28:03 PM 5816 (0x16B8)
    C:\Program Files\Microsoft Configuration Manager\CMUStaging\ApplicabilityChecks\Applicability_1806Release.sql has hash value SHA256:F90AF1239599C62B00A58DD0F1C2EC9D8F968E29DA2E7710364E5DDCA8FC58D8 SMS_HIERARCHY_MANAGER 4/24/2019 4:28:03 PM 5816 (0x16B8)
    Configuration Manager Update (PackageGuid=F420D72A-4A0B-40B2-B4D8-275489CC32D0) is applicable SMS_HIERARCHY_MANAGER 4/24/2019 4:28:03 PM 5816 (0x16B8)

    Added user Techno\sccmadmin for site role SCCM01.Techno.com SMS_HIERARCHY_MANAGER 4/24/2019 4:36:00 PM 7868 (0x1EBC)
    This site is not using SQL failover cluster. SMS_HIERARCHY_MANAGER 4/24/2019 4:36:01 PM 7868 (0x1EBC)

    Path is not found. Skip import metadata file of language 00000c04 for CM update 454B3508-4387-4106-9441-283495DEC3EC SMS_HIERARCHY_MANAGER 4/24/2019 4:47:09 PM 8076 (0x1F8C)
    Path is not found. Skip import license file of language 00000c04 for CM update 454B3508-4387-4106-9441-283495DEC3EC SMS_HIERARCHY_MANAGER 4/24/2019 4:47:09 PM 8076 (0x1F8C)

    Below are some content from smsexec log files: (No Error found)
    ———————————————
    Generating state message: 6 for package 454b3508-4387-4106-9441-283495dec3ec

    EasySetupMaintenance – Redownload package: 454b3508-4387-4106-9441-283495dec3ec SMS_DMP_DOWNLOADER 4/22/2019 4:54:47 PM 1388 (0x056C)
    EasySetupDownloadSinglePackage downloading 454b3508-4387-4106-9441-283495dec3ec. SMS_DMP_DOWNLOADER 4/22/2019 4:54:47 PM 1388 (0x056C)
    Generating state message: 8 for package 454b3508-4387-4106-9441-283495dec3ec SMS_DMP_DOWNLOADER 4/22/2019 4:54:47 PM 1388 (0x056C)

    Content for 454b3508-4387-4106-9441-283495dec3ec does not exist locally. Download it from internet SMS_DMP_DOWNLOADER 4/22/2019 4:54:47 PM 1388 (0x056C)
    Write the package meta data to connector’s outbox SMS_DMP_DOWNLOADER 4/22/2019 4:54:47 PM 1388 (0x056C)
    The CMU file name is C:\Program Files\Microsoft Configuration Manager\inboxes\hman.box\ForwardingMsg\___CMU454b3508-4387-4106-9441-283495dec3ec.MCM SMS_DMP_DOWNLOADER 4/22/2019 4:54:47 PM 1388 (0x056C)
    HasIntuneSubscription: Site has no Intune subscription. SMS_DMP_DOWNLOADER 4/22/2019 4:54:47 PM 1388 (0x056C)
    outerxml is SMS_DMP_DOWNLOADER 4/22/2019 4:54:47 PM 1388 (0x056C)

    SMSEXEC log files:
    —————————
    SMS_EXECUTIVE is stopping… SMS_EXECUTIVE 4/24/2019 4:27:56 PM 6092 (0x17CC)
    SMS_AI_KB_MANAGER is stopping… SMS_EXECUTIVE 4/24/2019 4:27:57 PM 6092 (0x17CC)
    *** [08001][-2146893055][Microsoft][SQL Server Native Client 11.0]SSL Provider: The handle specified is invalid SMS_EXECUTIVE 4/24/2019 4:27:57 PM 6092 (0x17CC)
    *** [08001][-2146893055][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection SMS_EXECUTIVE 4/24/2019 4:27:57 PM 6092 (0x17CC)
    *** Failed to connect to the SQL Server, connection type: SMS ACCESS. SMS_EXECUTIVE 4/24/2019 4:27:57 PM 6092 (0x17CC)
    *** [08001][-2146893055][Microsoft][SQL Server Native Client 11.0]SSL Provider: The handle specified is invalid SMS_EXECUTIVE 4/24/2019 4:27:57 PM 6092 (0x17CC)
    *** [08001][-2146893055][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection SMS_EXECUTIVE 4/24/2019 4:27:57 PM 6092 (0x17CC)
    *** Failed to connect to the SQL Server, connection type: SMS ACCESS. SMS_EXECUTIVE 4/24/2019 4:27:57 PM 6092 (0x17CC)

    *** [08001][2][Microsoft][SQL Server Native Client 11.0]Named Pipes Provider: Could not open a connection to SQL Server [2]. SMS_EXECUTIVE 4/24/2019 4:31:54 PM 464 (0x01D0)
    *** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user ‘NT AUTHORITY\SYSTEM’. SMS_EXECUTIVE 4/24/2019 4:31:54 PM 464 (0x01D0)
    *** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database “CM_IN2” requested by the login. The login failed. SMS_EXECUTIVE 4/24/2019 4:31:54 PM 464 (0x01D0)
    *** [08001][2][Microsoft][SQL Server Native Client 11.0]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. SMS_EXECUTIVE 4/24/2019 4:31:54 PM 464 (0x01D0)
    *** Failed to connect to the SQL Server, connection type: SMS ACCESS. SMS_EXECUTIVE 4/24/2019 4:31:54 PM 464 (0x01D0)
    CSiteControlEx::GetCurrentSiteInfo: Failed to get SQL connection SMS_EXECUTIVE 4/24/2019 4:31:54 PM 464 (0x01D0)

    Let me know if anything else is needed. Just fyi, I have only one primary site & SQL Server 2014 Standard on same VM.

    • Let me understand the problem. The 1810 update got downloaded and no issues with that. Is that correct understanding? Prerequisite check related log entries will be available C:\ConfigMgrPrereq.log file. Have you already checked the same?

  11. Yes Anoop. Package for 1810 got downloaded under C:\Program Files\Microsoft Configuration Manager\CMUStaging already and same is available under C:\Program Files\Microsoft Configuration Manager\EasySetupPayload.

    While I was trying to upgrade 1810 from Console, I never seen any prerequisites warnings except SQL Native Client version warning. But I have just seen C:\ConfigMgrPrereq.log and found below log entries with red color.

     INFO: Prerequisite rule ‘SQL availability group configured for manual failover’ will run for easysetup upgrade.
     EQSCCMIN02.technologic.com; SQL availability group configured for manual failover; Passed

    But I guess this has nothing to do with my setup.

    Just FYI, when this upgrade for 1810 stuck in Prerequisites checks, I decided to download 1806 but now that option is also grayed out sir.

    It is for sure, package got downloaded.

  12. HI Anoop, I have just found something on ConfigMgrSetup.log file which is as below, but these logs are two days old. Just thought to share.

    NFO: Manifest Version: Configmgr Configuration Manager Setup 4/22/2019 5:04:32 PM 12052 (0x2F14)
    INFO: Manifest build Version: 201810 Configuration Manager Setup 4/22/2019 5:04:32 PM 12052 (0x2F14)
    INFO: Manifest full Version: 5.00.8740.1000 Configuration Manager Setup 4/22/2019 5:04:32 PM 12052 (0x2F14)

    CMUPreReqCheckListener::ReportPrereqStatus : [INFO] Saved prereq message[F162D439-F781-471B-9446-845A120A98EA][5][1] into Database. Configuration Manager Setup 4/22/2019 5:13:32 PM 11696 (0x2DB0)
    CMUPreReqCheckListener::ReportPrereqStatus : [INFO] Saved prereq message[360CD826-CA7A-4680-A1DC-7E7FE28B3A90][5][1] into Database. Configuration Manager Setup 4/22/2019 5:13:32 PM 11696 (0x2DB0)

    INFO: Registry key SOFTWARE\Microsoft\ServerManager is opened. Configuration Manager Setup 4/22/2019 5:13:32 PM 11696 (0x2DB0)
    INFO: Failed to open registry key SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\RebootPending on EQSCCMIN02.technologic.com. Error = 2 Configuration Manager Setup 4/22/2019 5:13:32 PM 11696 (0x2DB0)
    INFO: Failed to open registry key SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired on EQSCCMIN02.technologic.com. Error = 2 Configuration Manager Setup 4/22/2019 5:13:32 PM 11696 (0x2DB0)
    INFO: Registry key SYSTEM\CurrentControlSet\Control\Session Manager is opened.

  13. Hi Anoop,
    Finally after 1 month of exhausting reading, troubleshooting, I was able to in place upgrade my SCCM CB to 1810.
    I used UpdateResetTool twice and rebooted server and then I could see Install option enabled. Though it got stuck during installation, I had rebooted server again.

    After opening console I could see Configuration Manager 1810 as Installed.

    Thank you Anoop.

  14. Hi Anoop,

    Have you seen any issues with applications getting stuck at downloading on 1810? I am noticing this on Applications that was setup before and new applications that I am deploying. As it is only stuck on a handful of computers, and not the same ones every time. Most noticeable on the newly imaged machines, for post installation after imaging.

    Any suggestion would be appreciated.

    Thanks.

    • Hello David – Are you using application catalog or software center ? Are those apps required or available deployments? User based or device based deployments? Why am I asking these questions? Users based available deployments have some known issues with software center

      • Hi Anoop,

        Thanks for the quick respond, some are user base and some are device based deployment. Some are required and some are available. I am using software center, and seeing it get stuck in Installation status.

        Thanks,
        David

  15. Hi Anoop,
    I am facing issue of inplace upgrade win 10 1903. My sccm version 1810. There is no issue in win 10 1803 & 1809.
    Error code is 0x80070002.
    Can you help me.
    As per google I have already set network access account but same issue.

    • Can you please provide more details about the error? Are you getting this while you run in place upgrade (IPU) task sequence? If so, can you share the portion of Amat’s.log ? Or You get this when you upgrade with windows 10 servicing?

      • Hi ,
        We have using CB1810 version with latest KB in our organization, some times we are facing patch deployment status not reflect properly in console.. can you give suggestion

  16. Hi ,
    We have using CB1810 version with latest KB in our organization, some times we are facing patch deployment status not reflect properly in console.. can you give suggestion

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.