We are running CM2012 1610.   We are running all Windows 7 32-bit workstations.   Our last round of workstation patching went well.   This was done about 9 months ago (before we updated to v1610).   I created a new patch package today and began testing it.  I noticed that in the WindowsUpdate.log on my test machines I kept getting this error:


WARNING: ISusInternal::GetUpdateMetadata2 failed, hr=8007000E

which lead me to this web page:

https://social.technet.microsoft.com/Forums/en-US/cf8fbe28-714d-49d3-b2ce-5cc5f6f79c63/some-clients-not-updating-reporting-compliant-hr8007000e-error-in-windowsupdatelog?forum=configmanagersecurity


Which lead me to this web page:

https://blogs.technet.microsoft.com/enterprisemobility/2012/04/12/software-update-content-cleanup-in-system-center-2012-configuration-manager/


This second web page I followed.   I searched for all EXPIRED update in CM2012.  It retunred 0.  

I then created this .CMD file and I deployed it to my test machines.

@ECHO OFF
Net stop wuauserv
ping 127.0.0.1 -s 3
Sc config wuauserv type= own
ping 127.0.0.1 -s 3
Net start wuauserv
echo "wuauserv service was stopped and re-started" >> c:\windows\ITTools\logs\wuauserv.txt


I then deployed a Windows 7 patch package to my test machines.   I still see this in the WindowsUpdates.log file on all systems.

I've read quite a few things to try but so far it is still a big problem.   is there anything I can do within WSUS?

And I must add.....we have 1 CM2012 Primary site server and on this server we have both  SQL and the WSUS role installed.   We only have 3,000 total end points so 1 Primary is all we needed.   Is there anything I can do within WSUS to fix this?  it seems to be a memory leak on Windows 7 that CM2012 does not like.   Or is there a patch I can deploy (as a package) that will fix this Windows 7 issue?  

Any/all help would be great!!




2017-01-3107:40:36:4676056101cAgent**  END  **  Agent: Finding updates [CallerId = CcmExec]
2017-01-3107:40:36:4676056101cAgent*************
2017-01-3107:40:36:5266056101cReportREPORT EVENT: {12516C03-6692-46BA-84C2-4548983F5FBF}2017-01-31 07:40:36:399-08001147101{00000000-0000-0000-0000-000000000000} 00CcmExecSuccessSoftware SynchronizationWindows Update Client successfully detected 466 updates.
2017-01-3107:40:36:5266056101cReportREPORT EVENT: {CDD0208E-06A2-46C1-BE98-A7DAB202CD35}2017-01-31 07:40:36:401-08001156101{00000000-0000-0000-0000-000000000000} 00CcmExecSuccessPre-Deployment CheckReporting client status.
2017-01-3107:40:36:5276056101cReportCWERReporter finishing event handling. (00000000)
2017-01-3107:40:36:5276056101cReportCWERReporter finishing event handling. (00000000)
2017-01-3107:40:36:5276056101cReportCWERReporter finishing event handling. (00000000)
2017-01-3107:40:36:5276056101cReportCWERReporter finishing event handling. (00000000)
2017-01-3107:40:36:5276056101cReportCWERReporter finishing event handling. (00000000)
2017-01-3107:40:36:5286056101cReportCWERReporter finishing event handling. (00000000)
2017-01-3107:40:36:5286056101cReportCWERReporter finishing event handling. (00000000)
2017-01-3107:40:36:5286056101cReportCWERReporter finishing event handling. (00000000)
2017-01-3107:40:36:5286056101cReportCWERReporter finishing event handling. (00000000)
2017-01-3107:40:36:5296056101cReportCWERReporter finishing event handling. (00000000)
2017-01-3107:40:36:5296056101cReportCWERReporter finishing event handling. (00000000)
2017-01-3107:40:36:5296056101cReportCWERReporter finishing event handling. (00000000)
2017-01-3107:40:36:5296056101cReportCWERReporter finishing event handling. (00000000)
2017-01-3107:40:36:5306056101cReportCWERReporter finishing event handling. (00000000)
2017-01-3107:40:36:5306056101cReportCWERReporter finishing event handling. (00000000)
2017-01-3107:40:36:5306056101cReportCWERReporter finishing event handling. (00000000)
2017-01-3107:40:36:5306056101cReportCWERReporter finishing event handling. (00000000)
2017-01-3107:40:36:5316056101cReportCWERReporter finishing event handling. (00000000)
2017-01-3107:40:36:5316056101cReportCWERReporter finishing event handling. (00000000)
2017-01-3107:40:36:5316056101cReportCWERReporter finishing event handling. (00000000)
2017-01-3107:40:36:5316056101cReportCWERReporter finishing event handling. (00000000)
2017-01-3107:40:36:5326056101cReportCWERReporter finishing event handling. (00000000)
2017-01-3107:40:36:5326056101cReportCWERReporter finishing event handling. (00000000)
2017-01-3107:40:36:5326056101cReportCWERReporter finishing event handling. (00000000)
2017-01-3107:40:36:5326056101cReportCWERReporter finishing event handling. (00000000)
2017-01-3107:40:36:5336056101cReportCWERReporter finishing event handling. (00000000)
2017-01-3107:40:36:5336056101cReportCWERReporter finishing event handling. (00000000)
2017-01-3107:40:36:5336056101cReportCWERReporter finishing event handling. (00000000)
2017-01-3107:40:36:5336056101cReportCWERReporter finishing event handling. (00000000)
2017-01-3107:40:36:5346056101cReportCWERReporter finishing event handling. (00000000)
2017-01-3107:40:36:5346056101cReportCWERReporter finishing event handling. (00000000)
2017-01-3107:40:36:5346056101cReportCWERReporter finishing event handling. (00000000)
2017-01-3107:40:36:5346056101cReportCWERReporter finishing event handling. (00000000)
2017-01-3107:40:36:5346056101cReportCWERReporter finishing event handling. (00000000)
2017-01-3107:40:36:5356056101cReportCWERReporter finishing event handling. (00000000)
2017-01-3107:40:36:5356056101cReportCWERReporter finishing event handling. (00000000)
2017-01-3107:40:36:5356056101cReportCWERReporter finishing event handling. (00000000)
2017-01-3107:40:36:5356056101cReportCWERReporter finishing event handling. (00000000)
2017-01-3107:40:36:5366056101cReportCWERReporter finishing event handling. (00000000)
2017-01-3107:40:36:5366056101cReportCWERReporter finishing event handling. (00000000)
2017-01-3107:40:36:5366056101cReportCWERReporter finishing event handling. (00000000)
2017-01-3107:40:36:5366056101cReportCWERReporter finishing event handling. (00000000)
2017-01-3107:40:36:5376056101cReportCWERReporter finishing event handling. (00000000)
2017-01-3107:40:36:5376056101cReportCWERReporter finishing event handling. (00000000)
2017-01-3107:40:36:5376056101cReportCWERReporter finishing event handling. (00000000)
2017-01-3107:40:36:5376056101cReportCWERReporter finishing event handling. (00000000)
2017-01-3107:40:36:54215401164COMAPI>>--  RESUMED  -- COMAPI: Search [ClientId = CcmExec]
2017-01-3107:40:37:19115401164COMAPI - Updates found = 466
2017-01-3107:40:37:19115401164COMAPI---------
2017-01-3107:40:37:19115401164COMAPI--  END  --  COMAPI: Search [ClientId = CcmExec]
2017-01-3107:40:37:19115401164COMAPI-------------
2017-01-3107:40:37:68715401164COMAPIWARNING: ISusInternal::GetUpdateMetadata2 failed, hr=8007000E
2017-01-3107:40:41:4716056101cReportCWERReporter finishing event handling. (00000000)

