Not reporting software update compliance

[AshrakTheWhite]

Hello

 

I have the following problem, many of my managed computers are reporting a status of passed/active unknown in monitoring for software updates.

 

WUAHandler log is clear of errors.

 

 

The updates are NOT showing up in software center for the machines in question.

 

SUP / WSUS adress is set by SCCM to the correct server.

 

 

Any idea on how to troubleshoot this further?

[AshrakTheWhite]

UpdatesDeployment.log has following

 

Assignment {BF626CE7-1F5E-4802-8857-0D16E7D98989} has total CI = 73 UpdatesDeploymentAgent 24.01.2014 11:03:53 2020 (0x07E4)

Assignment ({BF626CE7-1F5E-4802-8857-0D16E7D98989}) reconnected to the existing job ({9C1C5B81-6F4A-432B-97C1-C24461CDBBCD}) successfully. UpdatesDeploymentAgent 24.01.2014 11:03:53 2020 (0x07E4)

Assignment {CCEA778A-A80B-4C7B-A724-F0AE93CA77C3} has total CI = 73 UpdatesDeploymentAgent 24.01.2014 11:03:53 2020 (0x07E4)

Assignment ({CCEA778A-A80B-4C7B-A724-F0AE93CA77C3}) reconnected to the existing job ({4C6FD2A7-19C9-4269-B299-07822F2BD9F4}) successfully. UpdatesDeploymentAgent 24.01.2014 11:03:53 2020 (0x07E4)

Assignment {CF98ABA8-D808-41E2-BF42-D001CA6963B0} has total CI = 60 UpdatesDeploymentAgent 24.01.2014 11:03:53 2020 (0x07E4)

Assignment ({CF98ABA8-D808-41E2-BF42-D001CA6963B0}) reconnected to the existing job ({B4D82189-930F-4919-8A55-3CFBD486D8F4}) successfully. UpdatesDeploymentAgent 24.01.2014 11:03:53 2020 (0x07E4)

Assignment {6D9FF552-2F14-457A-9C50-C40B2F47B22D} has total CI = 60 UpdatesDeploymentAgent 24.01.2014 11:03:53 2020 (0x07E4)

Assignment ({6D9FF552-2F14-457A-9C50-C40B2F47B22D}) reconnected to the existing job ({9B5966EB-DB2D-4862-9AE9-B20C35253227}) successfully. UpdatesDeploymentAgent 24.01.2014 11:03:53 2020 (0x07E4)

Assignment {8007920A-4A52-404B-A5D1-B66987C92757} has total CI = 351 UpdatesDeploymentAgent 24.01.2014 11:03:53 2020 (0x07E4)

Assignment ({8007920A-4A52-404B-A5D1-B66987C92757}) reconnected to the existing job ({E9309D61-3E58-4AB1-BD00-E25C00215C3D}) successfully. UpdatesDeploymentAgent 24.01.2014 11:03:53 2020 (0x07E4)

Assignment {8D8CAD86-182F-44E4-810D-97D422666261} has total CI = 10 UpdatesDeploymentAgent 24.01.2014 11:03:53 2020 (0x07E4)

Assignment ({8D8CAD86-182F-44E4-810D-97D422666261}) reconnected to the existing job ({A38CE0E4-471C-4830-AE5F-CE1B9B5D8A2C}) successfully. UpdatesDeploymentAgent 24.01.2014 11:03:53 2020 (0x07E4)

Assignment {FB81169B-3CA6-4AFE-AC7A-594EBABFC84C} has total CI = 351 UpdatesDeploymentAgent 24.01.2014 11:03:53 2020 (0x07E4)

Assignment ({FB81169B-3CA6-4AFE-AC7A-594EBABFC84C}) reconnected to the existing job ({9E9EB925-88B9-4458-887A-34AEBFDF99D6}) successfully. UpdatesDeploymentAgent 24.01.2014 11:03:53 2020 (0x07E4)

Assignment {53AA7BC6-3B71-40A1-9DF7-FE6B4F37886E} has total CI = 52 UpdatesDeploymentAgent 24.01.2014 11:03:53 2020 (0x07E4)

Assignment ({53AA7BC6-3B71-40A1-9DF7-FE6B4F37886E}) reconnected to the existing job ({CC366D85-94B9-4E84-9137-A48201536C88}) successfully. UpdatesDeploymentAgent 24.01.2014 11:03:53 2020 (0x07E4)

