It is a common practice to maintain server-side builds of the Cdo.dll file on the BlackBerry Enterprise Server or the GoodLink Enterprise Edition server. These builds match the Cdo.dll file that is on the servers that are running Exchange Server in the organization.
Although this practice does not cause problems, it is unnecessary from a technical perspective. If a CDO-related problem exists on a BlackBerry Enterprise Server or on a GoodLink Enterprise Edition server, you must update only the Cdo.dll file that is on the BlackBerry Enterprise Server or the GoodLink server. To update the Cdo.dll file on the Exchange server will not affect the problem.
In the Microsoft Knowledge Base, CDO-related hotfix articles may state that the problem is related to �a Collaboration Data Objects (CDO)-based application.� This statement indicates that the fix must be installed only on the server on which the application runs. Most of the time, this server is the BlackBerry Enterprise Server or the GoodLink Enterprise Edition server.
Although fewer problems occur with MAPI-related files, the same principle applies. If a MAPI-related problem exists on a BlackBerry Enterprise Server or on a GoodLink Enterprise Edition server, you have to update only the file that is on the BlackBerry Enterprise Server or that is on the GoodLink server.
Microsoft Customer Support Services can help with questions about specific issues, and can advise you about where to apply a hotfix for your specific CDO-related issue.
For a list of Microsoft Customer Support Services telephone numbers, visit the following Microsoft Web site:
For more information about how CDO and MAPI work together to communicate with Exchange Server, with Outlook, and with third-party products, visit the following Microsoft TechNet Web page:
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.