The All TECHNICAL Blog : DCM Troubleshooting

DCM Solution Troubleshooting Steps

Sai Kodi — Fri, 23 Feb 2007 03:09:00 GMT

Here are some troubleshooting steps that you might want to perform for a successful DCM deployment / execution: 1. Install DCM Solution and ensure that all the files were deployed and the DCM Solution database created. 1. Create an SMS package / program...(read more)

DCM v 2.0 Download Updated

Sai Kodi — Thu, 26 Oct 2006 17:42:00 GMT

Overview

Microsoft Systems Management Server (SMS) 2003 Desired Configuration Monitoring (DCM) 2.0 now supports configuration monitoring of desktops and servers. The accelerator allows the user to define desired hardware, operating system, and application configuration settings in multiple configuration data sources. Then, using the supplied auditing engine, DCM compares desired settings with actual settings and finally reports configuration compliance.

DCM 2.0 includes a redesigned user interface (UI) to reduce the time needed for defining Configuration Items. The new user interface supports complex rule definition with the Advanced View and adds a wizard-based simplified UI for defining simple rules as the Standard View. The new UI also includes common rule templates and enables users to define common rules specific to their organizations. In addition, CI rules can now be viewed and edited in a table view.

Notes

DCM 2.0 was updated and re-released on October 25, 2006, to address a known issue when parsing complex XPath query expressions generated using DCM 1.0. See the updated Release Notes for more details. If you have experienced any problems with DCM 2.0 rendering query expressions defined in DCM 1.0, I encourage you to download this updated version. Please see the updated Release Notes for more details.

Choose the SMS_DCM2.0_for_DotNet1.1.zip download package if you are using .NET Framework 1.1. Choose the SMS_DCM2.0_for_DotNet2.0.zip download package if you are using .NET Framework 2.0. With either DCM package, you also should download the Configuration_Items.zip and SMS_Reports.zip packages. You can select the files you want to download from the list on this page.

Send questions or feedback to us directly at CISfdbk@microsoft.com.

DCMSolution Database not created during installation

Sai Kodi — Fri, 29 Sep 2006 23:56:00 GMT

There was a known issue in Desired Configuration Monitoring (DCM) Solution Accelerator v 1.0 where the DCMSolution database was not created during installation in specific cases. The issue occurred because the v 1.0 installer retrieved SQL information from a different registry path. However it happens only when the default data / log file locations is altered after SQL Server is installed.

This issue has been fixed in the DCM v 2.0 releases. I am outlining how DCM installer detects the data / log folders for creating the DCMSolution database.

For SQL Server Default Instance:

The DCMSolution installer first retrieves the value of "DefaultData" under the registry key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer". If it exists and is not blank, it goes with this path. This value is populated if you alter the data / log file locations after the SQL Server was installed.
If the “DefaultData” value is blank, then it gets the value of "SQLPath" under the registry key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Setup". This is the default SQL location that you provide at the time of installing SQL Server.

For SQL Server Named Instance:

The DCMSolution installer first retrieves the value of "DefaultData" under the registry key " HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\<InstanceName>\MSSQLServer". If it exists and is not blank, it goes with this path. This value is populated if you alter the data / log file locations after the SQL Server was installed.
If the DefaultData value is blank, then it gets the value of "SQLPath" under the registry key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\<InstanceName>\Setup". This is the default SQL location that you provide at the time of installing SQL Server.

The above is true for SQL Server 2000 SP3 and above. If you are facing a problem where the DCMSolution database is not being created at install time, you should check these registry locations and verify that the physical paths pointed to by these registry values exist on the physical server. Let me know if you have further questions.

Thanks,

Sai Kodi

XMLToDCMTransfer DTS package requires 3 mandatory files for proper execution

Sai Kodi — Thu, 28 Sep 2006 09:49:00 GMT

In DCM v 2.0, the functionality of the XMLToDCMTransfer DTS package has been altered. In the current version (v 2.0), the DTS package requires the following three files to be present in the DCM UI folder for successful execution:

DCM.xsd
DCMXMLValidator.exe
<machinename>_Mapping.xml (at least one mapping file is required)

