|
Search Microsoft.com for: |
Microsoft Systems Management Server 2003 Desired Configuration MonitoringPublished: November 15, 2005 Microsoft Systems Management Server (SMS) 2003 Desired Configuration Monitoring (DCM) is a powerful solution to maintain a consistent configuration across all server roles and hardware types and ensure that all servers have required software updates, service packs and drivers installed. This solution requires Windows Server 2003 or Windows XP for component installation and will monitor most Microsoft Windows Server System applications and hardware configurations. The solution runs on any server application where configurations can be accessed through Microsoft Active Directory, Window Management Instrumentation, metabase, file system, and registries. View the Solution Documentation
Download the Complete Solution DCM helps you to reduce unplanned service downtime, correlate configuration data, reduce support costs, and increase end-user satisfaction. It provides you with an easy-to-use XML editing tool and guidance for defining Desired Configuration Models. DCM provides detailed compliance reports to assist with detection and remediation of configuration errors. Figure 1 gives an overview of how DCM works. Figure 1: How SMS 2003 Desired Configuration Monitoring works You begin by defining a Desired Configuration Model for each server role and hardware type. A sample model is included in the solution and further sample models will be released on the Microsoft Download Center. When you're defining the models, you specify the desired values in Windows Management Instrumentation (WMI), the system registry, the Internet Information Services metabase, Active Directory directory service, and the Windows File System (WFS). After you have defined all of the Desired Configuration Models, you deploy each model to targeted servers, where it runs as an SMS 2003 package. Once data is returned to the SMS 2003 database server, you may generate compliance reports on demand. Using Microsoft Operations Manager 2005, you can specify that IT staff be alerted automatically of configurations that are defined as out-of-compliance so that they can take appropriate action to avoid disruptions in service. Table 1 provides a list of the minimum technology requirements that you will need in place to use SMS 2003 Desired Configuration Monitoring.
Solution ImplementationMicrosoft Services provides Desired Configuration Monitoring for Messaging consulting services utilizing the capabilities of SMS 2003 Desired Configuration Monitoring and creating Desired Configuration Models for each Exchange server role. These services will enhance your change, configuration, and release management processes for Exchange. Please visit the Microsoft Services Messaging Services website to learn more. DCM Configuration Manifest Beta ProgramVisit http://connect.microsoft.com to register for the DCM Configuration Manifest Beta program. This program has been established to test and validate sample configuration files for Microsoft Internet Security and Acceleration Server 2004, Microsoft Windows Server 2003, and Microsoft Exchange Server 2003. These manifests can help get you started with the DCM solution and save time in creating the initial configuration manifests required to use the DCM solution in your environment. Each manifest can be edited by the DCM authoring tool to meet your specific needs. Visit Microsoft Connect and register today! Additional Resources
|