Outlook Extension Prerequisites and Limitations

Install the ContinuityA feature provided by GFI OneConnect that queues the emails sent and received in a Data Center and ensures that your organization can keep the mail flow even when the email infrastructure is down. Outlook Extension on systems that meet or exceed the following prerequisites.

Supported Environments

Supported operating systems (32-bit or 64-bit):

• Windows 7 SP1 or higher
• Windows 8.1
• Windows 10

Supported Microsoft Outlook versions (32-bit or 64-bit):

• 2016
• 2013
• 2010 SP1
• 2007 SP3 - This version is only supported on Windows 7 SP1.

Other prerequisites

The following are required to use the Outlook Extension:

• Microsoft Outlook must be in cached mode.
• Users must have administrative permissions on the machine where to install the Outlook Extension.

Outlook Extension Limitations

The following table describes known limitations of the Outlook Extension.

Limitation	Description
One instance per machine.	Outlook Extension does not support more than one instance of Outlook on the same machine.
When upgrading from 32-bit Outlook to 64-bit Outlook, first uninstall the Outlook Extension while still on 32-bit Outlook, and then install Outlook 64-bit, followed by re-installing the Outlook Extension.	If this upgrade procedure is not followed then the user is likely to encounter the following error message: "Microsoft Outlook 2007, or 2010 (x86) is a prerequisite of Outlook Addin (x86)". To resolve this error, the user should first downgrade back to a 32-bit Outlook version, uninstall Outlook Extension, and then install 64-bit Outlook version, followed by installing Outlook Extension.
When an active user on Outlook 2010 replies to a meeting invitation received 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 is confirmed as a bug with Exchange 2010. The recipient's Exchange 2010 server must have the following update installed to resolve this issue: Update Rollup 5 for Exchange Server 2010 Service Pack 1 (KB2582113) or Service Pack 2 for 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.	It is recommended to have only one running instance of Outlook Extension per mailbox at any time. Use WebMailA web-based email client provided by GFI OneConnect that is available when your organization's primary email infrastructure is unavailable. to access a mailbox from a different machine while Outlook Extension is running.
During an activation, read/delivery receipts require user to click Send/Receive button in order to be delivered.	During an activation, read receipts are generated and sent when a user clicks the Outlook Send/Receive button. If a user does not click Send/Receive, the receipts are delivered after recovery.
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. 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.	This is purely a cosmetic issue and the display characters should not cause any malfunction or loss of data. This is under investigation for a future release.
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.	Outlook cannot process resource requests while offline.
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.	This is an expected difference in behavior between the Outlook Extension and Exchange on the primary mail server.
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 SMTPSimple Mail Transfer Protocol (SMTP) is an Internet standard used by GFI OneGuard for electronic mail (email) transmission. SMTP by default uses TCP port 25. addresses to behave as expected.