Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

NEW SCCM Clients not reporting back to the SCCM Server after enabling Third Party updates

  • Thread starter Thread starter Jav2893
  • Start date Start date
  • Replies Replies 0
  • Views Views 5K

Jav2893

New Member
Messages
3
Reaction score
1
Points
1
Hi,
I was wondering if someone can shed some light, one week ago after adding the Adobe catalog and enabling third party software updates, allowing ECM server to manage the SSL certificates all my clients are failing to report. I did a test deploy to one computer and the deploy is at 0%.
When I opened the Settings --> Updates & Security --> Windows Updates section and click on Check for updates I received the following error.
Error Encountered: We couldn't connect to the update service. We'll try again later, or you can check now. If it still doesn't work, make sure you're connected to the Internet.
Windows update log shows this error constantly:
WS error: There was an error communicating with the endpoint at 'https://server:8531/SimpleAuthWebService/SimpleAuth.asmx'.
2022/10/26 11:13:49.3647133 28504 22632 ComApi *FAILED* [80246007] ISusInternal:: IsCommitRequired
WUAHandler.log shows this entries.
OnSearchComplete - Failed to end search job. Error = 0x80240440. 10/25/2022 9:39:42 PM 25488 (0x6390)
Scan failed with error = 0x80240440. 10/25/2022 9:39:42 PM 25488 (0x6390)
ccmnotificationagent.log:
Failed to find a access point for BGB client. 8000000a 10/26/2022 8:57:28 AM 14060 (0x36EC)
locationservices.log:
Domain joined client is in Unknown location 10/26/2022 7:57:27 AM 14060 (0x36EC)
Failed in WinHttpSendRequest API, ErrorCode = 0x2ee7 10/26/2022 8:07:28 AM 14060 (0x36EC)
[CCMHTTP] ERROR: URL=http://server/SMS_MP/.sms_aut?SITESIGNCERT, Port=80, Options=1248, Code=12007, Text=ERROR_WINHTTP_NAME_NOT_RESOLVED 10/26/2022 8:47:28 AM 14060 (0x36EC)
ccmmessaging.log:
Access check failed against user 'xxxxxxx' 10/26/2022 12:16:35 PM 1724 (0x06BC)
certificatemaintenance.log:
Key 'ConfigMgrMigrationKey' not found, 0x80090016. 10/26/2022 11:46:35 AM 9048 (0x2358)
clientlocation.log:
Failed in WinHttpSendRequest API, ErrorCode = 0x2ee7 10/26/2022 5:46:31 AM 12164 (0x2F84)
FSPStatemessage.log:
[CCMHTTP] ERROR: URL=HTTP://Server/SMS_FSP/.sms_fsp, Port=80, Options=1248, Code=12007, Text=ERROR_WINHTTP_NAME_NOT_RESOLVED 10/26/2022 5:45:47 AM 12164 (0x2F84)
Failed to create HTTP connection 10/26/2022 5:45:35 AM 12164 (0x2F84)
scanagent.log:
ScanJob({F545C2DE-C88B-44FD-82BA-24F00A7E83A6}): CScanJobManager::OnScanComplete- failed at CScanJob::OnScanComplete with error=0x80240440 10/25/2022 9:39:42 PM 16764 (0x417C)
updatesdeployment.log:
GetUpdateInfo - failed to get targeted update, error = 0x87d00215. 10/26/2022 5:04:56 AM 5672 (0x1628)
Failed to notify policy modification to the assignment, error = 0x0 10/26/2022 5:04:56 AM 5672 (0x1628)
CCMVDIProvider.log
Missing property 'IsAssignedToUser' is mandatory to this set of mappings. Fail the execution. 10/26/2022 12:00:02 AM 5444 (0x1544)
Any though as to what it may have changed on the clients to failed to download updates and failed and the windows updates feature to fail scanning
 
Back
Top