mqh7

I have an ADR created for adobe acrobat reader updates.  I am pulling the updates in thru the SCUP. If I click on All Software Updates and do a search with the criteria of Product = Adobe Reader I see the Adobe Acrobat Reader DC updates and several of them are required. If I go to my ADR the software updates tab has the following criteria 

Product= "Adobe Reader" Required >0 

When I hit preview Adobe Reader 10 and 11 updates show in the preview windows but no DC updates.

I don't get it.

Thanks

Hi All, after the Maintenance window is finished we still see few servers with patches missing on them because of various reasons, so what would be the best way to handle this scenarios? And is it possible for any Automation with powershell? Thanks in Advance. 

When using CI and Config. Baselines you have reports to look at compliance history. How far back can you go in history. I would think that this compliance history is cleaned at some point but cannot find it?

I looked at site maintenance task to see if there was a task that is responsible to cleanup this date but it is not.

so my question: Is compliance history cleaned after a while and ho long can be go back in time to look at compliance history?

thx in advance

I have an issue with my current setup which consists of a Server 2008 R2 SP1 box with SCUP 2011, SCCM 2012, and WSUS 3.2.7600.226 installed on it as well.  I followed the guide here for setting up custom updates (specifically for Adobe):  http://blog.coretech.dk/kea/the-complete-scup-2011-installation-and-configuration-guide/. Whenever I attempt to publish full content, I get the following errors in the SCUP log:

2014-08-28 19:08:50.375 UTCErrorScup2011.8Publisher.SignPackageCabError signing cab file: K:\WSUS\UpdateServicesPackages\9d002f7e-f84c-42f4-8381-f9fce9b3b920\b403f819-3221-46d6-9e5c-b997b062264a_1.cab, result: 21479424032004114283 (0x77745B6B)

2014-08-28 19:08:50.376 UTCErrorScup2011.8Publisher.PublishPackagePublishPackage(): Operation Failed with Error: Failed to sign package; error was: 21479424032004114283 (0x77745B6B)

PublishItem: InvalidException occurred during publishing: Failed to sign package; error was: 2147942403Updates Publisher8/28/2014 2:08:50 PM8 (0x0008)

