AvMsgStoreMonitorSvr (the service that houses ExchangeMonitor). Exchange logs this
whenever another account logs into a mailbox that is not its own, even if it has rights to do
so; thus, this is not a message to be concerned about:
Windows 2000 User LINDBORGLABS\Administrator logged on to
EAdmin@lindborglabs.thinkpad.com mailbox, and is not the primary Windows 2000
account on this mailbox.
Another (and perhaps unknown) job of ExchangeMonitor is to detect when an Exchange
mailbox of a Unity subscriber has been moved. It is not uncommon for a network adminis-
trator to move the mailbox of a give Unity subscriber from one location to another. When
this happens, Directory Monitor detects the change on that subscriber object and writes the
change into SQL. Writing the change into SQL sets off a special trigger, and information
about the subscriber is written into a special Moved Mailbox table. At the same time, the
trigger sets off an event that a thread in ExchangeMonitor has been waiting on. When
this event is ﬁred, ExchangeMonitor reads the Moved Mailbox table to gather the relevant
information on the recently moved subscriber’s mailbox. ExchangeMonitor then logs out
the old mailbox of that subscriber and logs into the new mailbox while reregistering for
change notiﬁcations of that new inbox.
In the case of Domino, the Message Store Monitor actually registers for changes on
any inboxes that it is interested in through the Domino Uniﬁed Communications Service
(DUCS) interface on each Domino server that houses one or more Unity subscribers. When
changes have happened on Unity subscriber inboxes, a message count packet is sent to the
Unity server. This contains data wrapped in XML, signifying the user and the type of change
that occurred. When any message is added, removed, or modiﬁed, the Message Store
Monitor is notiﬁed of this change and pushes the appropriate event onto the notiﬁcation
queue in the same way the Exchange Message Store Monitor does. At startup, Unity logs
into each user’s mailbox and synchs. After that, it is simply a matter of adjusting as
necessary based on change events for each user’s mailbox.
Unity uses MAPI to send messages and interact with subscribers homed on MS Exchange.
In a lot of ways, Unity behaves as a normal MS Outlook client. In most ways, however,
Unity’s use of MAPI is truly server-based and more optimized than the normal Outlook
client. The optimizations are made to the normal MAPI proﬁle that Unity creates and uses
during installation. These optimizations are done so that Unity can log onto many mail-
boxes at once and register to receive notiﬁcations of changes on many inboxes (Exchange-
Monitor uses the same MAPI proﬁle as the MAL).
Microsoft Outlook is no longer supported on the Cisco Unity server as of version 3.x.
Instead, the Exchange 5.5 Administrator program is required on the Unity server for