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
A possible workaround is to publish an application that launches the Outlook desktop app instead of Outlook published app. This is a Citrix admin's task but contact us if you need further guidance.
- Active Directory on-premises joined PCs
This process consists of only two steps:
- The Xink client package (MSI) which updates Outlook email signatures when connected with your account.
- 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).
Deploy Xink MSI client and Token
Step 2: IT Pro: Deploy Xink ADM-File via GPO Template (Xink Token ID)
Test OK using Gpupdate /force.
Need remote help? Select my time slot
How to test deployment OK
- Log in to a Citrix/RDS session as a user or login to a domain PC.
- Open the Xink client in the systray (lower right-hand corner).
- 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.
If for some reason your token is compromised it is possible to revoke it.
Go to Preferences > Downloads > "Step 2 - IT: Obtain the ADM template (HKLM registry)" and click “Revoke” to revoke an active 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' if needed.