Using Client Status Reporting to Monitor Client Status
Client status reporting in Configuration Manager 2007 R2 provides up-to-date information on the manageability of clients in a Configuration Manager 2007 hierarchy. This information can be used by the site administrator to identify individual client problems and to maintain a more accurate site database. It can also help to increase software distribution success rates.
Client status reporting in Configuration Manager 2007 R2 provides the following improvements over existing methods for diagnosing the status of Configuration Manager 2007 clients:
- Identifies clients that are online but are not requesting policy.
- Provides a number of reports that detail the status of clients on your site.
- Identifies clients that are online but have nonfunctioning client components.
- Identifies clients that are online but do not have up-to-date discovery or inventory records.
- Identifies clients that are offline.
- Is not dependent on Configuration Manager 2007 site systems. For example, client status reporting will not be affected by problems with backlogged site systems which could cause traditional reporting mechanisms to generate inaccurate results.
- Uses a number of data sources for its analysis, including data from the Configuration Manager 2007 site database, such as inventory, discovery, and heartbeat data. Additionally, client status reporting components gather and analyze policy request log files from management points, and can also check the status and activity of Configuration Manager 2007 client components.
This post is to provide an insight on Client Status Reporting tool that can be used to provide up-to-date Information on the status of client computers in Configuration Manager 2007 hierarchy.
A number of methods exist in Configuration manager 2007 R2 that can assist you in monitoring the status of client computers on your CM 2007 R2 site. These methods are largely based on the data of the latest discovery and inventory data received from the client.By using CSR tool to identify individual client problems and to maintain a more accurate site database. It can also help to increase software distribution success rates.
Select “Client Status Reporting” from the main installation wizard under the “Additional Content” section. You can also browse to the “Client Status Reporting” folder on the CD as the install will take you there anyways.
Launch the “Clientstatusreporting” MSI.
Select “I accept the license agreement” and select “Next”.
Select the destination folder and select “Next”.
Select “Next” to start the installation.
You will have a new menu option in the Start menu. Launch the “Configure Client Status Reporting” to finalize the installation.
On the “Site Settings” tab, you will need to configure the SQL server and instance, along with what account you want the Client Status reporting to run under. I typically will configure it to use the local system account.
On the Options tab, you will want to select the “Update Configuration Manager 2007 site database with inactive client information”, you will also want to configure the client activity periods for your environment.
On the Schedule tab, you will want to enable the Client pulse settings along with the Client ping settings. You will also want to configure the schedules for those settings.
8. Importing the Client Status reports into Configuration Manager
Select “Import Objects” on the Reporting node.
Browse to the path you see below. Then select “Open”.
After the reports have been imported, you can see them listed in the reports folder or
Bottom of Form
After the reports have been imported you can see them listed in Report viewer link
You will get More information about Client status reporting tool in Microsoft TechNet Library http://technet.microsoft.com/en-us/library/cc161956.aspx