Cisco Unity

Cisco Unity and Microsoft Exchange

Document ID: 15366

Updated: Jan 10, 2006



This document describes which Cisco Unity versions are supported with various Exchange versions.

Refer to Cisco Technical Tips Conventions for more information on document conventions.

Q. How does Unity Enterprise Unified Messaging work with Exchange 2000?

A. Cisco Unity 2.X cannot be installed directly on top of Exchange 2000 or in an Exchange 2000 environment.

Cisco Unity 3.X and Cisco Unity 4.x are supported with Exchange 2000. Refer to System Requirements, and Supported Hardware and Software for more information on supported environments for these versions.

Q. In a Cisco Unity server, what is the significance of the M drive (M:) which has an MBX folder with a copy of all of the mailboxes?

A. The M drive (M:) is a Virtual drive that maps the D drive (D:) of the system. Microsoft Exchange has a feature called Installable file system (IFS) which creates this Virtual drive while installing Exchange. If you check the disk size for the D and M drives, you will find that they are exactly the same.

Note: If you delete the MBX folder or the M drive, it can cause the exchange to not work properly.

Q. Currently, I use Micosoft Exchange 2003 with Cisco Unity version 4.0(5) and I plan to update Exchange 2003 to Exchange 2007. Is this possible?

A. Unity 4.0(5) does not work with Exchange 2007. Your only option at this point is to upgrade to at least Unity 5.x in order to support Exchange 2007. Refer to Upgrading Cisco Unity 4.x Software to the Shipping 5.x Version for information on how to upgrade to Cisco Unity 5.x.

Q. Which is the Exchange version supported with Cisco Unity 7.0?

A. Cisco Unity unified messaging integrates transparently with Microsoft Exchange. This allows you to handle all your messages (email, voice, and fax) through a single inbox using the Outlook email client. Microsoft Exchange 2007 and Outlook 2007 IMAP are supported with Cisco Unity 7.0. Refer to Cisco Unity 7.0 for Microsoft Exchange for more information.

Related Information

Updated: Jan 10, 2006
Document ID: 15366