The DCM.xsd and DCMXMLValidator.exe are deployed when the DCM Author component is selected at the time of installation. The mapping file is created when you save a DCM CI using the DCM Authoring Tool.

If you do not have the DCM UI folder and any of these three files in the DCM UI folder (because you did not select DCM Author component during installation), then you should create the DCM UI folder manually and copy the required files to the folder before attempting to execute the XMLToDCMTransfer DTS package.

Feel free to post any appropriate questions.

Thanks,

Sai Kodi

Now Available: SMS 2003 Desired Configuration Monitoring Version 2.0

Sai Kodi — Mon, 18 Sep 2006 17:42:00 GMT

DCM v2.0 automates the configuration management audits between desired or defined configuration settings and actual configuration settings. DCM accomplishes this by allowing the user to define desired hardware, operating system and application configuration settings in multiple configuration data sources and then using the supplied auditing engine, DCM compares desired settings with actual settings and then reports configuration compliance. SMS 2003 Desired Configuration Monitoring (DCM) Version 2.0 now supports configuration monitoring of desktops and servers.

DCM Version 2.0 continues to monitor configuration settings in the Microsoft Active Directory, Window Management Instrumentation (WMI), Metabase, file system, and registry and extends DCM Version 1.0 by adding support for the SQL Server data source, Windows desktop, x64 and .Net Framework 2.0. DCM Version 2.0 also adds predefined baseline Configuration Items for many Microsoft products and customizable SMS web reports.

As a highlight to the solution update, DCM Version 2.0 includes a redesigned user interface (UI) to reduce the time needed for defining Configuration Items. The new user interface supports complex rule definition with the Advanced View and adds a wizard-based simplified UI for defining simple rules as the Standard View. The new UI also includes common rule templates and enables users to define common rules specific to their organizations. In addition, CI rules can now be viewed and edited in a table format. These changes dramatically reduce the time needed to define and edit Configuration Items when using DCM.

Microsoft Systems Management Server (SMS) 2003 Desired Configuration Monitoring (DCM) is a functional extension to SMS 2003 to provide system configuration definition and monitoring functionality. This solution was designed to provide a framework today to begin exploring the power of DCM prior to the release of System Center Configuration Manager (ConfigMgr) 2007. ConfigMgr 2007 will offer a fully integrated and supported implementation of these capabilities.

DCM was developed in collaboration with the Microsoft Operations and Exchange Centers of Excellence and is applied internally at Microsoft. Microsoft IT uses SMS 2003 DCM to monitor Exchange and Windows Core Services (AD, DNS, DHCP, and WINS) configurations. The core set of baseline configurations available with the DCM Version 2.0 solution are intended to help users get started with DCM. Microsoft Services offers a complete implementation service for DCM using configuration management best practices and includes expanded Configuration Items for core Microsoft products. For details about Microsoft Services offerings using DCM, please contact opsleads@microsoft.com.

You can download DCM v 2.0 here: http://go.microsoft.com/fwlink/?LinkId=72132.

New 3rd Party Offerings for DCM

Sai Kodi — Wed, 19 Jul 2006 19:50:00 GMT

Alpha Tech Solutions has recently released training for SMS 2003 DCM and they also offer an automatic rule generator to help create configuration manifests. I have not yet used or tested the rule generator tool, but I have seen the training and it combines useful audio and video instruction across multiple scenarios for using the DCM solution.

