amlederer Posted June 16, 2015 Report post Posted June 16, 2015 We are in the process of a n environment wide patch remeidation effort. An issue I am running into is that if we run windows updates manually updates are listed important updates. When I push the same update via SCCM is comes back with a status of not required. Why is there the discrepency? Is there anyway to force an install of "Not required" updates? The goal would be that if windows updates was run manually it would find no important updates Quote Share this post Link to post Share on other sites More sharing options...
Eswar Koneti Posted June 16, 2015 Report post Posted June 16, 2015 logs can help you to check what is required and what is not.check wuahanlder.log,updatestore.log and updatesdeployment.log . More info about software update troubleshooting.read this post http://eskonr.com/2015/04/sccm-2012-troubleshoot-client-software-update-issues/ Quote Share this post Link to post Share on other sites More sharing options...
amlederer Posted June 16, 2015 Report post Posted June 16, 2015 While that makes sens in some ways it doesn't in others. The clients grab all new patch tuesday updates and install with no problem. This tells me they are communicating fine with the SCCM server...It is when applying older catchup patches that we see it. For example KB3032655 Yet if I go to those PC's and run windows update manually from Microsoft it tells me it is an important update Quote Share this post Link to post Share on other sites More sharing options...
Peter van der Woude Posted June 16, 2015 Report post Posted June 16, 2015 Are you by any change running Windows 7 x86? If so, please have a look at this: http://blogs.technet.com/b/configurationmgr/archive/2015/04/15/support-tip-configmgr-2012-update-scan-fails-and-causes-incorrect-compliance-status.aspx Quote Share this post Link to post Share on other sites More sharing options...
amlederer Posted June 16, 2015 Report post Posted June 16, 2015 Are you by any change running Windows 7 x86? If so, please have a look at this: http://blogs.technet.com/b/configurationmgr/archive/2015/04/15/support-tip-configmgr-2012-update-scan-fails-and-causes-incorrect-compliance-status.aspx We are running 7 x86 although I do not see that error in the windows update logs Quote Share this post Link to post Share on other sites More sharing options...
amlederer Posted June 16, 2015 Report post Posted June 16, 2015 Never mind, just ran a new software update scan cycle and I do thee the error. I will run hotfix and try again Quote Share this post Link to post Share on other sites More sharing options...
amlederer Posted June 16, 2015 Report post Posted June 16, 2015 Thank you Peter. This did the trick on my test box. I will deploy this to all PC's and then we should be in business Quote Share this post Link to post Share on other sites More sharing options...
amlederer Posted June 17, 2015 Report post Posted June 17, 2015 Of course about 1/3 of the PC's saw the update as not required so I will manually force the install on those. Quote Share this post Link to post Share on other sites More sharing options...
Peter van der Woude Posted June 17, 2015 Report post Posted June 17, 2015 Yeah, a package-program would be the best in this case. Quote Share this post Link to post Share on other sites More sharing options...
