This document provides instructions for the installation of Exact Exchange Integrator for Exchange Online (Office 365/Hosted email) users and it is meant to be used by Pilot customers only!
Note that Office 365 integration is not yet officially supported by Exact. Therefore, if you will have any issue with installation or if you will find any issue while running this solution please send email to Sanja.djuretic@exact.com

Installation

Install Exact Exchange Integrator based on the document How-to: Installing Exact Exchange Integrator (Microsoft Exchange 2010) for product update 250 onwards

When installing, please pay special attention to the following:
-Location for the installation of Exact Exchange Integrator solution MUST be Exact Synergy Enterprise installation folder 
-The SQL server instance name is case-sensitive. Example: FSASQL01\FSASQL.  The synchronization will not working properly if the server name is entered as fsasql01\fsasql
-During installation of Exact Exchange Integration solution make sure to select Use Autodiscover when asked for the Exchange Web service Url
-Select Hosted for the Exchange Server Installation type
-In the Service account section of the installation enter local domain UserName for the service account, for example “<domain>\<service account>”
Note: UserName within Exchange Online environment is the same as email address in most cases with exception on proxy domain address usage.  For the installation we don't use Exchange user name but local domain UserName.
-Service account password has to be the same in Synergy and Exchange Online/Hosted environment. Don't forget to encrypt the password as instructed in the main installation document after the installation has completed.

-To setup impersonation ignore the instructions from the installation document (mentioned above) and follow instructions from the document: HowTo: Assigning Application Impersonation in Exchange Online/Office 365 - This is the most Office 365 specific part!

-Make sure that the Autodiscover is set up correctly. For the test and troubleshooting you can make use of Microsoft tool:  Remote Connectivity Analyzer (RCA) and document Correcting Autodiscover and DNS settings


Once the installation is completed please make following change in the 'Exact.MacroManager.Exchange.config':
Browse to the Exact Exchange integrator \ XML folder, and open 'Exact.MacroManager.Exchange.config' file using the notepad. Look for the <macro id="eseauthn">, change the value to 1.
The reason you have to make this change in 'Exact.MacroManager.Exchange.config' is that Basic authentication is a MUST for Exchange Online. In notation of Exact Exchange Integrator,  1 means 'Exact Synergy Enterprise is using the Basic authentication'.
For the same reason you might have to make a change in IIS. Please make sure that Basic Authentication is “Enabled” for Synergy application.

Be aware of the Exact Exchange Integrator limitation for the use of service account (fixed user) as a test account - please don't use service account for the testing of calendar synchronization, it is not supported!
Currently, Exact Exchange integration solution doesn’t support calendar synchronization for the service account (fixed user) from Synergy to Exchange/Outlook. This apply not only to the situation when user is logged in to Synergy as a Service account but also if logged in as Normal user delegated via Service account.
Note: We don’t advise using Service account as a ‘Normal’ Synergy user, but if you do, than appointments created in Synergy for that account won’t be synchronized to the Exchange.

About Autodiscover

The Autodiscover service uses a user’s email address and password to automatically configure a user profile. This profile can be configured whether the mailbox is located on-premise, hosted or in Office 365.

For custom Office 365 domain, e.g. office365.company.com there needs to be a CNAME record created for the service address space office365.company.com that points to autodiscover.outlook.com

If you have both internal and external DNS records then they both have to be configured correctly for Autodiscover to work properly!

Troubleshooting

-Make sure you have installed the latest ExchangeIntegrator.msi. This can be found in the cab folder of the Exact Synergy Enterprise installation folder.

-Missing or incorrect password for service account in config files can cause 401 error and/or "The Autodiscover service couldn't be located." error

-In case of missing Synergy->Outlook synchronization (missing messages in eseexchqueue and missing syn2out synclog) most likelly there is something wrong with Synergy’s notification system or the Url you use for creating appointments can't be reached on the Synergy webserver itself.
Here again, make sure you don't test calendar syncronization using service account hence no messages in the queue will be created.
Check if the Url you use on the client to create appointments in Synergy (for example: https://www.domain.com/synergy) can be reached on the Synergy webserver itself.

-You can use simple tool "Exchange Test Application: ExchangeTestApp" to test if Impersonation and Autodiscover are functioning correctly.
Make sure you run this tool from the web server where Exact Exchange Integration solution is installed.
Unzip the ExchangeTestApp.zip attachment and enter test and service account details in ExchangeTestApp.exe.config file – replacing the XXXXXXXX values and eventually true/false values of other attributes.
Then just run the exe and observe results (url and your calendar entries) and wait until you see the message “Press a key to exit”.Application will create a number of txt/log files at the installation directory and we will need to check them only if you get the error while running this app.
Note: It might happened that this application gives correct result when you run it from your machine but you still have issues with Autodiscover. In that case run this app from the server where your solution is deployed and check the results again. You might need to add/correct DNS SRV record on that server.

-DNS settings related to eventual Autodiscover issues
For test and troubleshooting you can make use of Microsoft tool:  Remote Connectivity Analyzer (RCA)
More information: Correcting Autodiscover and DNS settings, External DNS records for Office 365

Example for SRV record:
<Name of the cert that you have> = <ip of your CAS>
Service: _autodiscover
Protocol: _tcp
Port Number: 443
Host: <name of the cert that you have> 

Note: If you have multiple DNS zones you can create multiple SRV records in all different DNS zones that leads to single name, and you will need only one certificate for this name.


-Combination of Autodiscover issue and Error 401
Although Remote Connectivity Analyzer tool might show that the Autodiscover works when you run it from your machine it doesn’t always mean it will work on the web server where Exact Exchange Integration solution is running. With our first pilot customer I have seen that Autodiscover didn’t work because of missing DNS SRV record. Because of that they tried installation with Fixed Url but  that didn’t work because our solution is always using default credentials with FixedUrl (will be fixed) so Error 401 was thrown.

-Authenticate problems by using of NTLM

Known Issues

Calendar items deleted in Outlook calendar were not synchronized with Synergy calendar. This is fixed in Synergy 254.