Publish: A fatal error occurred during publishing :Signature verification exception during publish, verify the WSUS certificates and advanced timestamp setting are properly configured.Updates Publisher8/28/2014 2:08:50 PM8 (0x0008)

I did some searching, and everywhere I can see points to the issue being that the certificate is not correctly placed into the Computer Accounts "Trusted Publishers" and "Trusted Root Certification Authorities" certificate stores.  However, I verified that they were indeed located there.  I also deleted and re-added the certificates, as some people had posted that resolved the issue.  It did not for me.

I did some more searching, and I saw some people had success just blowing out the existing certificate/SCUP install and trying again.  So, i went through the whole process of reinstalling SCUP (making sure the required hotfix was pre-installed), generated a new certificate, placed it into the above listed stores.  I still get this error message.  In SCUP I have tried both checking and unchecking the "Add timestamp when signing updates" box under options --> Advanced.  Same result.

I am at a bit of a loss where to go from here.  Looking at the error, the directory K:\WSUS\UpdateServicesPackages\9d002f7e-f84c-42f4-8381-f9fce9b3b920 doesn't exist (the path K:\WSUS\UpdateServicePackages does, just that directory doesn't), but I wasn't sure if that was just because it failed to sign it/failed to create the package.

Hi All

I have seen some threads about this in the forums.

I am in the same boat, where an automated software updates deployment kicks in overnight on number of servers.

It then encounters an update that failed to install. Upon reboot of the server, the failed update does not get retried during the Maintenance window period.

From various workarounds suggested to get the failed update installed during the maintenance window period, these two are what I like so far.

Has anyone tried them, and wondering which would be the favourable method?

1. Setup a package that kicks off a script which will kick off the "Update SCCM Scan Agent" and "Update SCCM Updates Deployment Agent". This package can be scheduled to run every week at specific time, or few hours after the software updates deployment is scheduled.

2. Create a custom Client Setting for the targeted servers. Configure "Software Update Scan Schedule" to run every day. The timing is the importance here. I need to time this so that it runs, few hours after when the software updates deployment was scheduled, and estimate time of when the servers are rebooted. So in theory, lets say patching is scheduled to kick off at 8pm on Friday night, and expect that the patching to be complete and server rebooted by 10pm. I would schedule the "Software Update Scan Schedule" to kick off at midnight everynight. So in theory, if my maintenance window is till 6am in the morning, the failed update should kick off again after the scan.

Your thoughts?

Thanks, DM.

Guys I know this might be old/ regular issue many might have faced.

