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 a 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 a per-machine installer (MSI-file) and policy template (ADM-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 the 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 on-premises joined PCs

This process consists of only two steps:

  1. The Xink client package (MSI) which updates Outlook email signatures when connected with your account.
  2. The .ADM file (Token ID) which connects the Xink client with your Xink account (authentication).

You need to uninstall any manually installed Xink clients before installing any MSI packages. These packages do not work together.
FAQ - Switching from old authentication to oAuth2 (Aug 2016).


Download the package and collect your ADM-file

To get the MSI package go to 'Preferences':



Click Downloads and click IT: Download Xink Client (.MSI Package).
Once you have downloaded the package file, click 'Token Manager'.



The first step is to create a domain authentication token, Click "Add" button.
One token is enough in the most cases for the whole Xink account.
Then click “Get .ADM” link to download policy template with the token embedded (HKLM registry setting).  
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 authentication 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 for SCCM deployment.


How to test deployment OK

  1. Log in 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 below two messages your installation is OK:

    1st: Updating email signatures

    ...wait a few seconds...

    2nd: Email signatures updated
     
    If you only see the 1st message, the Token ID (HKLM reg) is not applied (via GPO/SCCM etc.).
    Try if gpupdate /force will fix.


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. Then click 'Add'.


And the screen with multiple tokens would look like this:

Quick Demo  

Did you find it helpful? Yes No

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