Below are quotes from the Alpha Tech Solutions website (http://www.alpha-tech-solutions.com).

1. Desired Configuration Monitoring Training

Alpha Tech Solutions computer based training provides you with in-depth step by step instructions on solutions, concepts and best practices that are supported by Alpha Tech leading edge solutions. …

The SMS 2003 Desired Configuration Monitoring Training will take you though the installation and deployment of the solution and provide you with valuable knowledge on how to create configuration manifests. Included in the training are real world scenarios and samples that you can use for configuration monitoring.

2. ATS Rule Generator

This time saving solution allows you to generate rules for configuration settings in a DCM configuration manifest by capturing them from a given “ideal” machine. The ATS Rule Generator will create configuration rules on the fly for any xml file generated by Microsoft’s Desired Configuration Monitoring Product.

In April, Configuresoft also released “ECM Management Extensions for DCM.”

Below is a quote from the Configuresoft website (http://www.configuresoft.com/Products/dcm.aspx).

Compliance expertise for Microsoft management frameworks

Enterprise Configuration Manager Management Extensions for DCM (ECMMX) allow Microsoft® SMS users to quickly and easily monitor and manage system compliance for both Windows and non-Windows platforms from a familiar interface. Working in partnership with Microsoft to extend the System Center management framework, Configuresoft provides compliance reporting and control for heterogeneous environments. ECMMX seamlessly integrates with existing Windows® server management tools, making extensive compliance information visible and instantly available. ECM prioritizes and continuously validates the state of system compliance via its Compliance Toolkits, which feature rule-based templates, reports and dashboards that plug into ECM.

Sample DCM Manifests Available!

Sai Kodi — Wed, 12 Apr 2006 01:18:00 GMT

Visit 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 will 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!

To find the program on connect, follow these steps:

Go to connect site, http://connect.microsoft.com/

Sign in using your VALID passport account.
Find the Microsoft SMS 2003 Desired Configuration Monitoring: Configuration Manifest Program in the available programs section.
Then apply to join this program.
After that you should be able to download the package.

Thanks!

Windows Server Deployment Automation Survey

Sai Kodi — Wed, 12 Apr 2006 00:52:00 GMT

The Solutions for Infrastructure and Management team in the Core Infrastructure Solutions group wants to better understand customer needs around installation and configuration for Longhorn server deployment. We would appreciate it if you would complete a short survey on this topic. Your feedback will be a critical factor in the design of the solution. http://connect.microsoft.com

Dynamic link library file mscoree.dll could not be found – while executing DCM Engine

Sai Kodi — Wed, 22 Mar 2006 09:40:00 GMT

While executing the DCM Command line wrapper (also called the DCM Engine) on a server, you might come across the error: “Unable to locate dll - Dynamic link library file mscoree.dll could not be found in the specified path.”.

This is an error caused when dot net framework v 1.1 is not installed on the target machine. The DCM Command line wrapper (DCM Engine) is a dot net executable and it requires dot net framework v 1.1 to be installed on the target machine. This error can be resolved by installing the dot net framework v 1.1. Refer to the article at http://support.microsoft.com/?kbid=316091 for more information on this error.

Management Exception While executing Desired Configuration Monitoring Engine

Sai Kodi — Sun, 19 Mar 2006 21:43:00 GMT

You might run into a Management Exception while executing the DCM Command Line Wrapper (also called the DCM Engine). It’s a general practice to copy the bits of the DCM Engine to another machine in order to execute the engine on the other machine. In this process, you might forget to copy over the DCM.MOF file. This file is very essential.

The DCM.MOF file defines the DCM-related WMI classes. When the command line wrapper is executed, it first checks if both the WMI classes for DCM exist in the WMI repository. If they do not exist, the command line wrapper executes the DCM.MOF file to create the WMI classes. In the event if the mof file does not exist in the folder (possibly not copied), then it will fail to create the WMI classes. When the rules are evaluated, and when an event is ready to being published to the WMI repository by the DCM Issue Processor, it does not find the appropriate classes in the WMI repository. Hence, it throws a Management Exception. It might look similar to this:

System.Management.ManagementException: Invalid namespace

at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)

at System.Management.ManagementScope.InitializeGuts(Object o)

at System.Management.ManagementScope.Initialize()

at System.Management.ManagementObject.Initialize(Boolean getObject)

at System.Management.ManagementBaseObject.get_wbemObject()

at System.Management.ManagementClass.CreateInstance()

at DCMCmd.DCMCmd.Main(String[] argsParm)

If you happen to see this exception in the NT Event log (Application section), ensure that you have the DCM.MOF file in the same folder as the DCM Command Line Wrapper (where you have DCMCmd.exe and other bits) and re-run the DCMCmd.exe. That should fix the problem.

You might also be interested in knowing the files that are required in order to execute the DCM Engine. I have posted another article on the blog which gives a listing of the required files. You can find the post here.

Thanks!