Email Signature Platform - Help Desk and Knowledge Base

IT Pro: Unattended deployment for AD on prem domain (Windows/Citrix/RDS)

This deployment method is designed for domain environment with more than 50 end users, Also for (Citrix/RDS) setup.
Active Directory administrators can use this guide instead of manual installation or invitation method for each employee. 

The idea behind is very simple: we provide per-machine installer (MSI-file) and policy template (ADMX-file) with application configuration. The domain administrator can deploy both centrally.

This is perfect when:

  • You want to deploy the Xink App unattended to all Outlook users.
  • You don't want Outlook (desktop) users to have any kind of interaction.
  • You don't want to deal with invitation emails and rely on users having to enter access code.
  • You want to deploy across medium or larger teams.

This process works with:

  • Outlook (Win)
  • Outlook on (Citrix/RDS) - Outlook published application (Citrix) is not supported. 
  • Active Directory as data source (AD on-prem)

This process consists of only two steps:

  1. Download the package (msi)
  2. Get your .ADMX file.

Do not just download the package and deploy it without your .ADM file. You need the .ADM file also.
FAQ - Switching from old authentication to oAuth2 (Aug 2016).
You need to uninstall any manually installed Xink client apps before installing any msi packages via GPO, Citrix etc. These packages do not work together.

Download the package and collect your ADM-file

To get the MSI package go to 'Preferences' and click 'Downloads' and click "IT: Download Xink Client (.MSI Package)"
Once you have downloaded the package file, proceed to Token Manager area. To do so click 'Token Manager' from the download section.

First step is to create domain authentication token, Click "Add" button. One token is enough in the most cases for the whole Xink account.
The token is not user-specific. Then click “Get .ADM” link to download policy template with the token embedded.  
The policy contains only one setting – “Use AD Auth” – enable it and distribute to target computers along with Xink Client MSI file.

Xink MSI client and Token ID deployment

Step 1: IT Pro: Deploy Xink Client MSI Package via GPO
Step 2: IT Pro: Deploy Xink ADM-File via GPO Template (Xink Token ID) 

Test OK using Gpupdate /force.

If you are using SCCM, you may deploy your package and write the registry keys without having to apply the template through GPO. Please refer to this KB

How to test deployment OK

You deploy the MSI package (and the ADM-file) via GPO .
If you use other deployment tools, you open ADM-file in notepad and copy and deploy HKLM registry content.
  1. Login to a Citrix/RDS session as a user or login to a domain PC.
  2. Open the Xink client in the systray (lower right hand corner):
  3. You test OK by clicking ‘Update Now’ – When you see two messages your installation is OK:

    You will receive two notifications:

    1st: Updating email signatures
    2nd: Email signatures updated

    if you only see the first message, It's commonly due to ADM-file is missing on the client. 

    Check IT Pro: Deploy Xink ADM-File via GPO Template (Xink Token ID) - Test OK using gpupdate /force.
    Also validate HKLM registry content (found when you open the ADM-file in Notepad).
    if you used other deployment method aside from described on this KB article. 

Token Revocation

If for some reason your token is compromised it is possible to revoke it.
On the same “Domain Token Manager” page click “Revoke” button for a token.
This operation cannot be undone. Once revoked, the token will no longer be valid for authentication.
A new token would be required to renew access.

And the screen with multiple tokens would look like this:

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.