software update management
68 TopicsUpdate 2207 for Microsoft Endpoint Configuration Manager current branch is now available
We are delighted to announce Microsoft Endpoint Configuration Manager release 2207. This release includes several feature enhancements and updates, including key enhancements to manage security settings, hybrid workspace, and simplifying the admin persona.192KViews3likes4CommentsManaging Patch Tuesday with Configuration Manager in a remote work world
This article is designed to help you successfully deliver patches to your managed PCs that are no longer on-premises and connecting via VPN using home broadband networks. We will take you through a decision tree of options available to your organization when it comes to managing your upcoming patch deployments as we approach the April 2020 security update.150KViews19likes17CommentsExtended Security Updates and Configuration Manager
This article describes software update management and OS deployment using Configuration Manager for clients covered under the ESU program. For those clients covered under the ESU program, the latest released version of Configuration Manager current branch can be used to deploy and install any Windows security updates released under the program.100KViews10likes0CommentsUnified update platform (UUP) FAQ's
After a month of UUP update release, sharing best practices based on our field and feedback through multiple channels. 1. Will UUP patch work for CB 2111 and below? Our pre-req is Configuration Manager Version 2203 and above as per our release documents. For Configuration Manager Version 2111 (Lesser than this are unsupported now) to patch UUP updates for windows 11 22H2 seamlessly, enable delta download setting using client settings in ConfigMgr. When this option is set, delta download is used for all Windows update installation files, not just express installation files. 2. Please be sure to select the appropriate update classifications in your ADRs. If you have ADRs configured to auto-approve Security Updates, be sure to specify the “Security Updates” classification in your ADR settings. If you would like to take advantage of all the great features of UUP and utilize UUP feature updates to upgrade endpoint clients to Windows 11 22H2, be sure to include the “Upgrades” classification in your ADRs. This will ensure that as endpoint clients go through the OS upgrade they will receive the latest security updates as part of the upgrade and will only need to reboot once. If you do not want to utilize UUP feature updates to upgrade endpoint clients right now, you will want to exclude the “Upgrades” classification from your ADRs. Note: The feature updates will be released every month but there will be sharing of content for the old files and the new content should be only a few hundred MBs between the month releases. See Question 9 for more details on deduplication. 3. ConfigMgr + Adaptiva integrated solutions Adaptiva has released a patch for its customers to support the UUP. The public documentation can be found here: https://adaptiva.com/blog/using-unified-update-platform-with-adaptiva-onesite. Note that Adaptiva has asked customers not to enable delta download from the client settings and this is our recommendation from ConfigMgr 2203+ onwards only (which is our recommended version as well but as mentioned before for UUP to work with ConfigMgr 2111 there is a requirement to enable delta download from client settings.) 4. ConfigMgr console on Windows Server 2012 R2 cannot download the UUP Quality update fails to verify cert signature PatchDownloader.log Verifying file trust C:\Users\admin\AppData\Local\Temp\2\CAB291B.tmp.wim Software Updates Patch Downloader Authentication of file C:\Users\admin\AppData\Local\Temp\2\CAB291B.tmp.wim failed, error 0x800b0004 Software Updates Patch Downloader Attempting to delete 0 byte tmp files from previous downloads Software Updates Patch Downloader ERROR: DownloadUpdateContent() failed with hr=0x80073633 Software Updates Patch Downloader Workaround: Patch the Windows Server 2012 R2 with 2023 4B (April CU) which then fixes this issue. 5. ConfigMgr Patchdownloader component may fail to verify (*.psf files) if the UUP patches were synched before ConfigMgr 2111 version. The issue will persist even if ConfigMgr version is upgraded to ConfigMgr 2111+ if the updates were synched before ConfigMgr was on a lesser version than version 2111. Sample error in PatchDownloader.log Verifying file trust C:\WINDOWS\TEMP\CAB6062.tmp.psf Software Updates Patch Downloader Authentication of file C:\WINDOWS\TEMP\CAB6062.tmp.psf failed, error 0x800b0004 Software Updates Patch Downloader Attempting to delete 0 byte tmp files from previous downloads Software Updates Patch Downloader ERROR: DownloadUpdateContent() failed with hr=0x80073633 Software Updates Patch Downloader The below SQL query will help you identify the issue. -- Sample check for 2023-04 Cumulative Update for Windows 11 Version 22H2 for x64-based Systems (KB5025239). -- Replace the unique update id below if you are searching for a different UUP update IF EXISTS( select all SMS_CIContentFiles.CI_UniqueID,SMS_CIContentFiles.Content_ID,SMS_CIContentFiles.FileName,SMS_CIContentFiles.FileSize, SMS_CIContentFiles.IsSigned,SMS_CIContentFiles.SecuredTypeID,SMS_CIContentFiles.SourceURL from vSMS_CIContentFiles AS SMS_CIContentFiles WHERE SMS_CIContentFiles.CI_UniqueID='3157dbaf-04f5-49fc-baef-300bbd6d121a' AND FileName like '%.psf' and isSigned= 1 ) PRINT 'UUP Updates likely synched before upgrading to 2111. This will need correction, Please call Microsoft support to correct this.' ELSE PRINT 'You are not likely affected by the UUP PSF update signing issue' If you get the output of the above query as 'UUP Updates likely synched before upgrading to 2111. This will need correction, please call Microsoft support to correct this.' then likely you are affected and open a support case with Microsoft to correct the issue. 6. UUP updates installed as a part of OSD TS in "Install Software Updates" step (Fixed 2309 or later) There is a known issue that is currently investigated. The issue is the Delta Download component of CCMEXEC not starting on time and the updates timeout on the first scan, later scans are not impacted. Workaround: Add a restart step in between two install software updates steps. This will allow UUP updates to be successfully downloaded and installed in the second attempt. Resolution: Upgrade to CB 2309 and upgrade the client. This issue is addressed. 7. Does offline servicing work with UUP updates? No. Offline servicing images with UUP QU updates from the ConfigMgr console is not supported. 8. Are Delivery Optimization (DO) and Delta Download (DD) components different ? What is ConfigMgr dependency on DO? Delivery Optimization is a Windows technology to deliver content in a smart way reducing internet bandwidth owned by the Windows team and Delta Download is a component which is an http listener for requests owned by the ConfigMgr team. Delivery Optimization is a peer-to-peer distribution technology available in Windows 11 and Windows 10 that allows devices to share content, such as updates, that the devices have downloaded from Microsoft over the internet. DO is a part of the Windows OS. Delta Download is a http listener and is a component of ConfigMgr. ConfigMgr requires the DO client as it invokes the Delta download listener to download the content (as we configure the alternate content location URL in WUA policy to point to Delta Download Listener URL). The Invocation flow is WUA (Windows Update Agent) -> DO (Delivery Optimization) -> DD (Delta Download). Hence even if we don't enable DO, ConfigMgr would automatically enable DO by setting these two policies. This is visible in the UpdateDOGPO.log SetDOGPOSettings: Set Windows DO group policy to DOGroupId = DeliveryMode = group Customers should not create any GPO settings to disable these policies OR edit the registry to disable the DOSVC service or from services console. 9. Update Supersedence changing to 6 months default for new installs. How does update supersedence affect UUP scenarios? Refer the blog for the announcement details for this change. The default for expiring updates which are superseded will only change for the new installations and the existing ones will not be altered from whatever the current setting is. 10. Does ConfigMgr have deduplication of files at source and distribution points? Deduplication at the source in ConfigMgr : When PatchDownloader component downloads a file it checks if the file exists in the same share and creates a hard link for the already existing file instead of re-downloading it. Scenario 1 If the files/folders for previous UUP update source package are on the same volume but different share name, customers don't go into creating hard link path at all. Scenario 2(a) If the Package path has a common share \\machine\share but different folders inside it (which is the normal case) like \\machine\share\jan and \\machine\share\feb we go to the hard link and create the hard link for the file with the Patchdownloader.log entry Content already downloaded. Created link for ContentID Scenario 2(b) Same scenario as 2(a) but the PatchDownloader here finds the same file present in a different share first apart from being present on the same share. Here the PatchDownloader doesn't go deep and check if the file is also present on the same share and fails to create the hard link. But here it doesn't download from internet again but copies the file from the other share to this share. Log entries fail to create hard link with error 17 (which is it thinks these are different drives). Could not create hard link: \\MachineNetbios\UpdatesPackage\2302_Win11_21H2_UUP\b1e9d019-7dec-4eee-b7e4-9e8eae99d89b.1\19222DDC6156FBE5570C3A6DDF69759662F93AEE_FeatureOnDemand.wim -> \\ MachineNetbios\22-11-UUPWin11\bcb528ff-85c2-4372-8b91-20bd0c7fa1e4\19222DDC6156FBE5570C3A6DDF69759662F93AEE_FeatureOnDemand.wim. LastErr=17 Summary It is recommended to have a single share for all the UUP monthly packages \\machine\UUP and then creating folders inside it for each months. for eg.. \\machine\share\jan and \\machine\share\feb . In this case ConfigMgr will create hard links instead of downloading the actual files again. Note If you actually check the properties of the folder it will still show the size of the actual file and not hard link. Use DU.exe from sysinternals suite to find the actual size of a folder. E:\UpdatesPackage\2302_Win11_21H2_UUP>E:\DU\du.exe . DU v1.62 - Directory disk usage reporter Copyright (C) 2005-2018 Mark Russinovich Sysinternals - www.sysinternals.com Files: 14 Directories: 2 Size: 9,675,198,236 bytes Size on disk: 9,675,227,136 bytes Note To find all the hard link references to a file use the fsutil command. fsutil harlink list <full_file_path> 11. Why does ConfigMgr UUP On-Prem download a 3-5GB wim when I want to install a very small FOD/LP package? This is an issue with the size attribute on the file as we don't download the full file for FOD/LP but only the needed byte ranges. Since we download the needed byte ranges only, the size that gets displayed for the file is the cumulative size of the file till that range. Meaning if the small FOD package is around 3035627519 of the byte range in the file, we will display the size of the file as around 2.82 GB. While in actuality we only downloaded the file ranges between 3034578944-3035627519 for the 1 MB FOD package. To confirm the actual size of the file on disk you can check the properties of the file and verify the "Size on disk". 12. Deduplication at the distribution points in ConfigMgr : Distribution Points in ConfigMgr are already designed to have a SIS (Single instance storage) in the form of Content Library. So we store any file only once no matter how many packages it is present in. More on ConfigMgr Content Library design here . For more details ref the actual windows blog and Configuration blog. Thank you, The Configuration Manager team85KViews3likes37CommentsUpdate 1910 for Microsoft Endpoint Configuration Manager current branch is now available
Update 1910 for Microsoft Endpoint Configuration Manager current branch is now available. As Brad Anderson announced at Ignite, Configuration Manager is now part of Microsoft Endpoint Manager. Microsoft Endpoint Manager is an integrated solution for managing all of your devices. Microsoft brings together Configuration Manager and Intune, without a complex migration, and with simplified licensing.44KViews9likes3CommentsWUAHandler.log error OnSearchComplete - Failed to end search job. Error = 0x80240439
80% of the systems failing while scanning 20% works WUAHandler.log Its a WSUS Update Source type ({7EE15F10-3F99-44F6-A92F-F5AAAE34C0E7}), adding it. WUAHandler 7/28/2020 2:00:00 PM 11976 (0x2EC8) Enabling WUA Managed server policy to use server: http://myserver.domain.local:8530 WUAHandler 7/28/2020 2:00:00 PM 11976 (0x2EC8) Waiting for 2 mins for Group Policy to notify of WUA policy change... WUAHandler 7/28/2020 2:00:01 PM 11976 (0x2EC8) Waiting for 30 secs for policy to take effect on WU Agent. WUAHandler 7/28/2020 2:00:04 PM 11976 (0x2EC8) Added Update Source ({7EE15F10-3F99-44F6-A92F-F5AAAE34C0E7}) of content type: 2 WUAHandler 7/28/2020 2:00:34 PM 11976 (0x2EC8) Scan results will include all superseded updates. WUAHandler 7/28/2020 2:00:34 PM 11976 (0x2EC8) Search Criteria is (DeploymentAction=* AND Type='Software') OR (DeploymentAction=* AND Type='Driver') WUAHandler 7/28/2020 2:00:34 PM 11976 (0x2EC8) Async searching of updates using WUAgent started. WUAHandler 7/28/2020 2:00:40 PM 11976 (0x2EC8) Async searching completed. WUAHandler 7/28/2020 2:00:41 PM 16952 (0x4238) OnSearchComplete - Failed to end search job. Error = 0x80240439. WUAHandler 7/28/2020 2:00:41 PM 11976 (0x2EC8) Scan failed with error = 0x80240439. WUAHandler 7/28/2020 2:00:41 PM 11976 (0x2EC8) WindowsUpdate.log 2020-07-29 17:15:26:958 992 678 PT +++++++++++ PT: Synchronizing server updates +++++++++++ 2020-07-29 17:15:26:958 992 678 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = HTTP://myserver.domain.local:8530/ClientWebService/client.asmx 2020-07-29 17:15:26:958 992 678 IdleTmr WU operation (CAgentProtocolTalker::GetConfig_WithRecovery) started; operation # 6; does use network; is at background priority 2020-07-29 17:15:27:021 992 678 WS WARNING: Nws Failure: errorCode=0x803d0000 2020-07-29 17:15:27:021 992 678 WS WARNING: Original error code: 0x80072f78 2020-07-29 17:15:27:021 992 678 WS WARNING: There was an error communicating with the endpoint at 'HTTP://myserver.domain.local:8530/ClientWebService/client.asmx'. 2020-07-29 17:15:27:021 992 678 WS WARNING: There was an error receiving the HTTP reply. 2020-07-29 17:15:27:021 992 678 WS WARNING: The input data was not in the expected format or did not have the expected value. 2020-07-29 17:15:27:021 992 678 WS WARNING: The server returned an invalid or unrecognized response 2020-07-29 17:15:27:021 992 678 WS WARNING: MapToSusHResult mapped Nws error 0x803d0000 to 0x80240439 2020-07-29 17:15:27:021 992 678 WS WARNING: Web service call failed with hr = 80240439. 2020-07-29 17:15:27:021 992 678 WS WARNING: Current service auth scheme='None'. 2020-07-29 17:15:27:021 992 678 WS WARNING: Proxy List used: '(null)', Bypass List used: '(null)', Last Proxy used: '(null)', Last auth Schemes used: 'None'. 2020-07-29 17:15:27:021 992 678 WS FATAL: OnCallFailure failed with hr=0X80240439 2020-07-29 17:15:27:021 992 678 IdleTmr WU operation (CAgentProtocolTalker::GetConfig_WithRecovery, operation # 6) stopped; does use network; is at background priority 2020-07-29 17:15:27:021 992 678 EP Got WSUS Client/Server URL: "HTTP://myserver.domain.local:8530/ClientWebService/client.asmx" 2020-07-29 17:15:27:021 992 678 PT WARNING: PTError: 0x80240439 2020-07-29 17:15:27:021 992 678 PT WARNING: GetConfig_WithRecovery failed: 0x80240439 2020-07-29 17:15:27:021 992 678 PT WARNING: RefreshConfig failed: 0x80240439 2020-07-29 17:15:27:021 992 678 PT WARNING: RefreshPTState failed: 0x80240439 2020-07-29 17:15:27:021 992 678 PT + SyncUpdates round trips: 0 2020-07-29 17:15:27:021 992 678 PT WARNING: Sync of Updates: 0x80240439 2020-07-29 17:15:27:021 992 678 PT WARNING: SyncServerUpdatesInternal failed: 0x80240439 2020-07-29 17:15:27:021 992 678 Agent * WARNING: Failed to synchronize, error = 0x80240439 2020-07-29 17:15:27:021 992 678 Agent * WARNING: Exit code = 0x80240439 2020-07-29 17:15:27:021 992 678 Agent ********* 2020-07-29 17:15:27:021 992 678 Agent ** END ** Agent: Finding updates [CallerId = CcmExec Id = 1] 2020-07-29 17:15:27:021 992 678 Agent ************* 2020-07-29 17:15:27:021 992 678 Agent WARNING: WU client failed Searching for update with error 0x80240439 2020-07-29 17:15:27:021 992 678 IdleTmr WU operation (CSearchCall::Init ID 1, operation # 4) stopped; does use network; is not at background priority 2020-07-29 17:15:27:021 992 678 IdleTmr Decremented idle timer priority operation counter to 0 2020-07-29 17:15:27:036 3828 274 COMAPI >>-- RESUMED -- COMAPI: Search [ClientId = CcmExec] 2020-07-29 17:15:27:036 3828 274 COMAPI - Updates found = 0 2020-07-29 17:15:27:036 3828 274 COMAPI - WARNING: Exit code = 0x00000000, Result code = 0x80240439 2020-07-29 17:15:27:036 3828 274 COMAPI --------- 2020-07-29 17:15:27:036 3828 274 COMAPI -- END -- COMAPI: Search [ClientId = CcmExec] 2020-07-29 17:15:27:036 3828 274 COMAPI ------------- 2020-07-29 17:15:27:036 3828 274 COMAPI WARNING: Operation failed due to earlier error, hr=80240439 2020-07-29 17:15:27:036 3828 274 COMAPI FATAL: Unable to complete asynchronous search. (hr=80240439) 2020-07-29 17:24:28:050 4468 1578 Misc =========== Logging initialized (build: 7.9.9600.18970, tz: +0400) =========== 2020-07-29 17:24:28:050 4468 1578 Misc = Process: C:\Windows\CCM\CcmExec.exe 2020-07-29 17:24:28:050 4468 1578 Misc = Module: C:\Windows\System32\wuapi.dll 2020-07-29 17:24:28:050 4468 1578 COMAPI ------------- 2020-07-29 17:24:28:050 4468 1578 COMAPI -- START -- COMAPI: Init Search [ClientId = CcmExec] 2020-07-29 17:24:28:050 4468 1578 COMAPI --------- 2020-07-29 17:24:28:050 4468 1578 COMAPI ------------- 2020-07-29 17:24:28:050 4468 1578 COMAPI -- START -- COMAPI: Search [ClientId = CcmExec] 2020-07-29 17:24:28:050 4468 1578 COMAPI --------- 2020-07-29 17:15:32:070 992 1250 Report REPORT EVENT: {575F43AD-B11F-4B2D-97DB-C33CE55EEDC9} 2020-07-29 17:15:27:021+0400 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80240439 CcmExec Failure Software Synchronization Windows Update Client failed to detect with error 0x80240439. 2020-07-29 17:15:32:070 992 1250 Report WARNING: Failed to get ProtocolVersion: 8024043d 2020-07-29 17:15:32:195 992 1250 Report CWERReporter::HandleEvents - WER report upload completed with WER status 0x8 (hr=0) 2020-07-29 17:15:32:195 992 1250 Report WER Report sent: 7.9.9600.19670 0x80240439(0) 00000000-0000-0000-0000-000000000000 Scan 0 1 CcmExec {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} 0 2020-07-29 17:15:32:195 992 1250 Report CWERReporter finished handling 1 events. (00000000) 2020-07-29 17:24:28:050 992 1a58 IdleTmr WU operation (CSearchCall::Init ID 2) started; operation # 23; does use network; is not at background priority 2020-07-29 17:24:28:050 992 1a58 IdleTmr Incremented idle timer priority operation counter to 1 2020-07-29 17:24:28:050 992 1a58 Agent *** START *** Queueing Finding updates [CallerId = CcmExec Id = 2] 2020-07-29 17:24:28:050 4468 1578 COMAPI <<-- SUBMITTED -- COMAPI: Search [ClientId = CcmExec] 2020-07-29 17:24:28:050 992 13b4 Agent *** END *** Queueing Finding updates [CallerId = CcmExec Id = 2] 2020-07-29 17:24:28:050 992 13b4 Agent ************* 2020-07-29 17:24:28:050 992 13b4 Agent ** START ** Agent: Finding updates [CallerId = CcmExec Id = 2] 2020-07-29 17:24:28:050 992 13b4 Agent ********* 2020-07-29 17:24:28:050 992 13b4 Agent * Include potentially superseded updates 2020-07-29 17:24:28:050 992 13b4 Agent * Online = Yes; Ignore download priority = Yes 2020-07-29 17:24:28:050 992 13b4 Agent * Criteria = "(DeploymentAction=* AND Type='Software') OR (DeploymentAction=* AND Type='Driver')" 2020-07-29 17:24:28:050 992 13b4 Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed 2020-07-29 17:24:28:050 992 13b4 Agent * Search Scope = {Machine} 2020-07-29 17:24:28:050 992 13b4 Agent * Caller SID for Applicability: S-1-5-18 2020-07-29 17:24:28:050 992 13b4 Agent * RegisterService is set 2020-07-29 17:24:28:081 992 13b4 EP Got WSUS Client/Server URL: "HTTP://myserver.domain.local:8530/ClientWebService/client.asmx" 2020-07-29 17:24:28:315 992 13b4 PT +++++++++++ PT: Synchronizing server updates +++++++++++ 2020-07-29 17:24:28:315 992 13b4 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = HTTP://myserver.domain.local:8530/ClientWebService/client.asmx 2020-07-29 17:24:28:315 992 13b4 IdleTmr WU operation (CAgentProtocolTalker::GetConfig_WithRecovery) started; operation # 24; does use network; is at background priority 2020-07-29 17:24:28:331 992 13b4 WS WARNING: Nws Failure: errorCode=0x803d0000 2020-07-29 17:24:28:331 992 13b4 WS WARNING: Original error code: 0x80072f78 2020-07-29 17:24:28:331 992 13b4 WS WARNING: There was an error communicating with the endpoint at 'HTTP://myserver.domain.local:8530/ClientWebService/client.asmx'. 2020-07-29 17:24:28:331 992 13b4 WS WARNING: There was an error receiving the HTTP reply. 2020-07-29 17:24:28:331 992 13b4 WS WARNING: The input data was not in the expected format or did not have the expected value. 2020-07-29 17:24:28:331 992 13b4 WS WARNING: The server returned an invalid or unrecognized response 2020-07-29 17:24:28:331 992 13b4 WS WARNING: MapToSusHResult mapped Nws error 0x803d0000 to 0x80240439 2020-07-29 17:24:28:331 992 13b4 WS WARNING: Web service call failed with hr = 80240439. 2020-07-29 17:24:28:331 992 13b4 WS WARNING: Current service auth scheme='None'. 2020-07-29 17:24:28:331 992 13b4 WS WARNING: Proxy List used: '(null)', Bypass List used: '(null)', Last Proxy used: '(null)', Last auth Schemes used: 'None'. 2020-07-29 17:24:28:331 992 13b4 WS FATAL: OnCallFailure failed with hr=0X80240439 2020-07-29 17:24:28:331 992 13b4 IdleTmr WU operation (CAgentProtocolTalker::GetConfig_WithRecovery, operation # 24) stopped; does use network; is at background priority 2020-07-29 17:24:28:331 992 13b4 EP Got WSUS Client/Server URL: "HTTP://myserver.domain.local:8530/ClientWebService/client.asmx" 2020-07-29 17:24:28:331 992 13b4 PT WARNING: PTError: 0x80240439 2020-07-29 17:24:28:331 992 13b4 PT WARNING: GetConfig_WithRecovery failed: 0x80240439 2020-07-29 17:24:28:331 992 13b4 PT WARNING: RefreshConfig failed: 0x80240439 2020-07-29 17:24:28:331 992 13b4 PT WARNING: RefreshPTState failed: 0x80240439 2020-07-29 17:24:28:331 992 13b4 PT + SyncUpdates round trips: 0 2020-07-29 17:24:28:331 992 13b4 PT WARNING: Sync of Updates: 0x80240439 2020-07-29 17:24:28:331 992 13b4 PT WARNING: SyncServerUpdatesInternal failed: 0x80240439 2020-07-29 17:24:28:331 992 13b4 Agent * WARNING: Failed to synchronize, error = 0x80240439 2020-07-29 17:24:28:331 992 13b4 Agent * WARNING: Exit code = 0x80240439 2020-07-29 17:24:28:331 992 13b4 Agent ********* 2020-07-29 17:24:28:331 992 13b4 Agent ** END ** Agent: Finding updates [CallerId = CcmExec Id = 2] 2020-07-29 17:24:28:331 992 13b4 Agent ************* 2020-07-29 17:24:28:331 992 13b4 Agent WARNING: WU client failed Searching for update with error 0x80240439 2020-07-29 17:24:28:331 992 13b4 IdleTmr WU operation (CSearchCall::Init ID 2, operation # 23) stopped; does use network; is not at background priority 2020-07-29 17:24:28:331 992 13b4 IdleTmr Decremented idle timer priority operation counter to 0 2020-07-29 17:24:28:331 4468 1578 COMAPI >>-- RESUMED -- COMAPI: Search [ClientId = CcmExec] 2020-07-29 17:24:28:347 4468 1578 COMAPI - Updates found = 0 2020-07-29 17:24:28:347 4468 1578 COMAPI - WARNING: Exit code = 0x00000000, Result code = 0x80240439 2020-07-29 17:24:28:347 4468 1578 COMAPI --------- 2020-07-29 17:24:28:347 4468 1578 COMAPI -- END -- COMAPI: Search [ClientId = CcmExec] 2020-07-29 17:24:28:347 4468 1578 COMAPI ------------- 2020-07-29 17:24:28:347 4468 1578 COMAPI WARNING: Operation failed due to earlier error, hr=80240439 2020-07-29 17:24:28:347 4468 1578 COMAPI FATAL: Unable to complete asynchronous search. (hr=80240439) 2020-07-29 17:24:33:331 992 1250 Report REPORT EVENT: {520D7BB5-B7B3-4C9E-96F2-877743C67D01} 2020-07-29 17:24:28:331+0400 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80240439 CcmExec Failure Software Synchronization Windows Update Client failed to detect with error 0x80240439. 2020-07-29 17:24:33:331 992 1250 Report WARNING: Failed to get ProtocolVersion: 8024043d 2020-07-29 17:24:33:425 992 1250 Report CWERReporter::HandleEvents - WER report upload completed with WER status 0x8 (hr=0) 2020-07-29 17:24:33:425 992 1250 Report WER Report sent: 7.9.9600.19670 0x80240439(0) 00000000-0000-0000-0000-000000000000 Scan 0 1 CcmExec {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} 0 2020-07-29 17:24:33:425 992 1250 Report CWERReporter finished handling 1 events. (00000000) 2020-07-29 17:44:21:208 992 88c AU Earliest future timer found: 2020-07-29 17:44:21:208 992 88c AU Timer: CF1ABEC6-7887-4964-BB93-B2E21B31CEC1, Expires 2020-07-29 22:23:34, not idle-only, not network-only 2020-07-29 17:44:22:208 992 14bc AU ########### AU: Uninitializing Automatic Updates ########### 2020-07-29 17:44:22:239 992 14bc WuTask Uninit WU Task Manager 2020-07-29 17:44:22:302 992 14bc AU Earliest future timer found: 2020-07-29 17:44:22:302 992 14bc AU Timer: CF1ABEC6-7887-4964-BB93-B2E21B31CEC1, Expires 2020-07-29 22:23:34, not idle-only, not network-only 2020-07-29 17:44:22:333 992 14bc AU Earliest future timer found: 2020-07-29 17:44:22:333 992 14bc AU Timer: CF1ABEC6-7887-4964-BB93-B2E21B31CEC1, Expires 2020-07-29 22:23:34, not idle-only, not network-only 2020-07-29 17:44:22:395 992 14bc Service ********* 2020-07-29 17:44:22:395 992 14bc Service ** END ** Service: Service exit [Exit code = 0x240001] 2020-07-29 17:44:22:395 992 14bc Service ************* 2020-07-29 17:44:24:146 992 17a4 Misc =========== Logging initialized (build: 7.9.9600.19670, tz: +0400) =========== 2020-07-29 17:44:24:146 992 17a4 Misc = Process: C:\Windows\system32\svchost.exe 2020-07-29 17:44:24:146 992 17a4 Misc = Module: c:\windows\system32\wuaueng.dll 2020-07-29 17:44:24:146 992 17a4 Service ************* 2020-07-29 17:44:24:146 992 17a4 Service ** START ** Service: Service startup 2020-07-29 17:44:24:146 992 17a4 Service ********* 2020-07-29 17:44:24:146 992 17a4 IdleTmr Non-AoAc machine. Aoac operations will be ignored. 2020-07-29 17:44:24:146 992 17a4 Agent * WU client version 7.9.9600.19670 2020-07-29 17:44:24:146 992 17a4 Agent WARNING: SleepStudyTracker: Machine is non-AOAC. Sleep study tracker disabled. 2020-07-29 17:44:24:146 992 17a4 Agent * Base directory: C:\Windows\SoftwareDistribution 2020-07-29 17:44:24:146 992 17a4 Agent * Access type: No proxy 2020-07-29 17:44:24:146 992 17a4 Service UpdateNetworkState Ipv6, cNetworkInterfaces = 0. 2020-07-29 17:44:24:146 992 17a4 Service UpdateNetworkState Ipv4, cNetworkInterfaces = 1. 2020-07-29 17:44:24:146 992 17a4 Agent * Network state: Connected 2020-07-29 17:44:24:162 992 17a4 Service UpdateNetworkState Ipv6, cNetworkInterfaces = 0. 2020-07-29 17:44:24:162 992 17a4 Service UpdateNetworkState Ipv4, cNetworkInterfaces = 1. 2020-07-29 17:44:24:178 992 17a4 Agent *********** Agent: Initializing global settings cache *********** 2020-07-29 17:44:24:178 992 17a4 Agent * Endpoint Provider: 00000000-0000-0000-0000-000000000000 2020-07-29 17:44:24:178 992 17a4 Agent * WSUS server: HTTP://myserver.domain.local:8530 2020-07-29 17:44:24:178 992 17a4 Agent * WSUS status server: HTTP://myserver.domain.local:8530 2020-07-29 17:44:24:178 992 17a4 Agent * Target group: (Unassigned Computers) 2020-07-29 17:44:24:178 992 17a4 Agent * Windows Update access disabled: No 2020-07-29 17:44:24:178 992 17a4 Misc WARNING: Network Cost is assumed to be not supported as something failed with trying to get handles to wcmapi.dll 2020-07-29 17:44:24:193 992 17a4 WuTask WuTaskManager delay initialize completed successfully.. 2020-07-29 17:44:24:193 992 17a4 AU Timer: CF1ABEC6-7887-4964-BB93-B2E21B31CEC1, Expires 2020-07-29 22:23:34, not idle-only, not network-only 2020-07-29 17:44:24:193 992 17a4 AU Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2020-07-29 22:23:34, not idle-only, not network-only 2020-07-29 17:44:24:209 992 17a4 Report CWERReporter::Init succeeded 2020-07-29 17:44:24:209 992 17a4 Agent *********** Agent: Initializing Windows Update Agent *********** 2020-07-29 17:44:24:209 992 17a4 DnldMgr Download manager restoring 0 downloads 2020-07-29 17:44:24:209 992 17a4 AU ########### AU: Initializing Automatic Updates ########### 2020-07-29 17:44:24:209 992 17a4 AU AIR Mode is disabled 2020-07-29 17:44:24:209 992 17a4 AU # AU disabled through Policy 2020-07-29 17:44:24:209 992 17a4 AU # Will interact with non-admins (Non-admins are elevated (User preference)) 2020-07-29 17:44:24:209 992 17a4 AU WARNING: Failed to get Wu Exemption info from NLM, assuming not exempt, error = 0x80240037 2020-07-29 17:44:24:209 992 17a4 AU AU finished delayed initialization 2020-07-29 17:44:24:224 992 1a7c DnldMgr Asking handlers to reconcile their sandboxes Michiel Overweel36KViews0likes4CommentsThird-Party Updates and Windows Update for Business
While using Windows Updates for Business (WUfB) is not for everyone, its simplicity and familiar end-user experience make it quite attractive to many organizations. One thing that WUfB does not provide today, though, is updates for third-party products. For that, you need to continue to use an on-premises solution like Microsoft Endpoint Manager Configuration Manager to complement WUfB.34KViews5likes13CommentsUpdate 2107 for Microsoft Endpoint Configuration Manager current branch is now available
Update 2107 for Microsoft Endpoint Configuration Manager current branch is now available. Starting in this release, you can enable an application deployment to support implicit uninstall. If a device is in a collection, the application installs. Then when you remove the device from the collection, the application uninstalls.33KViews4likes7CommentsUpdate 2111 for Microsoft Endpoint Configuration Manager current branch is now available
Update 2111 for Microsoft Endpoint Configuration Manager current branch is now available. We are excited to announce that two popular pre-release features, orchestration groups and application groups are now full features in this release.32KViews3likes8CommentsUpdate 2103 for Microsoft Endpoint Configuration Manager current branch is now available
Update 2103 for Microsoft Endpoint Configuration Manager current branch is now available. You can now upgrade a client's Windows OS by using a feature update deployed with a task sequence. This integration combines the simplicity of Windows servicing with the flexibility of task sequences.32KViews1like0Comments