The software update status just wont change for certain machines. The machines receive the patches, install as well. But the status of them is not reported as compliant in the reports :-(. 

The statemsg.log mentions 'Successfully forwarded State Messages to the MP'. However the state just wont change.

Client is healthy, as they are able to receive patches and install as well.

Is there any way to check if those machines are connected via VPN? or using any proxy. 

GPO is standard for all these machines, and no automatic updates enabled. 

System Security analyst at CapG

Hi All,

WSUS Sync is getting failed on our Upstream server for the first time it tries to sync daily on schedule, again it succeeds without any intervention. please find the below details

Wsyncmgr.log

sync: SMS synchronizing categories, processed 0 out of 273 items (0%) 
sync: SMS synchronizing categories, processed 273 out of 273 items (100%) 
sync: SMS synchronizing categories, processed 273 out of 273 items (100%) 
sync: SMS synchronizing updates 
sync: SMS synchronizing updates, processed 0 out of 1 items (0%) 
Synchronizing update 0fe4758a-4463-4797-b786-88082b360a39 - Definition Update for Microsoft Endpoint Protection - KB2461484 (Definition 1.203.310.0) 
sync: SMS synchronizing updates, processed 1 out of 1 items (100%) 
sync: SMS performing cleanup 
Sync failed: The operation has timed out. Source: Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponse 
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=CONTOSO.net SITE=CAS PID=8352 TID=6928 GMTDATE=Fri Jul 24 05:06:09.441 2015 ISTR0="Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponse" ISTR1="The operation has timed out" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 
Sync failed. Will retry in 60 minutes 
Setting sync alert to active state on site CAS 
Updated 13 items in SMS database, new update source content version is 2742 
Sync time: 0d00h06m09s 
Sending sync notification to child site(s): 1PR 
SQL Replication type has not been set for D:\Program Files\Microsoft Configuration Manager\inboxes\wsyncmgr.box\outbox\CAS.SYN, replicating to (1PR), inbox: D:\Program Files\Microsoft Configuration Manager\inboxes\replmgr.box 
Wakeup for a polling cycle 
Starting Sync 
Performing sync on retry schedule 
Read SUPs from SCF for CONTOSO.net 
Found 1 SUPs 
Found active SUP CONTOSO.NET from SCF File. 
STATMSG: ID=6701 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=CONTOSO.net SITE=CAS PID=8352 TID=6928 GMTDATE=Fri Jul 24 06:06:09.203 2015 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 
Synchronizing WSUS server CONTOSO.net 
STATMSG: ID=6704 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=CONTOSO.net SITE=CAS PID=8352 TID=6928 GMTDATE=Fri Jul 24 06:06:10.225 2015 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 
Synchronizing WSUS server CONTOSO.net ... 
sync: Starting WSUS synchronization 
Done synchronizing WSUS Server CONTOSO.net 
Sleeping 2 more minutes for WSUS server sync results to become available 
Set content version of update source {3C8C5A5C-3EEC-44FD-9654-421F428E7347} for site CAS to 2742 
Synchronizing SMS database with WSUS server CONTOSO.net 
STATMSG: ID=6705 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=CONTOSO.net SITE=CAS PID=8352 TID=6928 GMTDATE=Fri Jul 24 06:08:16.288 2015 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 
Synchronizing SMS database with WSUS server CONTOSO.net ... 
sync: Starting SMS database synchronization 

could not find any error in WCM,WSUSCtrl.logs.

please find the event log.

Log Name:      Application
Source:        SMS Server
Date:          7/24/2015 12:06:09 AM
Event ID:      6703
Task Category: SMS_WSUS_SYNC_MANAGER
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      contoso.net
Description:
On 7/24/2015 12:06:09 AM, component SMS_WSUS_SYNC_MANAGER on computer contoso.net reported:   WSUS Synchronization failed.
 Message: The operation has timed out.
 Source: Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponse.
  The operating system reported error 2148734217:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="SMS Server" />
    <EventID Qualifiers="49152">6703</EventID>
    <Level>2</Level>
    <Task>73</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-07-24T05:06:09.000000000Z" />
    <EventRecordID>170971</EventRecordID>
    <Channel>Application</Channel>
    <Computer>contoso.net</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponse</Data>
    <Data>The operation has timed out</Data>
    <Data>
    </Data>
    <Data>
    </Data>
     <Data>On 7/24/2015 12:06:09 AM, component SMS_WSUS_SYNC_MANAGER on computer contoso.net reported:  </Data>
    <Data> The operating system reported error 2148734217: </Data>
  </EventData>
</Event>

Prashanth Kumar System Center Administrator

What can I do to make these updates available in "All Software Updates" so that they can be deployed as part of our monthly updates cycle? Currently, SCCM ignores these when synchronizing with Microsoft (we have all products selected). This has become a headache for a couple of reasons. 

1) Updates tagged with InstallationCanRequestUserInput = 1 don't show up as missing from a client in SCCM. You can find out that they are missing by checking the client from the client itself (e.g. scan for updates from Microsoft).

2) Since they aren't available in All Software Updates, the only way to deploy them seems to be manually downloading them and creating a deployment package each month they are released. This means discovering that they are needed in the first place and then downloading them manually and manually creating deployment packages. 

While I can understand that you might not want to automatically deploy updates that can request user input, making them totally unavailable in SCCM seems extreme (especially when they can be critical or security updates). In practice, we found that many of the updates tagged this way did not end up requiring manual intervention, although post process commands and more than one reboot may have been required. Some recent examples of these type of security updates are:

Dear Folks,

As i have recently upgraded to Config Mgr 1602 and it went very smooth upgrade. But after a few days found annoying issue regarding updates. PC's esp with Windows 10 are not installing updates. Every time trying to manual install it prompts this error as shown in snapshot  

As per error description, 

But i have not configured any service windows on any collection. Then which service window is preventing from updates to instal. Furthermore, no error found in any logs file. Almost gone through all files.

I hope raised concern is clear. Waiting for your help and suggestion

Thank You

REGARDS DANISH DANIE

I've created a custom report that shows the deployment status of a software update group.  This is the query:

SELECT
li.title as [Software Update Group],
li.ModelID,
coll.name as [Collection Name],
SUM (DS.NumberSuccess) as [Successful],
SUM (DS.NumberInProgress) as [In Progress],
SUM (DS.NumberErrors) as [Error]

FROM v_DeploymentSummary DS
inner join v_collection COLL on COLL.collectionid = DS.collectionid
inner join v_AuthListInfo LI on LI.ModelID = DS.ModelID

WHERE li.ModelID = @model
AND coll.name = @collname

GROUP BY li.title, coll.name, li.ModelID
ORDER BY coll.name

Parameter One:

SELECT title as [Software Update Group],
ModelId

FROM v_AuthListInfo

ORDER by title

Parameter Two:

SELECT DISTINCT CollectionName,
ModelID

FROM  dbo.v_DeploymentSummary

WHERE ModelID like @model

ORDER BY CollectionName

This above works as expected.  What I want to do now is drill down the successful, in progress and error numbers too see a list of machines in each state.  

