I'm very new to SCE so this is probably a dumb question, but ... On the computers panel where the "update status" is shown with errors if I drill down to the error (like an update was not installed or failed) is there a way to clear those errors? Some of the errors are old or not meaningful and I'd like to reset them so I can reflect new information. Basically, is there a way to clear individual update errors or warnings for a client computers?

Hi, Thank you for posting here. Please let us know the details by clicking the “Error” of the Update status. Please try clearing the cache by running the SCE console from the command line with the option: “/clearcache” and see how it works: Example: "C:\Program Files\System Center Essentials\Microsoft.SystemCenter.Essentials.UI.Console.exe" /clearcache Meanwhile, please check the WindowsUpdate.log of the problematic client. If the issue persists, please also try the methods in the following post: Troubleshooting ‘Unknown’ software and update status, ‘Not yet contacted’ and lack of hardware and software inventory http://blogs.technet.com/b/systemcenteressentials/archive/2010/03/29/troubleshooting-unknown-software-and-update-status-not-yet-contacted-and-lack-of-hardware-and-software-inventory.aspx Hope this helps. Thanks. Nicholas Li TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com.Nicholas Li - MSFT Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

I just want to say hi and see how this is going. Please drop me a quick note at you convenience to let me know the current status of this issue. If you have any questions or concerns, please do not hesitate to let me know. Thanks, and have a great day! Nicholas Li TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com. Nicholas Li - MSFT Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Actually, beyond clearing things out (which I probably shouldn't do), the biggest problem is that updates simply don’t work properly across most of the client computers. Basically, it’s as if WSUS isn’t consistently pushing updates. Sometimes they works but oftentimes they don’t, so it’s not consistent. I’ve investigated all of the things I know to check – communication to the WSUS sever machine (and that seems fine), firewall settings, registry keys, and have run things like the WSUS Client Diag Tool, but I’ve yet to see what causes many of the updates to fail. The Client Diag Tool will report most everything as fine, but will end with a connection problem: WSUS Client Diagnostics Tool Checking Machine State Checking for admin rights to run tool . . . . . . . . . PASS Automatic Updates Service is running. . . . . . . . . . PASS Background Intelligent Transfer Service is running. . . PASS Wuaueng.dll version 7.4.7600.226. . . . . . . . . . . . PASS This version is WSUS 2.0 Checking AU Settings AU Option is 4: Scheduled Install . . . . . . . . . . . PASS Option is from Policy settings Checking Proxy Configuration Checking for winhttp local machine Proxy settings . . . PASS Winhttp local machine access type <Direct Connection> Winhttp local machine Proxy. . . . . . . . . . NONE Winhttp local machine ProxyBypass. . . . . . . NONE Checking User IE Proxy settings . . . . . . . . . . . . PASS User IE Proxy. . . . . . . . . . . . . . . . . NONE User IE ProxyByPass. . . . . . . . . . . . . . NONE User IE AutoConfig URL Proxy . . . . . . . . . NONE User IE AutoDetect AutoDetect not in use Checking Connection to WSUS/SUS Server WUServer = https://<Server>:8531 WUStatusServer = https://<Server>:8531 UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS Connection to server. . . . . . . . . . . . . . . . . . PASS WinHttpDownloadFileToMemory(szURLDest, NULL, 0, NULL, NULL, NULL, &downloadBuffe r) failed with hr=0x80072efd A connection with the server could not be established. Yet I can connect to the server just fine through Internet Explorer. The WindowsUpdate.Log file on the server will contain entries like: 2011-04-17 10:27:23:070 1108 fa8 DnldMgr Error 0x80244019 occurred while downloading update; notifying dependent calls. 2011-04-17 10:27:23:070 1108 d8c AU >>## RESUMED ## AU: Download update [UpdateId = {3E5D82CD-DE97-428C-AB60-AA22B048C083}] 2011-04-17 10:27:23:070 1108 d8c AU # WARNING: Download failed, error = 0x80244019 But I can’t seem to reconcile why these errors appear after searching most of the common reasons for them and coming up dry. Basically, I think WSUS just isn’t working right but I can’t figure out why.

Actually, beyond clearing things out (which I probably shouldn't do), the biggest problem is that updates simply don’t work properly across most of the client computers. Basically, it’s as if WSUS isn’t consistently pushing updates. Sometimes they works but oftentimes they don’t, so it’s not consistent. I’ve investigated all of the things I know to check – communication to the WSUS sever machine (and that seems fine), firewall settings, registry keys, and have run things like the WSUS Client Diag Tool, but I’ve yet to see what causes many of the updates to fail. The Client Diag Tool will report most everything as fine, but will end with a connection problem: WSUS Client Diagnostics Tool Checking Machine State Checking for admin rights to run tool . . . . . . . . . PASS Automatic Updates Service is running. . . . . . . . . . PASS Background Intelligent Transfer Service is running. . . PASS Wuaueng.dll version 7.4.7600.226. . . . . . . . . . . . PASS This version is WSUS 2.0 Checking AU Settings AU Option is 4: Scheduled Install . . . . . . . . . . . PASS Option is from Policy settings Checking Proxy Configuration Checking for winhttp local machine Proxy settings . . . PASS Winhttp local machine access type <Direct Connection> Winhttp local machine Proxy. . . . . . . . . . NONE Winhttp local machine ProxyBypass. . . . . . . NONE Checking User IE Proxy settings . . . . . . . . . . . . PASS User IE Proxy. . . . . . . . . . . . . . . . . NONE User IE ProxyByPass. . . . . . . . . . . . . . NONE User IE AutoConfig URL Proxy . . . . . . . . . NONE User IE AutoDetect AutoDetect not in use Checking Connection to WSUS/SUS Server WUServer = https://<Server>:8531 WUStatusServer = https://<Server>:8531 UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS Connection to server. . . . . . . . . . . . . . . . . . PASS WinHttpDownloadFileToMemory(szURLDest, NULL, 0, NULL, NULL, NULL, &downloadBuffe r) failed with hr=0x80072efd A connection with the server could not be established. Yet I can connect to the server just fine through Internet Explorer. The WindowsUpdate.Log file on the server will contain entries like: 2011-04-17 10:27:23:070 1108 fa8 DnldMgr Error 0x80244019 occurred while downloading update; notifying dependent calls. 2011-04-17 10:27:23:070 1108 d8c AU >>## RESUMED ## AU: Download update [UpdateId = {3E5D82CD-DE97-428C-AB60-AA22B048C083}] 2011-04-17 10:27:23:070 1108 d8c AU # WARNING: Download failed, error = 0x80244019 But I can’t seem to reconcile why these errors appear after searching most of the common reasons for them and coming up dry. Basically, I think WSUS just isn’t working right but I can’t figure out why.

Hi, Thank you for your update. Regarding the error 0x80072efd, please try the methods in the following Knowledge Base article: You may encounter temporary connection-related errors when you use Windows Update or Microsoft Update to install updates http://support.microsoft.com/kb/836941/en-us Regarding the error 0x80244019, please also try: WSUS: Client machines stop getting updates and return HTTP 404 when attempting to download content http://blogs.technet.com/b/sus/archive/2008/06/09/wsus-client-machines-stop-getting-updates-and-return-http-404-when-attempting-to-download-content.aspx Regarding WSUS client related issues, please also refer to the following document: WSUS 3.0 Client Computer Administration Issues http://technet.microsoft.com/en-us/library/cc708443(WS.10).aspx Hope this helps. Thanks. Nicholas Li TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com. Nicholas Li - MSFT Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Regarding the error 0x80244019, please also try: WSUS: Client machines stop getting updates and return HTTP 404 when attempting to download content http://blogs.technet.com/b/sus/archive/2008/06/09/wsus-client-machines-stop-getting-updates-and-return-http-404-when-attempting-to-download-content.aspx I guess the 2nd link you provided might help, but I'm on IIS Version 6.1 on Windows Server 2008 and I've yet to find where Execute Permissions for the Content vroot can be modified to "none" as suggested. Can you guide me where to do that in IIS Manager?

Hi, As far as I know, the version of the IIS which comes with Windows Server 2008 should be 7.0. Regarding the IIS configurations, please refer to the following document: How to: Verify or Correct the IIS Configuration for a Web Site or Virtual Directory http://msdn.microsoft.com/en-us/library/bb909676(v=vs.90).aspx Please see the section “To correct permissions to execute scripts for a virtual directory” under “To verify or change the IIS configuration for a Web site or virtual directory in IIS 7.0”. Hope this helps. Thanks. Nicholas Li TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com. Nicholas Li - MSFT Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

OK, I made a mistake on the version. I'm on IIS version 7.5.7600.16385. But based on that older 2008 post that we're talking about it says that "the Execute Permissions for the Content vroot was set to "Scripts and Executables." The default "Execute Permissions" for this vroot is "None"." and that I should set it to none. If I follow the directions provided, and go to IIS, expand the sites to show WSUS Administration, then go to Content in the tree, and then go to Handler Mappings, I get a long list of states with only 3 enabled: OPTIONSVerbHandler, TRACEVerbHandler, and Static File. If I edit feature permissions it shows only read is enabled and script is not, and execute is even greyed out. Is the recommendation to uncheck read?

Looks like to be an issue with proxy. Please run the following command netsh winhttp show proxy This would tell us under user context if they are using any proxy. Use psexec utility to test the same with localsystem account.Because at the backaround we use localsystem account to authentication. Also check if we really require any proxy settings. Let us know how it goes. As far the last part is concerned "Is the recommendation to uncheck read?" Answer is no, its the default setting and it needs to be checked in.Ketan Thakkar | Microsoft Online Community Support