OK, I have searched through about 18 pages of posts and didn't find the answer to this one but I apologize if I missed it. I have one client that will not update and its' status is unknown on the server. I checked the WindowsUpdate.log and a section is listed below: 2007-08-2810:17:14-07001092870Successfully opened event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{B34B46CF-7EE6-4FF5-8AFE-220208F2BEF5}.bin for reading.2007-08-2810:17:14-07003320ce8Trying to make out of proc datastore active2007-08-2810:17:15-07003320ce8Out of proc datastore is now active2007-08-2810:17:15-07001092870PT: Using serverID {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}2007-08-2810:17:15-07001092870Failed to obtain cached cookie with hr = 80248008.2007-08-2810:17:15-07001092870Failed to upload events with hr = 80248008.2007-08-2810:17:28-070010924d8AU received event of 12007-08-2810:17:28-070010924d8WU client succeeds CClientCallRecorder::BeginFindUpdates from AutomaticUpdates with call id {889E5B24-4C67-4CA6-B44D-9C4A557A64C2}2007-08-2810:17:28-07001092484WU client executing call {889E5B24-4C67-4CA6-B44D-9C4A557A64C2} of type Search Call2007-08-2810:17:29-07001092484Send failed with hr = 80072efd.2007-08-2810:17:29-07001092484SendRequest failed with hr = 80072efd. Proxy List used: <(null)> Bypass List used : <(null)>2007-08-2810:17:30-07001092484Send failed with hr = 80072efd.2007-08-2810:17:30-07001092484SendRequest failed with hr = 80072efd. Proxy List used: <(null)> Bypass List used : <(null)>2007-08-2810:17:31-07001092484Send failed with hr = 80072efd.2007-08-2810:17:31-07001092484SendRequest failed with hr = 80072efd. Proxy List used: <(null)> Bypass List used : <(null)>2007-08-2810:17:32-07001092484Send failed with hr = 80072efd.2007-08-2810:17:32-07001092484SendRequest failed with hr = 80072efd. Proxy List used: <(null)> Bypass List used : <(null)>2007-08-2810:17:32-07001092484DownloadFileInternal failed for https://sdisce.systron.com:8531/SelfUpdate/wuident.cab: error 0x80072efd2007-08-2810:17:32-07001092484IsUpdateRequired failed with error 0x80072efd2007-08-2810:17:32-07001092484PT: Using serverID {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}2007-08-2810:17:32-07001092484WU client failed Searching for update with error 0x802480082007-08-2810:17:32-07001092484Search Callback Failed, hr is 0x802480082007-08-2810:17:32-07001092484Setting next AU detection timeout to 2007-08-28 18:11:272007-08-2810:17:32-07001092484Setting AU scheduled install time to 2007-08-29 10:00:002007-08-2810:17:32-07001092484WU client calls back to search call AutomaticUpdates with code Call failed and error 0x80248008 2007-08-2810:17:32-07001092484WU client completed and deleted call {889E5B24-4C67-4CA6-B44D-9C4A557A64C2}2007-08-2810:17:37-07001092454REPORT EVENT: {C8B7D7E3-C0A7-4FFF-8C30-F57673D899E8}252007-08-28 10:17:32-07001148101{D67661EB-2423-451D-BF5D-13199E37DF28}080072efdSelfUpdateFailureSoftware SynchronizationError: Agent failed detecting with reason: 0x80072efd2007-08-2810:17:37-07001092454REPORT EVENT: {2A50F890-78C0-4C9B-A63F-DEB7E95239F9}262007-08-28 10:17:32-07001148101{00000000-0000-0000-0000-000000000000}080248008AutomaticUpdatesFailureSoftware SynchronizationError: Agent failed detecting with reason: 0x802480082007-08-2810:17:37-07001092454Created new event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{C9EBF717-BC98-4E61-8B78-D8CBA70D2E92}.bin for writing.2007-08-2810:22:32-07003320ce8Out of proc datastore is shutting down2007-08-2810:22:33-07003320ce8Out of proc datastore is now inactive2007-08-2810:27:15-07001092484Successfully opened event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{B34B46CF-7EE6-4FF5-8AFE-220208F2BEF5}.bin for reading.2007-08-2810:27:15-0700 576808Trying to make out of proc datastore active2007-08-2810:27:16-0700 576808Out of proc datastore is now active2007-08-2810:27:16-07001092484PT: Using serverID {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}2007-08-2810:27:16-07001092484Failed to obtain cached cookie with hr = 80248008.2007-08-2810:27:16-07001092484Failed to upload events with hr = 80248008.2007-08-2810:27:47-07001092448Service received connect notification2007-08-2810:27:47-070010924d8AU received event of 32007-08-2810:27:53-07001092448Service received disconnect notification2007-08-2810:27:53-070010924d8AU received event of 32007-08-2810:27:55-07001092448Service received connect notification2007-08-2810:27:55-070010924d8AU received event of 32007-08-2810:27:55-07001092448Service received logon notification2007-08-2810:27:55-070010924d8AU received event of 3 Can anyone help me determine why the client keeps failing to contact the SCE server? BTW, I have run gpupdate/force and wuauclt/detectnow several times. This is a brand new build of a client machine and it has been on for 2 days. All other clients in this OU are working fine. Thanks in advance.

Hi Hawkeye - This is a simple one, maybe you have tried it. 1. Stop the Automatic Updates service. 2. Delete the contents of the C:\Windows\SoftwareDistribution folder. 3. Restart the Automatic Updates service. 4. Wait about two minutes, then run wuauclt.exe /detectnow. I have found this to be asafe procedure to 'hard reset' a WSUS client. / JJ

