Topic Last Updated—August 2008

The following considerations should be taken into account when installing the Configuration Manager 2007 R2 client status reporting feature:

Note
The information in this topic applies only to Configuration Manager 2007 R2 and Configuration Manager 2007 R3.

Deployment Scope

Only one SQL server and one Configuration Manager 2007 site database can be specified for each installed instance of client status reporting. Only one instance of client status reporting can be installed on a computer.

Client Status Reporting Host System

The client status reporting host system is the computer on which you install client status reporting. Consider the following when designating the client status reporting host computer:

  • You can install client status reporting on any Configuration Manager 2007 site system. However, this is not a requirement. You can also install client status reporting on any server or workstation with network connectivity to your Configuration Manager 2007 site.

    Note
    For performance reasons, Microsoft recommends installing client status reporting on a server other than the server hosting the Configuration Manager 2007 site database.
  • It is recommended that the client status reporting host system be located in close proximity on the network to the site server of the monitored site.

  • If you want to monitor the status of client computers in a Configuration Manager 2007 secondary site, you must configure client status reporting to report to the database of the parent site.

  • Client status reporting might use considerable computer resources on the client status reporting host system. For this reason, it is recommended that you do not install client status reporting on a computer that is running other resource intensive applications.

  • The Client Status Reporting Service Account requires administrator privileges and the "logon as a service" right on the client status reporting host system computer.

  • To be able to query the Configuration Manager 2007 client service on client computers by using client ping, the Client Status Reporting Service Account must have administrator permissions on the client computers.

Network Bandwidth

If you have slow network connections between Configuration Manager 2007 sites in your hierarchy, the available bandwidth might not be sufficient to support using client ping and collecting policy request log files. In this case, consider installing an instance of client status reporting at each primary site in your hierarchy.

Note
Client status reporting does not consolidate reports for multiple instances of the feature.

See Also