Articles in this section

See more

Installing Exclaimer Exchange Transport Agent (on Windows Server Core)

Avatar
Exclaimer Support
  • Updated
Follow

Relevant Products: Exclaimer Cloud - Signatures for Office 365

To make use of the Exchange On-Premises feature, you need to install the Exclaimer Exchange Transport Agent.


This article describes the steps on how you can install the Exclaimer Exchange Transport Agent on Windows Server Core, and it consists of the following sections:

Pre-requisites

Before you install the Exclaimer Exchange Transport Agent, please ensure you have: 
  • Windows Server 2012 and up
  • Exchange 2013 CU22 CU23, Exchange 2016 CU18 CU19 CU20 and Microsoft Exchange 2019 CU7 CU8 CU9.
  • A configured Exclaimer Cloud: Signatures for Office 365 Subscription
  • Azure AD Connect configured and synchronizing
  • A Domain Administrator account
  • PowerShell 4 and .Net Framework 4.7.2 installed

NOTE: Exclaimer Support is only provided for the versions listed here.


Retrieving the Exclaimer Exchange Transport Agent

Follow these steps to retrieve the Exclaimer Exchange Transport Agent: 

  1. Click the Download link highlighted below (Exclaimer Exchange Transport Agent) to download the latest version of the Exclaimer Transport Agent onto your computer, then copy the downloaded files to each of your mailbox servers.



  2. Click New Key, to create a new API Key.



    The Add API Key window is displayed.
  3. Enter a descriptive name for the new API Key.



  4. Click OK to create the key, else click Cancel to close the window without creating the new key.
    The new API Key is displayed in the API Keys list.
    Tip! 
    At this stage,     you copy the API key on a Notepad as the API Key is displayed in full. Once you exit from this window the API key is encrypted and you cannot copy it. And, once it is encrypted, the only solution to proceed with the installation is to create a new API key. You will need the API Key when you enter the first parameter details in PowerShell.

    You can also copy the Service Uri on a Notepad as this will make it easy for you to copy the path when you enter the second parameter details in PowerShell.

    This concludes the steps you need to do on the portal.

Installing the Exclaimer Exchange Transport Agent

Follow these steps to install the Exclaimer Exchange Transport Agent on Windows Server Core:

  1. Once the files have been successfully downloaded, open the Exchange Management Shell.

  2. Enter the command to the folder path where the file has been downloaded. 

    cd 'C:\Users\<username>\Downloads'

    Note: In most cases, Windows stores the Downloads folder under your user profile. To search for the Downloads folder quickly, type '%userprofile%\Downloads' in the File Explorer's address bar. 




  3. Enter the following command to run the installer:
    msiexec.exe /i .\ExclaimerCloudForExchange.msi

    Follow the steps onscreen to complete the installation.

Additional Install Options

As it is a Microsoft Installer (MSI), there are a number of values you can pass to the MSI when installing it via msiexec to allow for an install that requires little graphical interaction. 

The different parameters you can pass in the MSI are listed below with examples:

Name  Required  Description
IMPRINTFRONTEND_URL Yes The URL is given in the Portal - this is the address of the imprint server your emails will pass through in order to receive a signature.

For more information, see Service Uri in Exclaimer Cloud Signatures for Exchange.
API_KEY Yes The API Key you created within the Portal -this needs to be validated in order to route an email to the Exclaimer service.

For more information, see Service Uri in Exclaimer Cloud Signatures for Exchange.
INSTALLFOLDER No The location where the routing agent will be installed.

We recommend it to be on the root drive of the server, that is C:\Program Files\
ACCEPTED_SENDERS No This is a comma-separated array of SMTP email addresses. It is used to limit the routing agent to a specific list of sender addresses that will be processed.
ACCEPTED_GROUPS No

This is a comma-separated array of distribution groups. It is used to limit the routing agent to a specific list of distribution groups whose members will be processed.

 


Related articles