Nope, pretty much the same error codes (80072efd, 80070057, and 80248008).

So...It sounds like you may be having issues withyour proxy server. Please try the following on your client machine andpost back the results: Try to navigate tohttps://<FQDNNameOfYourSCEServer>:8531/simpleauthwebservice/simpleauth.asmx (make sure you replace the <FQDNNameOfYourSCEServer> with the name of your SCE Server). If you do not see a page with ping and getauthorizationcookie displayed then yourproxy server settings arethe root cause of this issue. Please post any errors you get while following these steps and we will help you resolve the issues. Thanks

This works just fine (going to the web page) and I get two options, ping and getauthorizationcookie. We are not using a proxy and there are no settings in the IE for proxies. What about computer names? The name of this PC is XX-XXXXX format, could that cause a name resolution issue with SCE?

Hi, From the error log, I found a error prompt with DownloadFileInternal failed for https://sdisce.systron.com:8531/SelfUpdate/wuident.cab: error 0x80072efd. It sound like maybe it is caused by connection between SCE server and that problematic client at some points. If the proxy is not the case, Please try following steps: 1. Run gpupdate /force command on the SCE server and check the HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate registry key to verify that the following settings are there: WUServer https://<SCEServer>:8531 WUStatusServer - https://<SCEServer>:8531AcceptTrustedPublisherCerts 1 2. Verify if the client can connect to the shares and sites to the WSUS server. 3. Type the following commands. Press ENTER after each command. Proxycfg -uproxycfg -dnet stop wuauservnet start wuauserv 4. Log on the problematic client. Use IE and go to https://<FQNDNameOfSCEServer>:8531/selfupdate/wuident.cab. Please ensure it has a File download prompt. 5. Open the SCE console and go to Administrator->Device Management->Agent Managed to find that problematic client. Right click the client and select repair. After that, if the problem still remain, please perform following points: Download the AU Client Reset troubleshooting tool to resolve some common issue. The link is following: Ftp server: https://sftasia.one.microsoft.com/choosetransfer.aspx?key=3c27aabb-81c2-49f0-bcfc-7e7ab4e5d136 Password: 7#MQgy]lF8j%vQ Tool Usage: 1) Launch the AU Client Reset tool by double clicking it on the problematic client.2) Follow the onscreen prompts for details on what is happening3) Once the tool completes please restart the computer. 4) Run "wuauclt /detectnow" to see if it works. More Information: If the problem remains, please send me the following data to the scedata@microsoft.com and copy the highlight lines in the email body:- All .txt files that were generated in the %systemdrive%\AULOGS Folder - WindowsUpdate.log (no space in name): Under your Windows Folder SCE server not reporting in to itself http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2021491&SiteID=17 Jie-Feng Ren MSFT Hope it helps. --------------------- Regards, Jie-Feng Ren Microsoft Online Community Support

What I actually ended up doing was to remove the monitoring agent from the PC, then change the GPO for the PC in question (actually put the PC in question into a different OU) that was still using the old WSUS 3 server and running updates from there. Once the PC was completely updated, I switched it back to the other OU, re-installed the agent, then performed a gpupdate/force and wuauclt/detectnow on the PC. This got me almost all the way there. After all this, it was still reporting an error in the windowsupdate.log and had several "invalidcookie" errors for each time it tried to update. I went to Internet explorer on the client and cleared the cookies, temporary internet files,and tried again, all went well after this. I'm not sure why this happened on this particular machine and why the old WSUS was able to perform updates but it seems to be responding now for about a 24 hour period so I will consider this a success. Thanks again for your help and hope this helps others.

Hey all, may I have a copy of the AU client reset tool? I've got a agent computer (XP) with all the same issues shown here, and I've been through all the normal channels shown above with zero success. Cheers, Pete

Hi Pete, Please download the AU_client from following link: FTP ADDRESS: https://sftus.one.microsoft.com/choosetransfer.aspx?key=bda82f1a-de00-4472-ab31-32f14e821e53 Password: uyh_-E5N8dDQ@vpv

I had exactly the same symptoms,alsoon a new build. Same messages in the windowsupdate.log too. Reading the above post reminded me that I had had this problem once before then I remembered that on that occasion Microsoft KB had suggested that the WSUS client agentneeded to be updated but could not do so from an updated WSUS server. The solution was to move the client computer from its active directory OUspecifying a local WSUS serverto an OU which allows the client to update directly from the Microsoft Windows Update server. This I did, and after the client updated itself directly from Microsoft I was able to move it back to the intended OU without further problems. Simple really. In the end. Only wasted a full day trying to work out what the problem was! So people, with new builds you might want to have the client update with Microsoft first, before moving the computer into your own WSUS environment. Anyway, thanks for the post, it did help.

We are have the same issue. I have tried both the above links and passwords for downloading the AU Client resest tool but with no success. Would you repost the link and a new password please?Thank you!

Hi,Likewise, I have tried a lot of the suggestions from the postings but still not having any luck updating the clients that are not reprting to WSUS server.Can you please post the link for the AU Client reset tool. Thank you

Just a question about this:https://<FQNDNameOfSCEServer>:8531/selfupdate/wuident.cabIs it nessecarry to have GPO with FQDN of the server, can we use ip address instead.Something like thishttps://<10.17.123.5>:8531/selfupdate/wuident.cab