This document contains detailed information on how to set up and operate the DCM environment used to monitor deployment servers and desktop computers deployed through BDD 2007. This process uses SMS to distribute the DCM engine and CI files, a computer running SQL Server to store data collected by the DCM engine, and SQL Server Reporting Services to view reports that the DCM solution generates. The main goal of a DCM solution for BDD 2007 is to ensure that the deployment servers and desktop computers remain functional after the BDD 2007 project is implemented in a production environment and that settings defined in the desktop images are not changed in a production environment.

This guide is intended for a technical audience. It includes information about how to install and configure a DCM solution to monitor the BDD 2007 deployment servers and client computers. It also documents how the process is run and how to customize the system to meet specific requirements.

On This Page

Background Background
Assumptions Assumptions
Education and References Education and References
Lab Requirements Lab Requirements


This document and the work it entails typically begin in the MSF Developing Phase, in which the DCM solution is installed and CI files are developed. The work continues into the Stabilizing Phase, in which the CI files are tested, piloted, and approved for release to the Deploying Phase.

The primary consumer of this work is the MSF Development Role Cluster, because most of this document focuses on the development work needed to install the DCM solution and to create the CI files.

The developers work with the technologies and processes described in this document to create and implement a monitoring environment that will ensure the functionality of the BDD 2007 implementation after the entire solution is deployed and handed to information technology (IT) Operations.

The input into this process is the functional specification, and the outputs from this process are the CI files and the DCM environment used to monitor the BDD 2007 deployment servers.


Those who use this system should be familiar with the concepts of configuration management, including concepts and technologies such as:

  • Configuration management database (CMDB)

  • CIs

  • SMS

  • SQL Server

  • DCM

Education and References

The following resources for education and reference can be helpful for those starting automation projects:

Lab Requirements

DCM requires the use of SMS and SQL Server along with other tools and services. The following list shows all necessary items for a fully functional lab environment:

  • Windows domain (This domain could be a Microsoft Windows Server® 2003 or Windows 2000 domain.)

  • A computer running Microsoft SQL Server 2005 or SQL Server 2000

  • A computer running SQL Server 2000 or SQL Server 2005 Reporting Services (This can be the same computer used for the databases.)

  • A computer running SMS 2003

  • A BDD 2007 build server (Details on this server are available in the Computer Imaging System Feature Team Guide.)

  • Network switches and cabling (100 megabits/sec (Mbps) or faster is recommended to accommodate the high volumes of data.)

  • Client computers (Any unique computer configuration found in production should be duplicated in the lab to allow for testing each hardware configuration.)

  • A computer to be used for creating the CI files

  • The DCM solution software, available at Microsoft Systems Management Server 2003 Desired Configuration Monitoring 2.0 at

  • Licenses for all products listed above

Note   The Desired Configuration Monitoring feature team typically shares the lab environment that the Computer Imaging System feature team uses.


Get the Microsoft Solution Accelerator for Business Desktop Deployment 2007

Update Notifications

Sign up to learn about updates and new releases


Send us your comments or suggestions