I have written a query that will produce a list of machines in a certain software update group for a certain collection (below).  There is no way to specify one state from another.  Therefore, when you click on the number of successful, you get a list of 1065 machines when there should only be 769.  The same results are produced when clicking on In Progress / Error.  The only way to limit the results is to pass the subquery a parameter distinguishing the states from one another.  The problem is the states are listed in three separate columns in the v_DeploymentSummary view rather than one common column.  How can I fix this subquery to work for each state?

SELECT sys.Name0 as [Computer Name],
li.title,
Min(ad.AgentTime) as [Last Heartbeat Time Stamp]

FROM v_r_system sys
full outer join v_AgentDiscoveries ad on ad.ResourceID = sys.ResourceID
full outer join v_FullCollectionMembership fcm on fcm.ResourceID = sys.ResourceID
inner join v_DeploymentSummary DS on DS.collectionid = fcm.collectionid
inner join v_collection COLL on COLL.collectionid = DS.collectionid
inner join v_AuthListInfo LI on LI.ModelID = DS.ModelID

WHERE ad.AgentName like 'Heartbeat Discovery'
AND (li.ModelId=@model and coll.name=@collname)

GROUP BY sys.name0, ad.AgentName, li.title

ORDER BY [Last Heartbeat Time Stamp]

To be clear, I do not want this report to show compliance numbers.  I want this report to show thestatus of a software update deployment.

Hi,

With SCCM 2012 R2 CY5, we have a strange behavior where some computers are just rebooting after a patch distribution.

From RebootCoordinator.log

User S-1-5-18 is getting pending reboot information...	RebootCoordinator	2017-01-09 15:05:21	5288 (0x14A8)
Entered ScheduleRebootImpl - requested from 'UpdatesDeploymentAgent'. set Rebootby = 0. set NotifyUI = False. set PreferredRebootWindowType = 4	RebootCoordinator	2017-01-09 15:18:23	1748 (0x06D4)
Scheduled non mandatory reboot from agent UpdatesDeploymentAgent	RebootCoordinator	2017-01-09 15:18:23	1748 (0x06D4)
User logoff notification received	RebootCoordinator	2017-01-09 15:18:54	6344 (0x18C8)

