Remote Usage
Remote Usage
This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release. This topic provides information about how the different technologies compare with regard to Remote Usage.
| Technology | Can the technology be used remotely? |
|---|---|
| Active Directory Services Interfaces (ADSI) | Yes. |
| Collaboration Data Objects for Windows 2000 (CDOSYS) | CDOSYS is installed with Microsoft® Windows, and sends mail by using standard network protocols. Applications that run on an Exchange server typically use CDO for Exchange 2000 Server. |
| CDOSYS SMTP/NNTP Event Sinks | CDOSYS SMTP/NNTP event sinks must run on the computer on which mail is being processed and cannot be used in COM+ applications. |
| Collaboration Data Objects for Exchange 2000 Server (CDOEX) | CDOEX is not supported for remote use. |
| Collaboration Data Objects for Exchange Management (CDOEXM) | CDOEXM can only be run on a computer that has the Exchange Administrative Tools installed. |
| Collaboration Data Objects for Exchange Workflow (CDOWF) | CDOWF can only be run on the Exchange server. |
| Exchange OLE DB Provider (ExOLEDB) | ExOLEDB cannot be used remotely. |
| Exchange Store Event Sinks | Exchange store events can only be run on the Exchange server that manages the store where the events are registered. In addition, the event sink can only access information within the Exchange store that they are registered in; cross-store access is not possible. |
| Exchange Web Forms | Exchange Web forms can be used remotely by means of Outlook Web Access. However, Web forms are stored and processed on the Exchange server. |
| HTTP/Web Distributed Authoring and Versioning (WebDAV) | WebDAV is often ideal for remotely accessing Exchange. Because it uses the same ports that HTTP and HTTPS use to communicate, corporate firewalls and routers often require no special configuration. |
| WebDAV Notifications | WebDAV is often ideal for remotely accessing Exchange. Because it uses the same ports that HTTP and HTTPS use to communicate, corporate firewalls and routers often require no special configuration. |
| Incremental Change Synchronization (ICS) | The ICS interfaces operate by means of MAPI, and so can be executed remotely. When synchronizing changes offsite, or across the Internet, it is recommended that you use a proxy collector and remote agent, and encrypt data during transmission between them. |
| Lightweight Directory Access Protocol (LDAP) | Firewalls and routers are usually configured to block LDAP access outside the corporate intranet. Applications that use LDAP and ADSI typically do not execute on the computer running Active Directory. |
| Messaging Application Programming Interface (MAPI) | MAPI uses Remote Procedure Calls (RPC) to communicate with the Exchange server. Typically RPC is intentionally blocked from passing through Internet firewalls. |
| Outlook Object Model (OOM) | OOM can only be used on a machine where Outlook is installed. OOM can be used to access information stored in Exchange that is available in the Outlook application. |
| Outlook Web Access | Outlook Web Access configured to use SSL/TLS and basic authentication can be used on an intranet as well as over the Internet. |
| Exchange Rules | The Exchange rules COM components use MAPI to communicate with the Exchange server and MAPI uses Remote Procedure Calls (RPC) to communicate with the Exchange server. Typically RPC is intentionally blocked from passing through Internet firewalls. However, Exchange Server 2003 does support RPC over HTTP, which can be configured to allow clients to remotely access an Exchange store. |
| SMTP Event Sinks | SMTP event sinks must run on the computer on which mail is being processed. SMTP event sinks cannot be used in COM+ applications. |
| Windows Management Instrumentation (WMI) providers for Exchange | Yes. WMI can be used remotely. The WMI classes verify that the user has the appropriate permissions to access and control the objects. |
| Exchange Backup and Restore API | Applications that use the Backup and Restore API should run only on a computer running Exchange Server 2003 that also manages the Exchange storage groups that are being accessed. |
| Exchange writer for the Windows Volume Shadow Copy Service | Applications that use VSS must run on the Microsoft Windows Server™ 2003 computer on which the Exchange store process is running. Because of the flexibility in large storage systems, the hardware hosting the storage volumes might not actually be a physical part of the computer running Windows Server 2003. |
Send us your feedback about the Microsoft Exchange Server 2003 SDK.
This topic last updated: June 2006
Build: June 2007 (2007.618.1)
© 2003-2006 Microsoft Corporation. All rights reserved. Terms of use.