Windows Management Instrumentation (WMI) providers evaluation criteria

Exchange

Find evaluation criteria information for the WMI providers for Exchange.

Last modified: November 05, 2013

Applies to: Exchange Server 2003

In this article
Functional criteria for WMI providers for Exchange
Development criteria for WMI providers for Exchange
Security criteria for WMI providers for Exchange
Deployment criteria for WMI providers for Exchange
Additional resources

Windows Management Instrumentation (WMI) is the Microsoft implementation of Web-Based Enterprise Management (WBEM). WBEM provides uniform access to management information, including information about the state of system memory, inventories of currently installed client applications, and other information about client status. The Exchange WMI providers supply information about the configuration and state of Exchange servers. Complex queries over the message tracking logs, however, can take a long time to process.

Important note Important

The Exchange WMI providers are not available in versions of Exchange starting with Exchange Server 2007.

The following table lists and describes the functional criteria for WMI providers for Exchange. For descriptions of the functional criteria, see Functional criteria in the Exchange development technology evaluation criteria descriptions article.

Table 1:  WMI providers for Exchange functional criteria

Criterion

Description

Application function

WMI provider applications are used for system monitoring and management consoles, administrative migration, analysis, and maintenance scripts.

Availability

The WMI providers for Exchange are available in Exchange Server 2003. This technology is not available in versions of Exchange starting with Exchange Server 2007.

Application architectures

WMI is typically used in command-line or GUI-based administrative scripts. In addition, WMI can be used within ASP pages to form a web-based Exchange 2003 server health monitor.

Remote usage

WMI can be used remotely. The WMI classes verify that the user has the appropriate permissions to access and control the objects.

Major objects

Instances provided by the Exchange 2003 WMI providers include, but are not limited to, the following: ExchangeConnectorState, ExchangeLink, ExchangeQueue, ExchangeServerState, Exchange_FolderTree, Exchange_Link, Exchange_Logon, Exchange_Mailbox, Exchange_Queue, Exchange_SMTPLink, Exchange_SMTPQueue, Exchange_ScheduleInterval, and Exchange_Server objects.

Data access model

Exchange WMI provider objects are represented as hierarchical lists of objects that have properties and methods. In addition, instances can be selected by using the WMI Query Language (WQL), which is similar to SQL in structure.

Threading models

Applications that use free-threading should not share WMI object instances among asynchronously operating threads. WMI is most frequently used in scripted applications, where threading is not an issue.

Transactions

None.

Management capabilities

WMI is itself a management technology.

The following table lists and describes the development criteria for WMI providers for Exchange. For descriptions of the development criteria, see Development criteria in the Exchange development technology evaluation criteria descriptions article.

Table 2:  WMI providers for Exchange development criteria

Criterion

Description

Languages and tools

WMI can be used in any COM-compatible language. It is most frequently used with scripting languages such as VBScript and Jscript. You can use C/C++ to develop WMI applications but it is much more difficult than using scripting languages.

Managed implementation

WMI can be used in a managed-code environment, with any language that provides access to the .NET Framework.

Scriptable

Yes.

Test/debug tools

No special tools are required to debug applications that use WMI.

Expert availability

Developers who have experience with the Exchange WMI Providers are readily available.

Available information

You can find information about creating applications and scripts that use WMI in Microsoft and third-party books. For more information about WMI, see Windows Management Instrumentation.

Developer/deployment licensing

You do not need any licenses to deploy an application that uses WMI to access Exchange. Refer to your Exchange and MSDN subscription licensing agreements to determine whether additional licenses are required for the Exchange servers that store the data accessed by your WMI-based applications.

The following table lists and describes the security criteria for WMI providers for Exchange. For descriptions of the security criteria, see Security criteria in the Exchange development technology evaluation criteria descriptions article.

Table 3:  WMI providers for Exchange security criteria

Criterion

Description

Design-time permissions

Applications that use WMI pass a user security context to the WMI provider. This can either be supplied in the script as a user name and password or be obtained from the user running the script. The Exchange WMI providers allow only Exchange administrators to perform actions that affect the Exchange system. If the development computer requires WMI components to be installed, a user who has local administrator privileges must perform the installation.

Setup permissions

WMI scripts can typically be copied to the intended computer and run without modification. The client computer must be in the same domain as the target computer. Depending on the type of Setup program used, the user may need local administrator rights to install software.

Run-time permissions

The Exchange WMI providers allow only Exchange administrators to perform actions that affect the Exchange system.

Built-in security features

WMI scripts pass a user security context to the WMI provider. This can either be supplied in the script as a user name and password or be obtained from the user running the script. The Exchange WMI providers allow only Exchange administrators to perform actions that affect the Exchange system.

Security monitoring features

None.

The following table lists and describes the deployment criteria for WMI providers for Exchange. For descriptions of the deployment criteria, see Deployment criteria in the Exchange development technology evaluation criteria descriptions article.

Table 4:  WMI providers for Exchange deployment criteria

Criterion

Description

Server platform requirements

The Exchange server that the WMI-based application accesses must have the appropriate WMI providers installed and the MOF file compiled.

Client platform requirements

There are no specific client requirements beyond the WMI core components and the WMI application.

Deployment methods

You can use standard software distribution technologies to deploy applications that use WMI. The installer should verify that WMI is installed and configured properly. Scripts can usually be copied to the destination computer.

Deployment notes

If your WMI application programmatically browses the Exchange 2003 provider class definitions and the application is running on a computer that does not have Exchange installed, you should use mofcomp.exe to compile the MOF file for the Exchange WMI providers on the client computer.

Show:
© 2014 Microsoft