Developer / Deployment Licensing
Developer / Deployment Licensing
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 Developer / Deployment Licensing.
| Technology | What product licenses are need to develop and deploy applications that use the technology? |
|---|---|
| Active Directory Services Interfaces (ADSI) | No special licensing is required for developing by using ADSI. The libraries and COM objects are installed with Microsoft Windows®. |
| Collaboration Data Objects for Windows 2000 (CDOSYS) | No special licenses are needed for using CDOSYS. Depending on your configuration, your systems may require access to an additional SMTP/NNTP server to transport messages to their destination. |
| CDOSYS SMTP/NNTP Event Sinks | No special licenses are needed for using CDOSYS. Depending on your configuration, your systems may require access to an additional SMTP/NNTP server to transport messages to their destination. |
| Collaboration Data Objects for Exchange 2000 Server (CDOEX) | Refer to your Exchange and MSDN subscription licensing agreements to determine whether additional licenses are required for the computers on which your CDOEX applications are developed and deployed. |
| Collaboration Data Objects for Exchange Management (CDOEXM) | Refer to your Exchange and MSDN subscription licensing agreements to determine whether additional licenses are required for the computers on which your CDOEX applications are developed and deployed. |
| Collaboration Data Objects for Exchange Workflow (CDOWF) | Refer to your Exchange and MSDN subscription licensing agreements to determine whether additional licenses are required for the computers on which your CDOEX applications are developed and deployed. |
| Exchange OLE DB Provider (ExOLEDB) | Refer to your Exchange and MSDN subscription licensing agreements to determine whether additional licenses are required for the computers on which your ExOLEDB applications are developed and deployed. |
| Exchange Store Event Sinks | Refer to your Exchange and MSDN subscription licensing agreements to determine whether additional licenses are required for the computers on which your Exchange store events applications are developed and deployed. |
| Exchange Web Forms | Refer to your Exchange and MSDN subscription licensing agreements to determine whether additional licenses are required for the computers on which your Exchange Web forms are developed and deployed. |
| HTTP/Web Distributed Authoring and Versioning (WebDAV) | 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 WebDAV applications. |
| WebDAV Notifications | 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 WebDAV applications. |
| Incremental Change Synchronization (ICS) | No special licensing is required for developing by using MAPI. Refer to your Exchange and MSDN subscription and other appropriate licensing agreements to determine whether additional licenses are required for the servers to be synchronized by your ICS applications. |
| Lightweight Directory Access Protocol (LDAP) | No special licensing is required for developing applications that use LDAP. |
| Messaging Application Programming Interface (MAPI) | No special licensing is required for developing by using MAPI. |
| Outlook Object Model (OOM) | Refer to your Exchange and MSDN subscription licensing agreements to determine whether additional licenses are required for Microsoft Outlook® and OOM to be used in your applications. |
| Outlook Web Access | Outlook Web Access customization and component reuse is not supported by Microsoft. |
| Exchange Rules | No special licenses are required 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 on which your application defines rules. |
| SMTP Event Sinks | No special licenses are needed for using SMTP event sinks. Depending on your configuration, your systems may require access to additional SMTP, NNTP, or Exchange servers to transport messages to their destination. |
| Windows Management Instrumentation (WMI) providers for Exchange | No special licenses are required 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. |
| Exchange Backup and Restore API | Refer to your Exchange and MSDN subscription licensing agreements to determine whether additional licenses are required for the Exchange Server 2003 servers that store the data backed up and restored by custom applications that use the Exchange Backup and Restore API. |
| Exchange writer for the Windows Volume Shadow Copy Service | Refer to your Exchange and MSDN subscription licensing agreements to determine whether additional licenses are required for the Exchange Server 2003 servers that store the data backed up and restored by custom applications that use VSS. |
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.