Hi thereI am working on a site in which I previously deployed SCE SP1 to manage Vista Clients.They are now looking to move to Windows 7.I have upgraded one of the Vista Clients to Windows 7.This client has never had the SCE Agent installed.SCE pushes out to the client agent fine.In the Agent Managed tab, the client health state shows "Not Monitored", there is no OS info either.I have upgraded the WSUS console to SP2, downloaded and installed the relevant Management Packs - the client library and the windows 7 client ones.Software updates (WSUS) seems to bring down updates to the client ok.I have uninstalled/reinstalled the agent. There are no errors in the client event logs.Has anyone an idea of what is wrong?The two certificates are listed in the program files folder also, and it is part of the managed clients AD group.I can connect remotely to the PC in computer management.I am able to carry out a remote assistance to the client also.ThanksNorman

Hello Norman, This problem can be caused by several factors. Make sure these reg keys match your domain name on "not monitored" computers: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\DefaultDomainNameHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Domain. Then, navigate to administration->device management->agent managed and highlight these Not monitored clients. Right click to choose repair it. Stop opsmgr health service and delete the files under folder "\..\System Center Essentials 2007\Health Service State\Health Service Store" and then try to start the health service on these problematic clients. After that, open the SCE console with /clearcache switch. For not yet contacted clients, please check following: 1. Open dsa.msc on server to check whether clients were added in "SCE Managed Computers" group 2. Run rsop.msc on clients to check whether the GPOs: SCE Managed Computers Group Policy& System Center Essentials All Computers Policy had been applied correctly on clients.Check that the client is configured to use the SCE server for Windows Updates. The following registry entries should be set to https://<SCEServerFQDN>:8531HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\windows\WindowsUpdate\WUServerHKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\windows\WindowsUpdate\WUStatusServer3. Run wuauclt /detectnow and reportnow on the SCE agents.4. Check whether the required ports for communication between clients and server had been opened, or disable the firewall as a test. 5. Is there a proxy server in your scenario? If not, please ensure there is no proxy setting in IE and run proxycfg -d command on problematic SCE clients.6. Check the %windir%\windowsupdate.log to see if any error prompt.You also can go to operations manager section of event viewer to see if anything is amiss which would indicate the problem.You can refer to these threads as well:http://social.technet.microsoft.com/forums/en-US/systemcenter/thread/8fe7cdbb-f3ce-4200-ac67-938cccf05eee/http://social.technet.microsoft.com/forums/en-US/systemcenter/thread/1216eb14-ed73-4517-b95f-5305274e0f07/Thanks, AnshuThis posting is provided "AS IS" with no warranties, and confers no rights.

Hi againNone of these steps fixed the problem.I deployed a Vista Client and the same thing is happening, so hence it must be to do with the SCE server itself.Last week, we had a problem with that server and it had to be removed and joined back on the domain again.In event manager under the Operations Manager log, there are event 2115 errors every 5 or so seconds.The error is "A Bind Source in Management Group HQRSCM01_MG has posted items to the workflow, but has not received a response in 403560 seconds.This relates to things like Microsoft.SystemCenter.CollectAlerts and Microsoft.Systemcenter.DataWarehouse.CollectEventsData.Given this, what I think has happened is the server is not talking to the Remote SQL Instance properly, probably permissions due to the server being taken off the domain and put back on.The client agent is reporting in the status to the server but it is not getting written to the database. Question is how do I fix this? I know it is to do with the Run As Profiles, but don't know the fix.ThanksNorman

I have fixed this!I fixed this by reseting the SQL Run As accounts.Even though they had the correct server listed, by removing it and then adding them in again fixed the problem.I assume it was down to the re-added server being a different computer account. It must hold the SID and not the FQDN for security reasons?

Hello,Thanks for sharing the information. It is very helpful for other community members facing similar problems.Thanks,Yog Li - MSFT

I have fixed this! I fixed this by reseting the SQL Run As accounts. Even though they had the correct server listed, by removing it and then adding them in again fixed the problem. I assume it was down to the re-added server being a different computer account. It must hold the SID and not the FQDN for security reasons? I dont understand how to do this since I have similar issues in SCE2007 SP1 with WSUS SP2. Win7 clients dont report back and newly added WinXP clients too. Can someone be so kind and guide me throught step-by-step. Thanx.

Hello??? some there to help me -> check my post above.