Assignment {F3CE1459-5121-4F57-9447-DA97C0C445A9} has total CI = 74 UpdatesDeploymentAgent 24.01.2014 11:03:53 2020 (0x07E4)

Assignment ({F3CE1459-5121-4F57-9447-DA97C0C445A9}) reconnected to the existing job ({A0A661A8-0F97-4DC0-9A97-BC44A791ABCD}) successfully. UpdatesDeploymentAgent 24.01.2014 11:03:53 2020 (0x07E4)

Assignment {4259ED4A-FEDD-40FC-96E4-2F9D1AF630F1} has total CI = 73 UpdatesDeploymentAgent 24.01.2014 11:03:53 2020 (0x07E4)

Assignment ({4259ED4A-FEDD-40FC-96E4-2F9D1AF630F1}) reconnected to the existing job ({E9AE693E-3983-4474-86A8-5AE1BEADF084}) successfully. UpdatesDeploymentAgent 24.01.2014 11:03:53 2020 (0x07E4)

Assignment {1BA1DA82-F045-4822-84E3-898643785628} has total CI = 52 UpdatesDeploymentAgent 24.01.2014 11:03:53 2020 (0x07E4)

Assignment ({1BA1DA82-F045-4822-84E3-898643785628}) reconnected to the existing job ({325897F3-A855-470A-99E3-AF90A145B4BD}) successfully. UpdatesDeploymentAgent 24.01.2014 11:03:53 2020 (0x07E4)

Assignment {7509EF8B-F790-4FFF-AF35-F372D9CC72C9} has total CI = 52 UpdatesDeploymentAgent 24.01.2014 11:03:53 2020 (0x07E4)

Assignment ({7509EF8B-F790-4FFF-AF35-F372D9CC72C9}) reconnected to the existing job ({78FBDE3F-DFA2-4CE5-9F61-2A7569244EC6}) successfully. UpdatesDeploymentAgent 24.01.2014 11:03:53 2020 (0x07E4)

No current service window available to run updates assignment with time required = 1 UpdatesDeploymentAgent 24.01.2014 11:03:53 2020 (0x07E4)

Startup task completed UpdatesDeploymentAgent 24.01.2014 11:03:53 2020 (0x07E4)

User logon system task UpdatesDeploymentAgent 24.01.2014 11:04:12 2912 (0x0B60)

EnumerateUpdates for action (UpdateActionInstall) - Total actionable updates = 0 UpdatesDeploymentAgent 24.01.2014 11:04:21 1916 (0x077C)

[AshrakTheWhite]

No help?

 

 

WUAHandler.log

 

Its a WSUS Update Source type ({AB6CE6FE-70E2-4244-9943-9653F0BEC7BC}), adding it. WUAHandler 28.01.2014 9:46:00 13120 (0x3340)