In UpdatesDeployment

Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_99248b4d-e3e9-41fd-af39-8d960997ad08) Progress: Status = ciStateDetecting, PercentComplete = 0, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:01:53	5376 (0x1500)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_31c27622-134b-41c9-8868-12932e358864) Progress: Status = ciStateDownloading, PercentComplete = 0, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:01:53	6584 (0x19B8)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_4518a5b2-3892-4ca3-a3d8-08744f92d95b) Progress: Status = ciStateDownloading, PercentComplete = 0, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:01:53	6584 (0x19B8)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_5eeca461-8de6-46f3-8653-f1162c7ef67f) Progress: Status = ciStateDownloading, PercentComplete = 0, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:01:53	6584 (0x19B8)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_660aaa6c-4e63-4a7c-a54e-1c5db83ad1be) Progress: Status = ciStateDownloading, PercentComplete = 0, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:01:53	6584 (0x19B8)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_99248b4d-e3e9-41fd-af39-8d960997ad08) Progress: Status = ciStateDownloading, PercentComplete = 0, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:01:53	6584 (0x19B8)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_31c27622-134b-41c9-8868-12932e358864) Progress: Status = ciStateWaitInstall, PercentComplete = 0, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:01:53	5376 (0x1500)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_4518a5b2-3892-4ca3-a3d8-08744f92d95b) Progress: Status = ciStateWaitInstall, PercentComplete = 0, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:01:53	5376 (0x1500)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_5eeca461-8de6-46f3-8653-f1162c7ef67f) Progress: Status = ciStateWaitInstall, PercentComplete = 0, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:01:53	6584 (0x19B8)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_660aaa6c-4e63-4a7c-a54e-1c5db83ad1be) Progress: Status = ciStateWaitInstall, PercentComplete = 0, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:01:53	3972 (0x0F84)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_99248b4d-e3e9-41fd-af39-8d960997ad08) Progress: Status = ciStateWaitInstall, PercentComplete = 0, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:01:53	3592 (0x0E08)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_1553c336-e028-485b-a4c7-7f98cfebaf14) Progress: Status = ciStateInstalling, PercentComplete = 0, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:02:24	5376 (0x1500)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_1553c336-e028-485b-a4c7-7f98cfebaf14) Progress: Status = ciStateInstalling, PercentComplete = 5, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:02:24	3972 (0x0F84)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_1553c336-e028-485b-a4c7-7f98cfebaf14) Progress: Status = ciStateInstalling, PercentComplete = 10, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:02:26	6052 (0x17A4)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_1553c336-e028-485b-a4c7-7f98cfebaf14) Progress: Status = ciStateInstalling, PercentComplete = 18, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:02:27	6052 (0x17A4)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_1553c336-e028-485b-a4c7-7f98cfebaf14) Progress: Status = ciStateInstalling, PercentComplete = 25, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:02:28	5376 (0x1500)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_1553c336-e028-485b-a4c7-7f98cfebaf14) Progress: Status = ciStateInstalling, PercentComplete = 30, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:02:33	4824 (0x12D8)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_1553c336-e028-485b-a4c7-7f98cfebaf14) Progress: Status = ciStateInstalling, PercentComplete = 35, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:02:34	6052 (0x17A4)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_1553c336-e028-485b-a4c7-7f98cfebaf14) Progress: Status = ciStateInstalling, PercentComplete = 47, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:02:35	6052 (0x17A4)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_1553c336-e028-485b-a4c7-7f98cfebaf14) Progress: Status = ciStateInstalling, PercentComplete = 52, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:02:51	4824 (0x12D8)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_1553c336-e028-485b-a4c7-7f98cfebaf14) Progress: Status = ciStateInstalling, PercentComplete = 60, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:02:55	4824 (0x12D8)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_1553c336-e028-485b-a4c7-7f98cfebaf14) Progress: Status = ciStateInstalling, PercentComplete = 72, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:03:08	3592 (0x0E08)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_1553c336-e028-485b-a4c7-7f98cfebaf14) Progress: Status = ciStateInstalling, PercentComplete = 77, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:03:23	6584 (0x19B8)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_1553c336-e028-485b-a4c7-7f98cfebaf14) Progress: Status = ciStateInstalling, PercentComplete = 82, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:03:24	3592 (0x0E08)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_1553c336-e028-485b-a4c7-7f98cfebaf14) Progress: Status = ciStateInstalling, PercentComplete = 97, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:03:25	6584 (0x19B8)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_1553c336-e028-485b-a4c7-7f98cfebaf14) Progress: Status = ciStateVerifying, PercentComplete = 0, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:03:26	6584 (0x19B8)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_9985f46d-86a8-4456-ab2a-22efa20b081d) Progress: Status = ciStateInstalling, PercentComplete = 0, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:03:28	3592 (0x0E08)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_9985f46d-86a8-4456-ab2a-22efa20b081d) Progress: Status = ciStateInstalling, PercentComplete = 5, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:03:28	3592 (0x0E08)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_9985f46d-86a8-4456-ab2a-22efa20b081d) Progress: Status = ciStateInstalling, PercentComplete = 18, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:03:29	5376 (0x1500)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_9985f46d-86a8-4456-ab2a-22efa20b081d) Progress: Status = ciStateInstalling, PercentComplete = 23, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:03:29	3592 (0x0E08)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_9985f46d-86a8-4456-ab2a-22efa20b081d) Progress: Status = ciStateInstalling, PercentComplete = 28, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:03:30	6584 (0x19B8)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_9985f46d-86a8-4456-ab2a-22efa20b081d) Progress: Status = ciStateInstalling, PercentComplete = 38, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:03:32	5376 (0x1500)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_9985f46d-86a8-4456-ab2a-22efa20b081d) Progress: Status = ciStateInstalling, PercentComplete = 43, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:03:34	6584 (0x19B8)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_9985f46d-86a8-4456-ab2a-22efa20b081d) Progress: Status = ciStateInstalling, PercentComplete = 48, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:03:34	6584 (0x19B8)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_9985f46d-86a8-4456-ab2a-22efa20b081d) Progress: Status = ciStateInstalling, PercentComplete = 58, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:03:35	3592 (0x0E08)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_9985f46d-86a8-4456-ab2a-22efa20b081d) Progress: Status = ciStateInstalling, PercentComplete = 63, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:03:40	3592 (0x0E08)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_9985f46d-86a8-4456-ab2a-22efa20b081d) Progress: Status = ciStateInstalling, PercentComplete = 68, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:03:48	3592 (0x0E08)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_9985f46d-86a8-4456-ab2a-22efa20b081d) Progress: Status = ciStateInstalling, PercentComplete = 78, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:03:56	6584 (0x19B8)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_9985f46d-86a8-4456-ab2a-22efa20b081d) Progress: Status = ciStateInstalling, PercentComplete = 83, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:04:00	6584 (0x19B8)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_9985f46d-86a8-4456-ab2a-22efa20b081d) Progress: Status = ciStateInstalling, PercentComplete = 88, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:04:04	3592 (0x0E08)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_9985f46d-86a8-4456-ab2a-22efa20b081d) Progress: Status = ciStateInstalling, PercentComplete = 98, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:04:05	3592 (0x0E08)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_9985f46d-86a8-4456-ab2a-22efa20b081d) Progress: Status = ciStatePendingSoftReboot, PercentComplete = 0, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:04:06	3592 (0x0E08)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_a18c06fb-7e86-4f5f-a7ac-ddf46f0b473a) Progress: Status = ciStateInstalling, PercentComplete = 0, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:04:10	3592 (0x0E08)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_a18c06fb-7e86-4f5f-a7ac-ddf46f0b473a) Progress: Status = ciStateInstalling, PercentComplete = 5, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:04:10	3592 (0x0E08)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_a18c06fb-7e86-4f5f-a7ac-ddf46f0b473a) Progress: Status = ciStateInstalling, PercentComplete = 10, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:04:10	6052 (0x17A4)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_a18c06fb-7e86-4f5f-a7ac-ddf46f0b473a) Progress: Status = ciStateInstalling, PercentComplete = 15, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:04:10	3592 (0x0E08)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_a18c06fb-7e86-4f5f-a7ac-ddf46f0b473a) Progress: Status = ciStateInstalling, PercentComplete = 20, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:04:11	6052 (0x17A4)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_a18c06fb-7e86-4f5f-a7ac-ddf46f0b473a) Progress: Status = ciStateInstalling, PercentComplete = 40, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:04:12	6052 (0x17A4)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_a18c06fb-7e86-4f5f-a7ac-ddf46f0b473a) Progress: Status = ciStateInstalling, PercentComplete = 53, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:04:13	6052 (0x17A4)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_a18c06fb-7e86-4f5f-a7ac-ddf46f0b473a) Progress: Status = ciStateInstalling, PercentComplete = 66, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:04:14	6052 (0x17A4)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_a18c06fb-7e86-4f5f-a7ac-ddf46f0b473a) Progress: Status = ciStateInstalling, PercentComplete = 90, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:04:14	3592 (0x0E08)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_a18c06fb-7e86-4f5f-a7ac-ddf46f0b473a) Progress: Status = ciStateInstalling, PercentComplete = 100, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:04:15	3592 (0x0E08)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_a18c06fb-7e86-4f5f-a7ac-ddf46f0b473a) Progress: Status = ciStateVerifying, PercentComplete = 0, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:04:15	6584 (0x19B8)
CUpdatesJob({406BC52C-BDE4-4828-8519-CEA8915CDF14}): Job completion received.	UpdatesDeploymentAgent	2017-01-09 15:04:36	6584 (0x19B8)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_1553c336-e028-485b-a4c7-7f98cfebaf14) Progress: Status = ciStateInstallComplete, PercentComplete = 0, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:04:37	6584 (0x19B8)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_a18c06fb-7e86-4f5f-a7ac-ddf46f0b473a) Progress: Status = ciStateInstallComplete, PercentComplete = 0, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:04:37	6584 (0x19B8)
Raising client SDK event for class CCM_SoftwareUpdate, instance CCM_SoftwareUpdate.UpdateID="Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_9985f46d-86a8-4456-ab2a-22efa20b081d", actionType 11l, value NULL, user NULL, session 4294967295l, level 0l, verbosity 30l	UpdatesDeploymentAgent	2017-01-09 15:04:37	6584 (0x19B8)
Raising client SDK event for class CCM_SoftwareUpdate, instance CCM_SoftwareUpdate.UpdateID="Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_9985f46d-86a8-4456-ab2a-22efa20b081d", actionType 11l, value NULL, user NULL, session 4294967295l, level 0l, verbosity 30l	UpdatesDeploymentAgent	2017-01-09 15:04:37	6584 (0x19B8)
CUpdatesJob({406BC52C-BDE4-4828-8519-CEA8915CDF14}): Delete job from WMI	UpdatesDeploymentAgent	2017-01-09 15:04:37	4824 (0x12D8)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_31c27622-134b-41c9-8868-12932e358864) Progress: Status = ciStateInstalling, PercentComplete = 0, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:07:28	3592 (0x0E08)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_31c27622-134b-41c9-8868-12932e358864) Progress: Status = ciStateInstalling, PercentComplete = 20, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:07:28	3972 (0x0F84)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_31c27622-134b-41c9-8868-12932e358864) Progress: Status = ciStateInstalling, PercentComplete = 25, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:07:28	2876 (0x0B3C)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_31c27622-134b-41c9-8868-12932e358864) Progress: Status = ciStateInstalling, PercentComplete = 31, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:07:28	4344 (0x10F8)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_31c27622-134b-41c9-8868-12932e358864) Progress: Status = ciStateInstalling, PercentComplete = 36, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:08:23	192 (0x00C0)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_31c27622-134b-41c9-8868-12932e358864) Progress: Status = ciStateInstalling, PercentComplete = 66, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:08:23	4344 (0x10F8)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_31c27622-134b-41c9-8868-12932e358864) Progress: Status = ciStateInstalling, PercentComplete = 71, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:08:29	3972 (0x0F84)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_31c27622-134b-41c9-8868-12932e358864) Progress: Status = ciStateInstalling, PercentComplete = 88, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:08:29	4824 (0x12D8)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/SUM_31c27622-134b-41c9-8868-12932e358864) Progress: Status = ciStateInstalling, PercentComplete = 93, DownloadSize = 0, Result = 0x0	UpdatesDeploymentAgent	2017-01-09 15:08:36	2896 (0x0B50)
Update (Site_ED4A5F71-85D0-4B2C-8871-A652C7DCDA71/S

Notice this error:

Failed to open to WMI namespace '\\.\root\ccm\Policy\Machine' (8007045b)	UpdatesDeploymentAgent	2017-01-09 15:20:50	4976 (0x1370)
CUpdatesAssignmentPolicy - spPolicyAgent->ConnectSettings failed, error 8007045b	UpdatesDeploymentAgent	2017-01-09 15:20:50	4976 (0x1370)
Failed to open to WMI namespace '\\.\root\ccm\Policy\Machine' (8007045b)	UpdatesDeploymentAgent	2017-01-09 15:20:50	4976 (0x1370)
CUpdatesAssignmentPolicy - spPolicyAgent->ConnectSettings failed, error 8007045b	UpdatesDeploymentAgent	2017-01-09 15:20:50	4976 (0x1370)
Failed to open to WMI namespace '\\.\root\CCM\SoftwareUpdates\DeploymentAgent' (8007045b)	UpdatesDeploymentAgent	2017-01-09 15:20:50	4976 (0x1370)
CTargetedUpdate::Save - Failed to open \\.\root\CCM\SoftwareUpdates\DeploymentAgent namespace, error 8007045b	UpdatesDeploymentAgent	2017-01-09 15:20:50	4976 (0x1370)
Failed to resolve time properties on system time change, error = 0x8007045b	UpdatesDeploymentAgent	2017-01-09 15:20:50	4976 (0x1370)
Failed to handle system time change event, error = 0x8007045b	UpdatesDeploymentAgent	2017-01-09 15:20:50	4976 (0x1370)
OnSystemTimeChange failed, error = 0x8007045b	UpdatesDeploymentAgent	2017-01-09 15:20:50	4976 (0x1370)

This morning I tried connecting to those namespace and succeed...

The users said me it is happening every months when Software updates are deployed.

Any idea?

For the past few months we have been facing a peculiar issue in which the windows updates are not showing in the software center for few servers with Windows server 2008 standard OS.

1. OS updates has been properly added to the software update group which has been mapped to the server collection in configuration manager since the windows updates for other Windows server 2008 standard servers are showing up properly in the software center

2. I guess there is no issue in connection between client server and DP server,  since some applications which i have tried to push to the client servers are showing up in the software client without issues.

3. I have tried to reboot the server and refreshed the policies in the client. But no luck even after that.

Versions:

Configuration manager version is 2012

SCCM client version is Advanced.

Could someone help me on troubleshooting this issue?

Thanks in Advance.

Hi,

I am looking for a script to delete all the deployment (applications and Update groups) made for multiple Device collections or for multiple Software update groups.

I am using SCCM 2012 SP2

Shailendra Dev

This is a weird behaviour.

My SCCM 2012 is set to removed superseded updates automatically.

I am tasked to review and remediate a Threat, Vulnerability report generated by my security team. The report will tell, a certain update is not found on a particular client (server). I need to verify, and solve it. Tedious work.

The latest issue I encounter, a behaviour that surprised me. It happens that I checked on a few Windows 2016 clients before this Patch Tuesday. They were installed with KB4103723 or KB4103720. Both this 2 updates replaced KB4041691 which is needed that the vulnerability stated in the report. KB4284880 replaces both KB4103720 and KB4103723. But due to a delay, we are not including KB4284880 in this coming patching maintenance. And, because of the settings in my SCCM, I can only find KB4284880 inside my SCCM now, not KB4103720 or KB4103723.

Today, I was checking for vulnerability of another KB, and checked the same 3 2016 servers. KB4103723 or KB4103720 are not found on them anymore! Can someone enlighten me what is happening?

When trying to upgrade SCCM to 1802 last weekend and the hotfix for 1710, which hadn't yet been installed, started. It has consequently failed, apparently on the below line in CMUpdate.log.

INFO: Executing SQL Server command: <IF OBJECT_ID('usp_CreateSoftwareRequestByUser') IS NOT NULL GRANT EXECUTE ON [usp_CreateSoftwareRequestByUser] TO [smsdbrole_MPUserSvc]>

ERROR: Failed to execute SQL Server command, error <>

Failed to update database

We now can't do anything in SCCM with any of the updates as everything is greyed out? Can anyone please advise?

Hi All,

I was deploying the below listed 8 updates to one of my client machine. Out of these 3 updates (KB4056894,KB4056897 and KB4056568) shows as already compliant and hence its not showing in software center for installation.

Total Software Updates details-

When i try to install these 3 updates (KB) manually on the same client machine, its getting installed. Ideally if it was already compliant, then these updates should either show as no applicable or should not get installed. Not sure why this issue is happening. Any lights to this is highly appreciated.

Thanks,

I am planning deploy Windows 10 June cumulative update to all of our Windows 10 laptops and desktops. I created software update group include the June cumulative update for version 1507 and 1607. 1507 update works fine, it shows 55 machines require this update, but for 1607 update, it shows 520 machines not required. 96% compliance. I wait for amost one week, still nothing changed. is there somebody can help me about this issue?

thanks,