Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

Collaboration Data Objects for Exchange Management (CDOEXM) evaluation criteria

Exchange

Published: July 16, 2012

Find evaluation criteria information for Collaboration Data Objects for Exchange Management (CDOEXM).

Applies to:  Exchange Server 2003 

In this article
Functional criteria for CDOEXM
Development criteria for CDOEXM
Security criteria for CDOEXM
Deployment criteria for CDOEXM
Additional resources

Collaboration Data Objects for Exchange Management (CDOEXM) provides the fundamental Component Object Model (COM) classes and interfaces that are used to manage the Exchange store. Before you can use CDOEXM, you must install the Exchange Administrative tools on your computer.

CDOEXM does not ship in and is not supported with versions of Exchange starting with Exchange Server 2007. Use the Exchange Management Shell to perform management tasks if you’re using Exchange 2007 or a later version.

CDOEXM can only be run on a computer on which the Exchange 2003 administrative tools have been installed. The computer running the CDOEXM application and the computer running Exchange 2003 must be in the same Active Directory service organization.

Important note Important

Because of issues with multiple-hop authentication and unexpected results observed in multithreaded runtime environments, we do not support the use of CDOEXM in ASP.NET pages, ASP web pages, or web services. To create web-based Exchange management applications that use CDOEXM functionality, we recommend that you wrap CDOEXM in a Distributed Component Object Model (DCOM) package and then call that package from your application.

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

Table 1:  CDOEXM functional criteria

Criterion

Description

Application function

CDOEXM is used in administrative applications and scripts to control, examine, and diagnose Exchange 2003 servers and stores.

Availability

Included in Exchange 2003. CDOWF does not ship in and is not supported with versions of Exchange starting with Exchange Server 2007. You must use the version of CDOEXM that ships with Exchange 2003 when you access Exchange 2003.

Application architectures

CDOEXM applications are typically used for administrative tools and scripts that use CDOEXM and Active Directory Services Interface (ADSI) to operate on Exchange servers, stores, and folder trees. You must run applications that use CDOEXM on a computer that has the Exchange Management Tools installed.

Remote usage

CDOEXM can only be run on a computer that has the Exchange 2003 Administrative Tools are installed.

Major objects

CDOEXM provides COM/Automation-compatible objects that represent components of Exchange 2003 servers. These include the ExchangeServer, FolderTree, MailboxStoreDB, PublicStoreDB, and StorageGroup classes.

Data access model

Collections of some object types can be accessed as ADO rowsets by using the DataSource object. The individual rows represent other CDOEXM objects.

Threading models

Applications that use CDOEXM do not have any specific threading restrictions. However, applications that use free-threading should not share CDOEXM object instances among asynchronously operating threads.

Transactions

Transactions are not supported with CDOEXM.

Management capabilities

CDOEXM does not generate Windows Event Log entries, and no performance counters are available to measure CDOEXM.

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

Table 2:  CDOEXM development criteria

Criterion

Description

Languages and tools

CDOEXM can be used with any COM/Automation-compatible language, as well as with non-COM languages such as C/C++.

Managed implementation

CDOEXM is an unmanaged component. Use of CDOEXM is supported under the COM Interoperability layer of Visual Studio .NET and the .NET Framework. CDOEXM can only be run on a computer on which Exchange has been installed.

Scriptable

CDOEXM is scriptable by means of the Windows Scripting Host (WSH), but it is not supported in ASP or ASP.NET.

Test/debug tools

You do not need any special debugging tools to debug applications that use CDOEXM.

Expert availability

You can find developers who are familiar with CDOEXM in many Microsoft and third-party forums and communities.

Available information

Microsoft and third-party books that describe programming for Exchange by using CDOEXM are available. In addition, CDOEXM is documented in the Exchange Server 2003 SDK.

Developer/deployment licensing

Refer to your Exchange and MSDN subscription licensing agreements to determine whether additional licenses are required for the computers that your CDOEXM applications are developed and deployed on.

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

Table 3:  CDOEXM security criteria

Criterion

Description

Design-time permissions

Depending on your development environment and configuration, you might need Exchange administrative permissions for the servers that you are working with. Use caution when granting anyone unrestricted access to user mailboxes and Exchange system configuration settings.

Setup permissions

Applications that use CDOEXM must run on either an Exchange server or a computer on which the Exchange Administrative tools are installed. The user who is setting up the application must have permissions to install software on that computer. In addition, if Setup makes changes to Exchange, the user must have permission to access that data or make the configuration changes.

Run-time permissions

Because CDOEXM controls and configures components of an Exchange server, only Exchange administrators should be permitted to run applications that use CDOEXM. For applications that use CDOEXM from an Exchange administrative console computer, it must be in the same domain as the Exchange server.

Built-in security features

CDOEXM uses the underlying Windows Server 2003 operating system security features. Most operations require that the application user security context have Exchange administrative permissions.

Security-monitoring features

None.

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

Table 4:  CDOEXM deployment criteria

Criterion

Description

Server platform requirements

You can only run CDOEXM on a computer on which the Exchange 2003 Administrative Tools are installed. Both the computer running CDOEXM and the Exchange 2003 server that is being accessed must be in the same Active Directory service organization. CDOEXM cannot be used with versions of Exchange starting with Exchange Server 2007.

Client platform requirements

You can only run CDOEXM on a computer on which the Exchange 2003 Administrative Tools are installed. Both the computer running CDOEXM and the Exchange 2003 server that is being accessed must be in the same Active Directory organization. CDOEXM cannot be used with versions of Exchange starting with Exchange 2007.

Deployment methods

If the client or application that is being installed needs access to CDOEXM, the installer should verify that the computer contains the Exchange 2003 Administrative Tools and that CDOEXM is properly installed on the computer.

Deployment notes

The CDOEXM version that ships with Exchange 2003 must be used to access Exchange 2003.

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.