Existing WUA Managed server was already set (http://CORRECTSERVER), skipping Group Policy registration. WUAHandler 28.01.2014 9:46:00 13120 (0x3340)

Added Update Source ({AB6CE6FE-70E2-4244-9943-9653F0BEC7BC}) of content type: 2 WUAHandler 28.01.2014 9:46:00 13120 (0x3340)

Scan results will include superseded updates only when they are superseded by service packs and definition updates. WUAHandler 28.01.2014 9:46:00 13120 (0x3340)

Search Criteria is (DeploymentAction=* AND Type='Software') OR (DeploymentAction=* AND Type='Driver') WUAHandler 28.01.2014 9:46:00 13120 (0x3340)

Async searching of updates using WUAgent started. WUAHandler 28.01.2014 9:46:00 13120 (0x3340)

Async searching completed. WUAHandler 28.01.2014 9:46:04 12648 (0x3168)

Successfully completed scan. WUAHandler 28.01.2014 9:46:05 13120 (0x3340)

Its a WSUS Update Source type ({AB6CE6FE-70E2-4244-9943-9653F0BEC7BC}), adding it. WUAHandler 28.01.2014 9:48:31 11816 (0x2E28)

Existing WUA Managed server was already set (http://CORRECTSERVER), skipping Group Policy registration. WUAHandler 28.01.2014 9:48:31 11816 (0x2E28)

Added Update Source ({AB6CE6FE-70E2-4244-9943-9653F0BEC7BC}) of content type: 2 WUAHandler 28.01.2014 9:48:31 11816 (0x2E28)

Scan results will include superseded updates only when they are superseded by service packs and definition updates. WUAHandler 28.01.2014 9:48:31 11816 (0x2E28)

Search Criteria is (DeploymentAction=* AND Type='Software') OR (DeploymentAction=* AND Type='Driver') WUAHandler 28.01.2014 9:48:31 11816 (0x2E28)

Async searching of updates using WUAgent started. WUAHandler 28.01.2014 9:48:31 11816 (0x2E28)

Async searching completed. WUAHandler 28.01.2014 9:48:34 12560 (0x3110)

Successfully completed scan. WUAHandler 28.01.2014 9:48:35 11816 (0x2E28)

Its a WSUS Update Source type ({AB6CE6FE-70E2-4244-9943-9653F0BEC7BC}), adding it. WUAHandler 28.01.2014 9:59:02 7404 (0x1CEC)

Existing WUA Managed server was already set (http://CORRECTSERVER), skipping Group Policy registration. WUAHandler 28.01.2014 9:59:02 7404 (0x1CEC)

Added Update Source ({AB6CE6FE-70E2-4244-9943-9653F0BEC7BC}) of content type: 2 WUAHandler 28.01.2014 9:59:02 7404 (0x1CEC)

Scan results will include superseded updates only when they are superseded by service packs and definition updates. WUAHandler 28.01.2014 9:59:02 7404 (0x1CEC)

Search Criteria is (DeploymentAction=* AND Type='Software') OR (DeploymentAction=* AND Type='Driver') WUAHandler 28.01.2014 9:59:02 7404 (0x1CEC)

Async searching of updates using WUAgent started. WUAHandler 28.01.2014 9:59:02 7404 (0x1CEC)

Async searching completed. WUAHandler 28.01.2014 9:59:05 12840 (0x3228)

Successfully completed scan. WUAHandler 28.01.2014 9:59:06 12860 (0x323C)

UpdatesHangler.log

Initiating updates scan for checking applicability. UpdatesHandler 28.01.2014 9:46:00 13120 (0x3340)

Successfully initiated scan. UpdatesHandler 28.01.2014 9:46:00 13120 (0x3340)

Updates scan completion received, result = 0x0. UpdatesHandler 28.01.2014 9:46:05 13120 (0x3340)

Method (Discover) called from SDM. UpdatesHandler 28.01.2014 9:46:11 13120 (0x3340)

Starting job with id = {99CF0088-3D8F-4F8D-AC0F-8319093229DE} UpdatesHandler 28.01.2014 9:46:11 13120 (0x3340)

Initiating Scan. Forced = (0) UpdatesHandler 28.01.2014 9:46:11 13120 (0x3340)

Successfully initiated scan for job ({99CF0088-3D8F-4F8D-AC0F-8319093229DE}). UpdatesHandler 28.01.2014 9:46:12 13120 (0x3340)

Initiating updates scan for checking applicability. UpdatesHandler 28.01.2014 9:48:00 11816 (0x2E28)

Successfully initiated scan. UpdatesHandler 28.01.2014 9:48:00 11816 (0x2E28)

Updates scan completion received, result = 0x0. UpdatesHandler 28.01.2014 9:48:00 12876 (0x324C)

Method (Discover) called from SDM. UpdatesHandler 28.01.2014 9:48:03 12872 (0x3248)

Starting job with id = {45617E27-067E-4CCC-AAC7-F11010C0FDE0} UpdatesHandler 28.01.2014 9:48:03 12872 (0x3248)

Initiating Scan. Forced = (0) UpdatesHandler 28.01.2014 9:48:03 12872 (0x3248)

Successfully initiated scan for job ({45617E27-067E-4CCC-AAC7-F11010C0FDE0}). UpdatesHandler 28.01.2014 9:48:03 12872 (0x3248)

UpdatesDeployment.log

Message received: '<?xml version='1.0' ?>

<CIAssignmentMessage MessageType='Activation'>

<AssignmentID>{2A4F2290-7982-4F26-9E4D-8B7F26643DE3}</AssignmentID>

</CIAssignmentMessage>' UpdatesDeploymentAgent 28.01.2014 9:46:00 12876 (0x324C)

Assignment {2A4F2290-7982-4F26-9E4D-8B7F26643DE3} has total CI = 158 UpdatesDeploymentAgent 28.01.2014 9:46:00 12876 (0x324C)

Assignment ({2A4F2290-7982-4F26-9E4D-8B7F26643DE3}) received activation trigger UpdatesDeploymentAgent 28.01.2014 9:46:00 12876 (0x324C)

Detection job ({99CF0088-3D8F-4F8D-AC0F-8319093229DE}) started for assignment ({2A4F2290-7982-4F26-9E4D-8B7F26643DE3}) UpdatesDeploymentAgent 28.01.2014 9:46:00 12876 (0x324C)

Progress received for assignment ({2A4F2290-7982-4F26-9E4D-8B7F26643DE3}) UpdatesDeploymentAgent 28.01.2014 9:46:12 12876 (0x324C)

Message received: '<?xml version='1.0' ?>

<CIAssignmentMessage MessageType='Activation'>

<AssignmentID>{B1786919-4FC8-4D0C-B864-B6498C78B758}</AssignmentID>

</CIAssignmentMessage>' UpdatesDeploymentAgent 28.01.2014 9:48:00 12876 (0x324C)

Assignment {B1786919-4FC8-4D0C-B864-B6498C78B758} has total CI = 88 UpdatesDeploymentAgent 28.01.2014 9:48:00 12876 (0x324C)

Assignment ({B1786919-4FC8-4D0C-B864-B6498C78B758}) received activation trigger UpdatesDeploymentAgent 28.01.2014 9:48:00 12876 (0x324C)

Detection job ({45617E27-067E-4CCC-AAC7-F11010C0FDE0}) started for assignment ({B1786919-4FC8-4D0C-B864-B6498C78B758}) UpdatesDeploymentAgent 28.01.2014 9:48:00 12876 (0x324C)

Progress received for assignment ({B1786919-4FC8-4D0C-B864-B6498C78B758}) UpdatesDeploymentAgent 28.01.2014 9:48:03 9240 (0x2418)

Message received: '<?xml version='1.0' ?><SoftwareUpdatesMessage MessageType='EvaluateAssignments'><UseCachedResults>False</UseCachedResults></SoftwareUpdatesMessage>' UpdatesDeploymentAgent 28.01.2014 9:48:33 11816 (0x2E28)

Removing scan history to force non cached results UpdatesDeploymentAgent 28.01.2014 9:48:33 11816 (0x2E28)

Assignment({B1786919-4FC8-4D0C-B864-B6498C78B758}) already in progress state (AssignmentStateDetecting). No need to evaluate UpdatesDeploymentAgent 28.01.2014 9:48:33 11816 (0x2E28)

Assignment({2A4F2290-7982-4F26-9E4D-8B7F26643DE3}) already in progress state (AssignmentStateDetecting). No need to evaluate UpdatesDeploymentAgent 28.01.2014 9:48:33 11816 (0x2E28)

Evaluation initiated for (0) assignments. UpdatesDeploymentAgent 28.01.2014 9:48:33 11816 (0x2E28)

EnumerateUpdates for action (UpdateActionInstall) - Total actionable updates = 0 UpdatesDeploymentAgent 28.01.2014 9:49:51 13244 (0x33BC)

i have reinstalled WSUS 3 times now no change.

[Edenost]

I might be wrong, but are those logs the WSUS logs? Have you checked the SCCM logs them selves, like ruleengine.log?

Have you configured SCCM to manage Updates? Or do you use WSUS?

[AshrakTheWhite]

SCCM manages updates, those are SCCM logs relevant to deployment of updates.

 

I have a premier support case open with this problem.

[AshrakTheWhite]

Issue is resolved.

 

During the upgrade process i did not export the WSUS database, so the database version of the WSUS was lower than the required version of updates on the clients. the SCCM database had catalog version higher than wsus.

 

To troubleshoot this enable debug loging on client

 

create key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM\Logging\DebugLogging under it string calue with name Enabled and value True

 

In scan agent log look for similar entry CScanAgent::ScanByUpdates- Added Policy to final ScanRequest List UpdateSourceID={AB6CE6FE-70E2-4244-9943-9653F0BEC7BC}, Policy-ContentVersion=1000, Required-ContentVersion=670

 

If policy content version is lower than Required-ContentVersion you have same problem as me.

 

To fix this go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Components\SMS_WSUS_SYNC_MANAGER on the SCCM server

 

increment ContentVersion, LastAttemptVersion, SyncToVersion. to Required-ContentVersion + 1

 

Give it some time and updates will start working again.