Outlook Extension does not support more than one instance of Outlook on the same machine.

For customers planning to upgrade from 32-bit Outlook to 64-bit Outlook, administrators must uninstall Outlook Extension while still on 32-bit Outlook, and then install Outlook 64-bit, followed by re-installing the Outlook Extension.

If the above upgrade procedure is not followed then the user is likely to encounter following error message: "Microsoft Outlook is a prerequisite of AMS Outlook Addin (x86)" when upgrading or uninstalling the Outlook Extension.

When an active user (on Outlook 2010) replies to a meeting invitation (from a user on Exchange 2010) and includes text in the body of the response, the recipient (on Exchange 2010) does not receive the response message text.

This was confirmed as a bug with Exchange 2010.

If two instances of Outlook Extension attempt to access the same mailbox at the same time, each instance will pick up different messages. This can confuse users who will not see all messages in both instances.

Meeting requests sent using the Outlook Extension in the Active State do not show meeting details when accessed on the Access Email Archive page. Only regular text messages can be rendered on the Access Email Archive page.

During an activation, read/delivery receipts require user to click Send/Receive button in order to be delivered.

During an activation, the New Mail icon does not display in the task bar.

Because of the way Microsoft encodes new lines in the Description field, meetings created using the Outlook Extension sometimes display n characters in the text when they are restored by the RecoveryManager. This is purely a cosmetic issue.

For example, instead of Meeting Request for Monday 4/23 - 11:00 -11:30, the invitation reads \nMeeting Request for Monday 4/23 - 11:00 -11:30\n.

When creating meeting invitations, you can choose conference rooms as recipients (required or optional) but cannot assign them as resources until Outlook is back online.

The data center validates email addresses when attempting to send a message. If the address is invalid per RFC-822 specifications, the data center fails to send the message, and it remains in the Outlook Outbox during an activation. By contrast, Exchange itself would attempt to send the message even if the address did not conform to RFC-822.

If a client-side rule (such as move a message from a user on Exchange to a folder) is based on an Exchange address, the rule may not be processed consistently. Rules must use SMTP addresses to behave as expected.

Outlook’s All Subfolders button does not apply to Outlook Extension Search. Outlook Extension Search searches only the selected folder in the Aurea Archive Store folder structure. If the currently selected folder happens to be the root Aurea Archive Store folder, the entire archive is searched.

After enabling a user for Folder Synchronization, archived email messages may not be immediately available in Outlook Extension Search results. Changes to folder structure and message location are synchronized on a schedule established by AMS administrators. Day to day changes to hierarchy or message location may take 24 hours to appear.