Hi, In SCE 2010, computers status are ok but servers (2003 sp2 and 2008 r2) show "Warning" as Agent Status. Reasons: "The computer did not connect to the SCE Server in last 10 days" "The computer is not configured to use the Essentials update server..." I tried the following resolution steps: 1. Reboot the server 2. Check the %windir%\WindowsUpdate.log -> The only warning is "WARNING: Cached cookie has expired or new PID is available" -> The SCE server is contacted (Reporter successfully uploaded 4 events). 3. Checked gpresult - SCE policy is applied, servers are members of SCE group and Computer Configuration\Administrative Settings\Windows Components\Windows Update\Specify intranet Microsoft updates location points to https://mysceserver.fqdn:8531 . 4. Repair agent (repair successful) ...But the servers agents are still in "warning state" with the same errors ! Any idea ? Thank you for your help

flush the health status from one of the servers effected and see if the warning state comes back. You perform this from the monitoring pane under discovered inventory.Ok, so I changed my name...you can still call me Tom if you like. It's a...jump...to conclusions...mat. My Blog Site: http://tmagnuson.wordpress.com

The "Recalculate health" task never ends and the "reset health" doesn't change the warning status...

you want to the flush the machine state, don't do it within the health explorer. I don't know why but I seem to get better results. Again, in the monitoring pane, then go to Discovered Inventory. Find the server in question, highlight it, and then the list of actions on the right side of the screen select "Flush Heath Service State and Cache"Ok, so I changed my name...you can still call me Tom if you like. It's a...jump...to conclusions...mat. My Blog Site: http://tmagnuson.wordpress.com

There's no "Flush Health.." action. Under Monitoring->Discovered Inventory (server highlighted) -> Task Pane -> State Actions there's only "Change Target Type...", "Health Explorer" and "Start Maintenance Mode.."

Hi, You can also try the following steps to “Flush Health Service State and Cache”: On the problematic servers: 1. Stop System Center Management service. 2. Go to C:\Program Files\System Center Essentials\, and rename the “Health Service State” folder. 3. Restart System Center Management service. Regarding this issue, please also try the methods in the following articles: 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 A Windows 2000-based, Windows Server 2003-based, or Windows XP-based computer that was set up by using a Windows 2000, Windows Server 2003, or Windows XP image does not appear in the WSUS console http://support.microsoft.com/kb/903262 Hope this helps. Thanks. 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.

Hi, You can also try the following steps to “Flush Health Service State and Cache”: On the problematic servers: 1. Stop System Center Management service. 2. Go to C:\Program Files\System Center Essentials\, and rename the “Health Service State” folder. 3. Restart System Center Management service. Regarding this issue, please also try the methods in the following articles: 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 A Windows 2000-based, Windows Server 2003-based, or Windows XP-based computer that was set up by using a Windows 2000, Windows Server 2003, or Windows XP image does not appear in the WSUS console http://support.microsoft.com/kb/903262 Hope this helps. Thanks. 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.

Hi, Thank you for your help but after "flushing health service state and cache" (your 3 steps above), the problem is still there. Following your links, I checked wu reg value and update log. Both are ok on the servers. And I checked the SusClientId : the value is not the same on each server. Any other idea ?

Ok, I know you already looked at this, but look again. The values for hklm\software\policies\microsoft\windows\windowsupdate\wuserver and hklm\software\microsoft\system center essentials\2.0\policysettings\sceserver have to be the EXACT same. I just had this problem with one of my windows 7 clients and the only difference between a working pc and a pc reporting this error was the one entry was correct, the other had just the shortname of the server and not the FQDN. I had to look at this 3 times before I really caught it on my system. so what you need to see is: "WUServer" under hklm\software\policies\microsoft\windows\windowsupdate -> https://yoursceserver.domain.org:8531 (usually this one) OR http://yoursceserver.domain.org:8530 "SCEServer" under hklm\software\microsoft\system center essentials\2.0\policysettings -> yoursceserver.domain.org Compare these entries to clients that are working and see what the difference is. This has happened before, see here: http://social.technet.microsoft.com/Forums/en/systemcenteressentials/thread/1ed91c34-1426-4962-b148-a5bf88bf03ee Ok, so I changed my name...you can still call me Tom if you like. It's a...jump...to conclusions...mat. My Blog Site: http://tmagnuson.wordpress.com