License editions: To understand the applicable license editions, see Plans & Pricing.
Overview
The mass deployment token is a security mechanism used to ensure that inSync Master processes activation requests from authentic clients. During integrated mass deployment (IMD), when you are installing inSync Client on user devices by using an automated installation tool, you must include the mass deployment token as a parameter for installation. After the user logs on to the device, the inSync Client sends an authentication request along with the user credentials to inSync Master. This also includes the mass deployment token. inSync Master authenticates only those requests that have a valid mass deployment token.
Consider the following guidelines when you generate a mass deployment token:
Once you generate a mass deployment token, all previous tokens can still be used until they reach their expiry date. During the installation of inSync client, always add the most recently generated mass deployment token.
You can enable an expiry date for a mass deployment token. The inSync Master does not authenticate any request that has an expired token attached to it.
Procedure
Steps to generate a new mass deployment token -
On the inSync Management Console menu bar, click on Endpoints.
Click on Mass Deployment.
Click on the 3 dots on the top right corner and click on “Generate New Token”.
4. The “Mass Deployment Token” window appears -
5. To set an expiry date for the token, select the “Enable expiry date” check box, and then select the expiry date in the Expiry Date field.
6. To disable expiry date for the new token, you can keep the “Enable expiry date” option as unticked.
7. Click “Generate Token”.
8. A new activation token will be generated. Copy the token to a text file or keep it handy. This token will be required during the deployment of the inSync Client on user devices using the Mass Deployment script.
9. Click Done.
📝 Note
A new token is auto-generated after expiry and is valid for 90 days. The IMD command gets updated with the new token. Once the new token is generated, the token used in the last generated command will not get updated automatically.