Deployment Notes
Deployment Notes
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 Deployment Notes.
| Technology | Are there other important details surrounding deployment of applications that use this technology? |
|---|---|
| Active Directory Services Interfaces (ADSI) | |
| Collaboration Data Objects for Windows 2000 (CDOSYS) | On systems on which Microsoft® Microsoft® Exchange 2000 Server or Exchange Server 2003 is installed, the CDOSYS components are replaced by Collaboration Data Objects for Exchange 2000 Server (CDOEX), which provides additional functionality over CDOSYS. CDOEX is described separately. |
| CDOSYS SMTP/NNTP Event Sinks | On systems on which Exchange 2000 Server or Exchange Server 2003 is installed, the CDOSYS components are replaced by CDOEX, which provides additional functionality over CDOSYS. CDOEX is described separately. Applications that use CDOSYS SMTP/NNTP events should not be installed on Exchange back-end servers. |
| Collaboration Data Objects for Exchange 2000 Server (CDOEX) | |
| Collaboration Data Objects for Exchange Management (CDOEXM) | The CDO for Exchange Management (CDOEXM) version that ships with Exchange Server 2003 must be used when accessing Exchange Server 2003. The Exchange Server 2003 CDOEXM can also be used to access Exchange 2000 Server. The CDOEXM library that ships with Exchange 2000 Server is not supported for accessing Exchange Server 2003. |
| Collaboration Data Objects for Exchange Workflow (CDOWF) | |
| Exchange OLE DB Provider (ExOLEDB) | |
| Exchange Store Event Sinks | Exchange store events that can be misused, or that can cause problems if installed incorrectly, should implement the ICreateRegistration interface, and programmatically prevent the event sink from being improperly registered. Cross-store access from within an event sink is not possible. After the event sink is registered and wrapped as COM+ applications, any user who knows the name of the event sink can register it in a folder to which they have write permissions. |
| Exchange Web Forms | If special user permissions are granted to enable deployment and testing of an Exchange Web forms-based application, remember to review and possibly remove those permissions after the application has been deployed and tested. |
| HTTP/Web Distributed Authoring and Versioning (WebDAV) | When using WebDAV with NTLM or Kerberos authentication to access Exchange data by means of a front-end server, the Keep-alive protocol header must be set to True. If it is not, the request might not be passed to the Exchange server. |
| WebDAV Notifications | |
| Incremental Change Synchronization (ICS) | Because ICS relies on Exchange MAPI, the installer application should verify that the correct version of MAPI is installed and correctly configured. ICS applications are likely to be architected as three services (the collector, synchronizer, and agent), and one GUI application that allows a user to configure the synchronization source, target, schedule, and so on. |
| Lightweight Directory Access Protocol (LDAP) | |
| Messaging Application Programming Interface (MAPI) | The installer should verify that the correct version of MAPI is available. |
| Outlook Object Model (OOM) | Because Outlook should not be installed on the Exchange server, applications that use OOM cannot be run on the Exchange server. |
| Outlook Web Access | |
| Exchange Rules | |
| SMTP Event Sinks | SMTP event sinks run in the same process as Microsoft Internet Information Services (IIS), and share the same security credentials as that service account. This may affect what resources the event sink can access. |
| Windows Management Instrumentation (WMI) providers for Exchange | If your WMI application programmatically browses the Exchange provider class definitions, and the application is running on a computer on which Exchange has not been installed, the MOF file for the Exchange providers should be compiled on the client computer by using mofcomp.exe. |
| Exchange Backup and Restore API | |
| Exchange writer for the Windows Volume Shadow Copy Service |
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.