Updates Show as Deployed, but not Installed

I just deployed a software update group and now all the updates say deployed, but they are not installed? Am I missing a step here?

August 17th, 2015 12:41pm

How long have you waited so far? (And don't set any intervals to 5min as you suggested in another thread)
Deployed just tells you that the update is member of a software update groups that is deployed to a collection. It will take a while until clients receive the policy, install the update and report data back. Have you already examined the Monitoring node / Deployments?
Free Windows Admin Tool Kit Click here and download it now
August 17th, 2015 1:04pm

I waited the whole weekend to check it again and no status that the updates have been deployed. Even checking installed updates there is nothing there. Also when I changed intervals to 5 minutes it really assisted in my applications being deployed faster. Thank you for your response. When I look at the monitoring node and check deployments compliance is 0%. Funny thing is I do see the client changes the service of windows updates to started shortly after deploying. Is there a good log to check for windows updates?
 The completion statistics are unknown.
  • Edited by mofayew 14 hours 17 minutes ago
August 17th, 2015 1:19pm

I waited the whole weekend to check it again and no status that the updates have been deployed. Even checking installed updates there is nothing there. Also when I changed intervals to 5 minutes it really assisted in my applications being deployed faster. Thank you for your response. When I look at the monitoring node and check deployments compliance is 0%. Funny thing is I do see the client changes the service of windows updates to started shortly after deploying. Is there a good log to check for windows updates?
 The completion statistics are unknown.
  • Edited by mofayew Monday, August 17, 2015 5:29 PM
Free Windows Admin Tool Kit Click here and download it now
August 17th, 2015 5:16pm

Yes, I know this is an old post, but Im trying to clean them up. Did you solve this problem, if so what was the solution?

August 29th, 2015 1:00pm

I found this a fantastic blog post for Troubleshooting SCCM updates, it walks you through the process of how updates are deployed, as well as giving you all the relevant logs.

http://blogs.technet.com/b/sudheesn/archive/2010/11/10/troubleshooting-sccm-part-iii-software-updates.aspx

I would give that a look over.

From what you've described, it sounds like you've deployed your SUG to a collection but your clients are not getting the deployment to compare metadata. So I would guess your clients either have the wrong destination set for updates, check WUAHandler.log to ensure they are looking at your SUP.

If its pointing to the right place, check the c:\windows\WindowsUpdate.log and WUAHandler to see if your client is doing Deployment eval and SU sync.

Let me know how it goes.


Free Windows Admin Tool Kit Click here and download it now
August 29th, 2015 1:21pm

I found this a fantastic blog post for Troubleshooting SCCM updates, it walks you through the process of how updates are deployed, as well as giving you all the relevant logs.

http://blogs.technet.com/b/sudheesn/archive/2010/11/10/troubleshooting-sccm-part-iii-software-updates.aspx

I would give that a look over.

From what you've described, it sounds like you've deployed your SUG to a collection but your clients are not getting the deployment to compare metadata. So I would guess your clients either have the wrong destination set for updates, check WUAHandler.log to ensure they are looking at your SUP.

If its pointing to the right place, check the c:\windows\WindowsUpdate.log and WUAHandler to see if your client is doing Deployment eval and SU sync.

Let me know how it goes.


August 29th, 2015 5:18pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics