About Reports for Configuration Manager Clients
Applies To: System Center Configuration Manager 2007, System Center Configuration Manager 2007 R2, System Center Configuration Manager 2007 R3, System Center Configuration Manager 2007 SP1, System Center Configuration Manager 2007 SP2
The following reports in Configuration Manager 2007 help you manage and troubleshoot clients in the Configuration Manager 2007 hierarchy. They have the report category of Site - Client Information.
For more general information about using reports, see Reporting in Configuration Manager.
Client Deployment and Assignment Reports
The following reports help you track and monitor client deployment for both Configuration Manager 2007 clients and SMS 2003 clients, and do not require that clients are assigned a fallback status point:
Computers Assigned but not installed for a particular site
Computers with a specific SMS client version
Count clients assigned and installed for each site
Count clients for each site
Count SMS client versions
The following reports help you track and monitor client deployment for Configuration Manager 2007 clients only, and require that these clients are assigned a fallback status point:
Client Assignment Detailed Status Report
Client Assignment Failure Details
Client Assignment Status Details
Client Assignment Success Details
Client Deployment Failure Report
Client Deployment Status Details
Client Deployment Success Report
Client Communication Reports
The following reports help you to identify client communication problems, for example if a client cannot communicate with its management point because of certificate problems.
These reports apply to Configuration Manager 2007 clients only, and require that these clients are assigned a fallback status point:
Issues by incidence detail report for a specific collection
Issues by incidence summary report for a specific collection
Issues by incidence detail report for a specific site
Issues by incidence summary report
Configuration Manager 2007 reports that require a fallback status point will only display data from computers that have commenced client installation and reported state messages to the fallback status point. Data from the fallback status point might take some time to reach the Configuration Manager 2007 site server if you are deploying the client to a large number of computers. For more information, see Determine If You Need to Configure Throttle Settings for the Fallback Status Point in Configuration Manager.
Client Mode Reports
These reports help you to manage clients for when sites are configured for native mode, which requires public key infrastructure (PKI) certificates for all clients, and specific site systems. For more information about native mode, see Configuration Manager Site Modes.
Use the following report when you are migrating sites from mixed mode to native mode, to help you identify which clients have successfully switched their site mode configuration so that they can communicate with their native mode site:
- Summary information of clients in native mode
The following reports help you to determine if clients are ready to be migrated to native mode, but require that the Configuration Manager Native Mode Readiness Tool is first run on Configuration Manager 2007 clients. For more information, see How to Determine Whether Client Computers Are Ready for Native Mode:
Clients incapable of native mode
Summary information of clients capable of native mode
To incorporate these reports into the procedures for migrating a site to native mode, see Administrator Checklist: Migrating a Site to Native Mode.
How to Assign the Fallback Status Point to Configuration Manager Client Computers
How to Create a Fallback Status Point in Configuration Manager
How to Migrate the Site Mode from Mixed Mode to Native Mode
For additional information, see Configuration Manager 2007 Information and Support.
To contact the documentation team, email SMSdocs@microsoft.com.