Topic last updated—January 2008
Microsoft Forefront Client Security provides unified virus and spyware protection for business desktops, laptops, and server operating systems. You can use desired configuration management to monitor the Client Security agent on clients managed by Microsoft System Center Configuration Manager 2007 R2 sites.
.gif) Note |
|
The information in this topic applies only to Configuration Manager 2007 R2. |
To monitor the Client Security agent, you import the configuration pack included on the Configuration Manager 2007 R2 CD, assign the baseline to a collection that contains computers running the Client Security agent, and then monitor the compliance evaluation reports as you would for any other configuration baseline. No additional installation or configuration is needed.
Configuration Manager 2007 does not actually report back about malware or viruses detected; those alerts are monitored by Client Security as long as the Client Security agent is operating correctly.
Monitoring the Client Security Agent
This scenario demonstrates how customers can compare the configuration of their Client Security agent against best practices specified in the Microsoft System Center Configuration Manager 2007 Forefront Client Security Configuration Pack and can detect a potentially detrimental configuration before it negatively affects service level agreements (SLAs).
A. Datum Corporation has deployed Client Security as its antivirus and antispyware solution. Although the Client Security agent is quite reliable, Ellen Adams, a security administrator, wants to know if any clients are not actively using Client Security. Ellen has the goal of obtaining 99.5% compliance with Client Security configuration on all computers running the Client Security agent. Users who disable the Client Security agent might be subject to disciplinary action under the company security policy.
Tommy Hartono, the Configuration Manager administrator, learned that Microsoft published a configuration pack for Client Security in Configuration Manager 2007 R2 that can be applied with desired configuration management in Configuration Manager 2007. They decide to follow the course of action in the following table.
Three months later, as a possible result of the desired configuration management implementation described in the preceding scenario, Ellen confirms that 99.99% of the clients in the organization are running Client Security and that they have sufficient uptime to reduce the risks posed by viruses and malware.
See Also
Did you find this information useful? Please click the following link to send your suggestions and comments about the documentation to the Configuration Manager Doc Feedback alias: