Client Platform Requirements
Client Platform Requirements
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 Client Platform Requirements.
| Technology | What are the client requirements for using this technology? |
|---|---|
| Active Directory Services Interfaces (ADSI) | There are no special requirements for accessing Active Directory® directory service information within the user's domain. Cross-domain or cross-forest access may be limited by Active Directory security policies. |
| Collaboration Data Objects for Windows 2000 (CDOSYS) | CDOSYS is available on the Microsoft® Windows® 2000 Server, Windows XP Professional, and Windows Server™ 2003 operating systems. |
| CDOSYS SMTP/NNTP Event Sinks | CDOSYS is available on Windows 2000 Server, Windows XP Professional, and Windows Server 2003. |
| Collaboration Data Objects for Exchange 2000 Server (CDOEX) | If the application client uses CDOEX directly, the client must be run on the computer that is running Exchange Server. If the client accesses the application middle tier via HTTP or other network protocol, there are no special client requirements, except those defined by the application. The application middle tier must be run on the Exchange server. |
| Collaboration Data Objects for Exchange Management (CDOEXM) | CDOEXM can only be run on a computer on which the Exchange Administrative Tools are installed. Both the computer running CDOEXM and the Exchange server being accessed must be in the same Active Directory organization. |
| Collaboration Data Objects for Exchange Workflow (CDOWF) | Workflows can be designed on any computer on which the Workflow Designer for Exchange has been installed. Application clients that directly access CDOWF must be installed and run on an Exchange server. |
| Exchange OLE DB Provider (ExOLEDB) | Not applicable; ExOLEDB is not a client-side technology. |
| Exchange Store Event Sinks | Not applicable; Exchange store events are not a client-side technology. |
| Exchange Web Forms | Base client requirements are the same as those for Microsoft Outlook® Web Access. However, browser-specific features used in an Exchange Web form may limit the range of compatible browsers that can be used to access the Web form. |
| HTTP/Web Distributed Authoring and Versioning (WebDAV) | WebDAV is not a client technology. The design and implementation of the application client determines the client requirements. |
| WebDAV Notifications | WebDAV notifications use UDP packets to notify the client that the Exchange store detected a subscribed event. The subscription command specifies the UDP port on which Exchange will contact the client computer. The client application must have a UDP listener running on the port specified on the subscription, so that the events will be received. Note that normal firewall configuration blocks UDP packets, so WebDAV notifications typically only work within an intranet, or over a PPTP tunnel. |
| Incremental Change Synchronization (ICS) | ICS is not generally considered a client technology. The agent portion of the application is likely to have a user interface in which the resources for synchronization can be chosen. |
| Lightweight Directory Access Protocol (LDAP) | LDAP is not a client technology. The design and implementation of the application client determines the client requirements. |
| Messaging Application Programming Interface (MAPI) | The client application installer should verify that the proper version of MAPI is available on the computer, and that it is properly configured via the MAPISVC.INF file. |
| Outlook Object Model (OOM) | Applications that use OOM to access Exchange data require that Microsoft Outlook be installed on the local machine. |
| Outlook Web Access | Outlook Web Access customization and component reuse is not supported by Microsoft. |
| Exchange Rules | The client application installer should verify that the proper version of MAPI is available on the computer, and that it is properly configured via the MAPISVC.INF file. |
| SMTP Event Sinks | SMTP event sinks are not considered a client technology. Typical applications that use SMTP event sinks will usually not include a GUI application for configuring and monitoring the system. |
| Windows Management Instrumentation (WMI) providers for Exchange | There are no special client requirements beyond the WMI core components and the WMI application. |
| Exchange Backup and Restore API | There are no special client requirements beyond the Exchange Backup and Restore API core requirements. |
| Exchange writer for the Windows Volume Shadow Copy Service | There are no special client requirements beyond the VSS core requirements. |
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.