Hello, I am a beginner to SCCM as I have only just decided to use ForeFront as out AV solution. I have followed a few guides on getting this all up and running and everyhting seemed to work for a few weeks on about a dozen machines I installed the SCCM client on. However now all my clients are showing up as inactive desptie them being used on a daily basis.  I cannot find the reason why clients are showing up as inactive so any help would be appreciated.

• Moved by Stan White [MSFT]Microsoft employee, Moderator Wednesday, May 02, 2012 6:14 PM Moving to category that matches more closely (From:Configuration Manager 2012 - General)

Have you changed something on the Boundaries, or in the AD Subnets, which could be used as Boundaries?

• Proposed as answer by JeffKuhne Sunday, April 07, 2013 1:04 AM

Nothing has changed in terms of our network it has all been the same since I started using SCCM

Check, on a client, the ClientLocation.log and ClientIDManagerStartup.log if there are any error, which the clients prevent to connect to the MP.

Is the MP working at all? Any errors on the Monitoring node (site status)? Any errors in mpcontrol.log?

Is this SCCM 2012 or 2007? Sounds like it may be 2007.

There are no indications of errors or faults in the logs and it is 2012

So this is a brand new install or a 2007 to 2012 migration?

It has been built from scratch as a 2012 installation.

Initiate a discovery data cycle and hardware inventory cycle on the client and see if the records make it to the database (properties of a resource and resource explorer).

How can I push that from the server?

The ConfigMgr 2012 toolkit contains sendsched.exe: http://www.microsoft.com/en-us/download/details.aspx?id=29265

Have you checked the info from Client Activity Detail tab?

This gives you a good idea when is the last time when the client has contacted. By default, the client requests a new policy every 60 min, sends a heartbeat DDR every 7 days, and reports hw/sw inventory every 7 days.

On the client, check the following log files (%windir%\ccm\logs):

- Inventory log: should have information about heartbeat DDR, hw/sw inventory)

- PolicyEvaluator.log should give you information when a new policy has been applied or you see that no changes are necessary

This gives you more information, it doesn't fix your problem! :-)

Panu

On the client activity Detail Tab I have:

Policy Request : 11/04/2012

Heartbeat DDR: 05/042012

Hardware Scan: 05/04/2012

It is not clear to me why they are so old and the client is not talking to the server any more and has not done so for quite a long time

Now you need to figure out what has happend on 11/04.

You could start doing basic troubleshooting:

Let's assume that you have the site server & MP & SQL Server running on the same box.

Check that the following services are running on your server:

• SQL Server
• SMS Excectutive
• SMS Site Component Server
• SMS Agent Host (MP role)

Some of those services might have been stopped or if you have restarted the server, some service might failed to start (this is quite rare).

On your site server, go to ConfigMgr_installation_directory\logs. Check

Can you contact your site server from your clients? You might have a network/name resulution issue.

There are a lot of potential issues!

Panu

You guys throw us Americans off with those date formats. LOL. 11/4/2012 isn't here yet. JK

Check CcmMessaging.log on a client and verify no errors are being reported.

Hello!

I have found this in the techet libary:

http://technet.microsoft.com/en-us/library/gg682132.aspx

Client Activity: You can configure thresholds to determine if a client is active, for example:

• Whether the client requested policy during the last seven days.
• Whether Heartbeat Discovery found the client during the last seven days.
• Whether the client sent hardware inventory during the last seven days.

When all these thresholds are exceeded, the client is determined to be inactive.

Maybe this will help you out to solve your problem.

Brgds.

Tamas

• Marked as answer by Stan White [MSFT]Microsoft employee, Moderator Monday, May 14, 2012 8:38 PM

If I may hijack this thread, all of my clients have stopped working too and I am getting these errors in CcmMessaging.log:

[CCMHTTP] ERROR: URL=http://BEIJING.heathfieldstmarys.net/ccm_system/request, Port=80, Options=224, Code=0, Text=CCM_E_BAD_HTTP_STATUS_CODE

In order to get the SCCM server working properly I did have to uninstall and reinstall IIS and I wonder if it's related (all the clients were deployed before these changes).  Have I got something missing at the server end with IIS or do my clients now have the incorrect settings?

If I may hijack this thread, all of my clients have stopped working too and I am getting these errors in CcmMessaging.log:

[CCMHTTP] ERROR: URL=http://BEIJING.heathfieldstmarys.net/ccm_system/request, Port=80, Options=224, Code=0, Text=CCM_E_BAD_HTTP_STATUS_CODE

In order to get the SCCM server working properly I did have to uninstall and reinstall IIS and I wonder if it's related (all the clients were deployed before these changes).  Have I got something missing at the server end with IIS or do my clients now have the incorrect settings?

Are you saying you reinstalled IIS after you had the roles installed? That most likely broke the management point, uninstall the MP then reinstall it. Once that has comepleted test it using the MP troubleshooter from the ConfigMgr toolkit or simply by using mplist and mpcert. You could have other roles broken on the server as well. If that fixes the MP I'd probably reinstall all the roles that use IIS on that server.

Morning,
I'm facing the same problem of having all my clients inactive, and not detecting new clients, the only change that i have done is changing the root domain controller admin p/w.
I took the responsibility of SCCM after one person who left our company, so i was enforced to change the root admin p/w,
I have nearly zero knowledge in SCCM,
I dont know if you can help me here where to dig

Morning,
I'm facing the same problem of having all my clients inactive, and not detecting new clients, the only change that i have done is changing the root domain controller admin p/w.
I took the responsibility of SCCM after one person who left our company, so i was enforced to change the root admin p/w,
I have nearly zero knowledge in SCCM,
I dont know if you can help me here where to dig

I strongly suggest you start a new post. You will get much more help that way.