The following Application Configuration Item Instance example determines whether the Microsoft System Center Configuration Manager 2007 client is installed on the system by using Microsoft Windows Installer-based detection.

Application Configuration Item Instance Reference

Application Configuration Item Example

  Copy Code
<?xml version="1.0" encoding="utf-8"?>

The root element for any DCM Digest document is the DesiredConfigurationDigest element referenced below.  All of the XML elements/attributes are defined in the DCM Digest schema definition namespace.

<DesiredConfigurationDigest xmlns="">

Every DCM Digest must contain exactly one configuration item. Specifically one of the following: an application, operatingsystem, general or baseline.
This digest defines an application configuration item.  

The unique identity of the configuration item is the combination of the attributes AuthoringScopeID, LogicalName and Version. 
Each attribute is part of the unique identity of the configuration item; the actual identity is AuthoringScopeID + LogicalName + Version.

AuthoringScopeID (string) - This attribute corresponds to the author’s namespace or identity.
LogicalName (string) - This attribute identifies the configuration item within the authoring scope.
Version (string) - This attribute specifies the version of the configuration item.

	<Application AuthoringScopeId="ScopeId_F348CC96-19CA-4F5D-9D4F-D1451B5BEB1E" LogicalName="Application_5cb68ff1-a234-41ed-a7d4-14174d8108b7" Version="1" Is64Bit="false">
			<DisplayName Text="Configuration Manager Client />
			<Description Text="Configuration Manager Client (msi-based detection)" />

There are no parts defined for this configuration item.
Parts are physical things with fixed lists of properties.Mandatory element tag for the section of the DCM Digest used to define Object parts, including:
Assembly (registered in the Global Assembly Cache (GAC))

			<ParentReferences />

There are no settings defined for this configuration item. 
Settings are configurable name/value pairs which influence the behavior of hardware and software. DCM can discover settings using any of the supported providers, including:
WMI (WQL query)
Microsoft SQL Server (SQL query)
Active Directory (LDAP)
XML (XPath query)
IIS Metabase
Script (JScript/VBScript/Powershell)


RootComplexSetting is the root container for all settings. Every configuration item has one of these, even if there are no actual settings defined.
			<RootComplexSetting />

This application is discovered via MSI-based discovery. If it does exist (is discovered) the system then discovers the parts and settings. Finally, the system evaluates the rules (if any) defined against the part property values and the setting values.

		<MsiDiscoveryInfo IsPerUser="false" ProductCode="{D7D7EE27-817F-481D-865F-F5755FA89E2E}" Version="4.00.5507.0000" />


See Also

Send comments about this topic to Microsoft.