Deployment in an Organization

Deployment in an Organization / Installing the Software—Administrators / Automated Deployment on Multiple Devices / Deployment With Microsoft Intune / Prerequisites

Deployment With Microsoft Intune

Before Starting

  • Installation with Intune is silent—no user interaction required.
  • As a result, using the Deployment Manager is essential. See Configuring and activating to learn more.

General notes

Installing Antidote 12 involves up to four MSI files: one for the Antidote 12 application, one for the Connectix 12 application and one each language module (English and French) if applicable.

Deploying Antidote 12 using the MST transform file allows for the following:

  • Entering the serial number and quota code a single time
  • Predetermining integrations with the supported software
  • Setting personalization options (questions answered by each user the first time they launch Antidote)
  • To avoid conflicts between different versions, you should not install or enable the Download Assistant when deploying Antidote with Intune.

Personalizing Antidote

When first launched in each user account, Antidote asks a few personalization questions to adapt the corrector to the needs of its user. The answers can be changed at any time thereafter using Antidote’s settings panels (Resources > Options). The answers to these questions can be defined in an MST configuration file. This file must be passed as a parameter when (installing Antidote 12).

  • One of the personalization questions asks if you want to apply rectified spelling, which proposes an alternative, more contemporary way of writing certain French words. For more details, see the “Rectifications” section of the French guide “Orthographe” in Antidote and the Spelling rectifications panel page of the Antidote 12 user guide. When in doubt, select “both”. This choice can be modified at any time by the user.
  • To enter the serial number and the quota code only once (rather than on each workstation), you can use an MST configuration file, which requires local installations using this transform file (see Deploying the Original MSI File). It is also possible to copy and paste the serial number in the first box when prompted.