Hey Jeff - using an ADR. User Experience tab is configured, "Display in 
Software Center and show all notifications"

Brian

Date: Tue, 12 Aug 2014 12:28:25 -0500
Subject: Re: [mssms] Security Updates not showing up in Software Center
From: [email protected]
To: [email protected]

Was the deployment done manually or with an automatic deployment rule? Either 
way, I believe that you can sepcify how the deployment interacts with software 
center.  I am not in an environment today that has a SUP or I would check and 
confirm the exact options. . .
 Jeff

On Tue, Aug 12, 2014 at 10:02 AM, Brian McDonald <[email protected]> 
wrote:




Confirmed. There are a ton of updates in the Deployments tab.

From: [email protected]
To: [email protected]

Subject: RE: [mssms] Security Updates not showing up in Software Center
Date: Tue, 12 Aug 2014 16:37:06 +0200

Rightclick computer object in console, properties and verify you see the 
security patches showing at the deployment tab…

 

From: [email protected] [mailto:[email protected]] On 
Behalf Of Brian McDonald

Sent: Tuesday, August 12, 2014 4:25 PM
To: [email protected]
Subject: [mssms] Security Updates not showing up in Software Center

 
Looking for ideas.

I have a Windows 7 client that I'm trying to deploy updates to. The client 
hasn't been patched since May. For some reason I cannot get updates that are 
made available to show up in Software Center. I have reviewed the 
PolicyEvaluator.log file and cannot find the corresponding Deployment ID, so 
I'm thinking the client isn't getting policies. However, if I deploy an 
application/package to the machine, It will show up in software center.


WUAHandler.log file indicates the following, "Received "SuccededWithErrors" 
code from WUA during search. Check WindowsUpdate.log in Windows Directory.  I 
don't see any errors in the WindowsUpdate.log file.


BTW - this is the first time I've worked on getting updates implemented in my 
environment. Looking for some ideas on what I can investigate to look into this 
further.

Thanks,

Brian

 


                                          







                                          


Reply via email to