Manage Configuration Manager clients - Managing Enterprise Devices and Apps - page 259

Verification method Description

Client logs You can use several log files to verify client installation. Examples include:

■

CCMSetup.log This log records setup tasks that CCMSetup.exe per-
forms. You use this log to help troubleshoot client installation problems.
CCMSetup.log is stored at %Windir%\CCMSetup\Logs.

Client.msi.log This log records setup tasks that Client.msi performs.
You use this log to help troubleshoot client installation problems. Client
.msi.log is stored at %Windir%\CCMSetup\Logs.

■

ClientLocation.log This log records site assignment tasks. You use
this log to help troubleshoot when the client is not assigned to a
Configuration Manager site. ClientLocation.log is stored at %Windir%
\CCM\Logs.

■

ClientIDManagerStartup.log This log records when the client has
registered in the site successfully. No other client processes will com-
plete until after registration of the client. This log is stored at %Windir%
\CCM\Logs.

■

DataTransferService.log This log records all BITS communication for
policy or package access. You should check this log when troubleshoot-
ing components that cannot download. This log is stored at %Windir%
\CCM\Logs.

■

PolicyAgent.log This log records policies by using the Data Transfer
service. You should check this log when troubleshooting the policy that
cannot update. This log is stored at %Windir%\CCM\Logs.

■

Client status
The System Center 2012 R2 Configuration Manager client agent runs a scheduled task to
evaluate its client health status. The health status of a client enables you to determine the
answers to the following questions:
■ How many clients are healthy in the hierarchy?
■ How many clients are inactive in the hierarchy because they have been powered off for
a long time or because the Configuration Manager client agent is not installed?
■ What is the main cause of unhealthy clients in the hierarchy?
The task runs daily between midnight and 1:00 A.M. by default. Then, the client sends the
evaluation results to a management point as a status message. Similar to the initial installa-
tion process, if the client fails to send its status message to a management point, it will then
send the status message to a fallback status point if one exists in your hierarchy. If you have
not installed a fallback status point in your hierarchy, the site server might not receive some
evaluation results. The site server summarizes the evaluation results and activities of the cli-
ent's health and then displays them in the Configuration Manager console in the Client Status
folder located in the Monitoring workspace.