Troubleshooting issues where clients are not reporting

re: Troubleshooting issues where clients are not reporting

Devidas Nainwad — Fri, 01 Jul 2011 10:02:01 GMT

If an still issue policy downloading please check secondary site server services Ex:-SMS Executive service and try to resatrt service once restart service issue will be resolve.

re: Troubleshooting issues where clients are not reporting

Amit — Wed, 29 Jun 2011 09:18:18 GMT

I have deployed sccm and forefront but atomatic approval rule is not working from wsus

re: Troubleshooting issues where clients are not reporting

Prashant Patil — Thu, 09 Jun 2011 17:41:34 GMT

Hi Sudheesh, Nice to see you here. Currently I a facing problem with Windows 7 & XP client system. Configure settings & Discover button is not highlighted (grayed out).

Please suggest

re: Troubleshooting issues where clients are not reporting

Sudheesh N — Mon, 07 Mar 2011 03:22:33 GMT

Client Assigned No is Boundaries issue and if you dont have the prequist for client installation you wont have the client installed.

Probably this should help you

blogs.technet.com/.../troubleshooting-sccm-part-i-client-push-installation.aspx

re: Troubleshooting issues where clients are not reporting

Anandh Kandasamy — Thu, 17 Feb 2011 09:23:52 GMT

We have SMS 2003 environment , nearly 900 machines not assigned to site as well as client status "no".We tried to remote that machines getting RPC not avilable.Also we tried righ click collection and given "Install Client" was not working.

Can you help me to sort out this issue?

Thanks in advance !!

Thanks,

Anandh Kandasamy

anandhkandasamy@gmail.com

re: Troubleshooting issues where clients are not reporting

Sudheesh N — Tue, 11 Aug 2009 04:44:38 GMT

I would say in this case we need to find out why the WMI is getting corrupted. We can use the WMI diag for the same before rebuilding the WMI.In my case i have was able to get rid of WMI issues with the rebuild. Also you can check

933062 A hotfix is available that improves the stability of the Windows Management Instrumentation repository in Windows XP (Included in WinXP SP3)

http://support.microsoft.com/default.aspx?scid=kb;EN-US;933062

re: Troubleshooting issues where clients are not reporting

Christoph Voigt — Tue, 11 Aug 2009 00:14:40 GMT

Thanks for the great summary Sudheesh. Very often we encounter clients that have been installed somewhere in 2006/7 which are not able to communicate with the server. In most cases however, the WMI repository of the client is completely fubar and the SMS client can't be repaired.

8 out of 10 times repairing WMI does not help and we have to do a completely new OS install to "fix" the system and the remaining 2 out of 10 usually come back a few weeks/months later with new errors too.

I'd love to see what your approach to a solution would be in such a case. To answer the most obvious question first: no, our users do not have administrative rights on their clients ;) Usually it's a XP SP2 wim that has been updated to SP3 via SMS and updates via WSUS