Deployment Methods
Deployment Methods
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 Methods.
| Technology | What methods are available/recommended for installing, distributing and deploying applications that use this technology? |
|---|---|
| Active Directory Services Interfaces (ADSI) | No special deployment methods are required. |
| Collaboration Data Objects for Windows 2000 (CDOSYS) | There are no special requirements for application installation, beyond verifying that the computer is running one of the operating systems that include CDOSYS. |
| CDOSYS SMTP/NNTP Event Sinks | There are no special requirements for application installation, beyond verifying that the computer is running one of the operating systems that include CDOSYS. |
| Collaboration Data Objects for Exchange 2000 Server (CDOEX) | If the client or application being installed needs direct access to CDOEX, the installer should verify that the computer is an Exchange server, and that CDOEX is properly installed on the computer. |
| Collaboration Data Objects for Exchange Management (CDOEXM) | If the client or application being installed needs access to CDOEXM, the installer should verify that the computer contains the Exchange Administrative Tools, and that CDOEXM is properly installed on the computer. |
| Collaboration Data Objects for Exchange Workflow (CDOWF) | If the client or application being installed needs direct access to CDOWF, the installer should verify that the computer is an Exchange server, and that CDOWF is properly installed on the computer. |
| Exchange OLE DB Provider (ExOLEDB) | If the client or application being installed needs access to ExOLEDB, the installer should verify that the computer is running Exchange, and that Exchange manages storage groups/databases on the server. |
| Exchange Store Event Sinks | Registering an event sink in a folder involves creating an event registration item in the folder, setting the appropriate properties on the item, and making the event sink code available on the server. Exchange Explorer, WebDAV, and ADO can be used to register event sinks. For script-based event sinks, the Script Host Sink COM component must be registered on the Exchange server. If the event sinks are contained in a COM component, that component must be registered on the Exchange server, and configured as a COM+ application. The Exchange Explorer tool and the eshmts.vbs and regevent.vbs scripts are also available for use with Exchange event sinks. |
| Exchange Web Forms | Deploying Exchange Web forms involves copying the Web form pages onto the Exchange server, and registering them. Refer to the SDK documentation for information about registering Exchange Web forms. |
| HTTP/Web Distributed Authoring and Versioning (WebDAV) | WebDAV client applications are deployed based on their client architecture and technology. The client or middle tier communicates by means of WebDAV with an Exchange server. |
| WebDAV Notifications | Client applications that use WebDAV notifications are deployed based on their client architecture and technology. The client or middle tier communicates by means of WebDAV with an Exchange server. WebDAV notifications use UDP packets to contact the client application, and so may be unsuitable for use across the Internet. |
| Incremental Change Synchronization (ICS) | Applications that use ICS can typically be deployed by using standard application installation tools and methods. |
| Lightweight Directory Access Protocol (LDAP) | Information about this is not yet available here. |
| Messaging Application Programming Interface (MAPI) | Applications that use MAPI can be deployed to client computers by using standard software distribution technologies. |
| Outlook Object Model (OOM) | Applications that use OOM are frequently distributed as scripts, or by using standard application installation software. |
| Outlook Web Access | Microsoft® Outlook® Web Access customization and component reuse is not supported by Microsoft. |
| Exchange Rules | Applications that use MAPI can be deployed to client computers by using standard software distribution technologies. The installer should verify that the correct version of MAPI is available, and that it is configured properly. |
| SMTP Event Sinks | Applications that use SMTP events can be deployed to computers by using standard software distribution technologies. The installer should verify that Microsoft Internet Information Services (IIS) and the SMTP service are installed and configured properly. |
| Windows Management Instrumentation (WMI) providers for Exchange | Applications that use WMI can be deployed to client computers by using standard software distribution technologies. The installer should verify that WMI is installed and configured properly. Scripts can usually be copied to the destination computer. |
| Exchange Backup and Restore API | Exchange Backup and Restore API applications can be installed on server computers by using standard software distribution technologies. |
| Exchange writer for the Windows Volume Shadow Copy Service | VSS applications can be installed on server computers by using standard software distribution technologies. |
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.