The SMS Provider is essentially the same as the SMS 2003 Provider, with the addition of new classes that support new Configuration Manager features. You can access the SMS Provider through the usual WBEM interfaces, but for managed code you must use the managed SMS Provider SDK.

The managed SMS Provider SDK provides a managed code library that abstracts the SMS Provider. It provides .NET Framework classes and interfaces that connect to the SMS Provider, make queries, and otherwise manipulate Configuration Manager objects and the site control file. You can use the managed SMS Provider SDK in stand-alone applications, or you can use the user interface framework to extend the existing Configuration Manager console.

For more information, see Managed SMS Provider Fundamentals in Configuration Manager.

The user interface framework lies on top of the managed SMS Provider SDK. The user interface framework provides functionality for dialog boxes and the Configuration Manager console, and it provides user interface validation within the Configuration Manager console. You can extend this user interface framework to add your own forms to the Configuration Manager console, or you can integrate your own forms within existing Configuration Manager console forms.

The Configuration Manager console XML defines how the Configuration Manager console looks and behaves. The XML defines nodes, queries, actions, forms, and everything else that is necessary to render the Configuration Manager console hierarchy, the results pane, and the action pane.

The XML files that are used by the Configuration Manager console are stored in %ProgramFiles%\Microsoft Configuration Manager\AdminUI\XmlStorage\. The following table shows the subfolders.

Concepts

Other Resources