You use the Xink Exchange Connector to configure integration between Xink Cloud and your local on-premises Exchange server when you want to keep email signatures updated for.
- Mobile devices sending emails through your Exchange server
- OWA (Outlook Web App or Outlook Web Access depending on Exchange Server version)
The Xink Exchange Connector is installed on one of your servers. It connects to Xink Cloud and pulls down users and signatures to a local SQL Server. From your local SQL Server you can access the signatures from Exchange.
Check out below infographic and Exchange Connector FAQs.
You basically need two installs:
- Xink Exchange Connector (this will pull the users and their signatures from Xink to a local SQL Server database)
- Exchange Mobile Gateway (this will install a transport agent on your Exchange Server, hence allowing to add the signature when the email is being send)
First Install Xink Exchange Connector
Download the Xink Exchange Connector installer here.
Install the file, you need to give permission for the package to be installed.
Once installed launch the program called "Configure Xink Exchange Connector" from 'Start' Menu:
The Configuration program will start elevated so you need to approve the program to start.
Windows will ask you for this permission.
This will start the main menu of the Xink Exchange Connector Configuration:
Connect Exchange Connector to the Settings database
First you need to connect to your settings database. If you are using eMailSignature already (Xink Classic on-premises product), you just need to find your connection string to the settings database. Then add the connection string to the setup program as shown here:
If you do not have a local setting database, you need to create one in a local SQL Server.
This is easy - use this SQL create script to create it and you will need to construct the connection string yourself.
This database is always referred to as the 'settings database'.
Enter the connection string in "Connect to the settings database" and click “Test” ´to test the connection as shown above.
Click “Save” to save and exit to the main menu. You have now established a connection to your local SQL Server. You need to make sure that you Exchange Server has access to this SQL Server.
Connect Exchange Connector to Xink Cloud
Next step is to connect to Xink Cloud so the Xink Exchange Connector can pull your users and signatures from your Xink Cloud account to your local settings database. To do so you need to create an API user in Xink:
- Go to http://app.xink.io and sign in with you administrator credentials.
- Go to the settings menu (the cog-icon at the top-right corner) and choose “Admins”.
- Click “API Users” in the list to the left.
- Create a new API user by clicking the “+” button at the top right.
- Assign permissions to the newly created API user. To do so click 'Admins' and choose the 'API Users' folder. Select the API user you just created and click the gear and choose 'permissions'. Now choose the correct permissions for this API user:
Now that you have created an API user you are ready to connect to Xink Cloud.
In Xink Exchange Connector enter the username and secret/password of your API user. Click “Test” to test the connection and “Save” to save your settings and exit to the main menu.
Start Importing Users and Signatures from Xink Cloud
After you are done with the configuration it is time to start the import of users in Xink Cloud to the local settings database.
To start the import, locate the file 'XinkExchangeConnector.exe' in the install directory for Exchange Connector.If you have not changed this during installation, it will be in your program files folder under sub folder "Xink Exchange Connector". You should set it up to run as a Windows scheduled task to keep the users synchronized on a regular basis, e.g. once per day.
Start the file with no parameters or switches from a command prompt.
Important note: Xink Exchange Connector will only work on machines on your domain and it must run in the context of a user that is allowed to look up users in the Active Directory.
It is necessary to run in the context of an AD user with those permissions because the Xink Exchange Connector needs to look up the SAMAccountName in your Active Directory. If it cannot look up the SAMAccountName in Active Directory it will not work.
Note that Xink Exchange Connector will always overwrite whatever is in the local database with data is imported from Xink Cloud. Set this file up to run as a scheduled task to get recent updates. Once per days is usually enough.
The Status Monitor will show you all users imported from Xink. You search for specific users by entering a search text and hitting “Enter” or clicking “Search”.
Continue to setting up the Exchange Mobile Gateway.