Deployment in an Organization

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

Installing for the First Time

To deploy Antidote 12, you must create a new Intune app for it.

Complete these steps in your Microsoft Intune admin center. To learn more, see Microsoft’s Win32 app management in Microsoft Intune guide.

Creating app packages generated all required files. They can be found in the extracted installation folder Antidote_12.y_B_n_Installation.

  1. In the Apps > All apps view, select Other > Windows app (Win32) to add a new app.

  2. On the App information page:

    1. Select the Antidote12.intunewin file that was generated previously.
    2. Make sure these fields are filled out as follows:
      • Name: Antidote 12
      • Publisher: Druide informatique inc.
      • Version: Automatically obtained from the installation package
      • Information URL: https://www.antidote.info
      • Developer: Druide informatique inc.
      • Logo: Download and use this icon :
    3. Fill out the other fields according to your policy.
  3. On the Program page:

    1. Change Install command to powershell.exe -ExecutionPolicy RemoteSigned -WindowStyle Hidden -File Installer-Antidote.ps1.
    2. Change Uninstall command to powershell.exe -ExecutionPolicy RemoteSigned -WindowStyle Hidden -File Desinstaller-Antidote.ps1.
    3. Set Install behavior to System.
    4. In the Device restart behavior field, select Determine behavior based on return codes.
    5. Ensure the following return codes are set properly:

      Return code Code type
      0 Success
      1707 Success
      3010 Soft reboot
      1641 Hard reboot
      1618 Retry

    Each installation or update requires a reboot. Ensure you have enabled the Restart grace period of the app’s assignment to prevent users from losing data.

  4. On the Requirements page, fill out the fields with the following information:

    • Operating system architecture: 64-bit only
    • Minimum operating system: Windows 10 21H2
    • You can also fill out the following optional field:
      • Disk space required (MB): 7500 (for the bilingual edition) or 6000 (for one language)
  5. On the Detection rules page:

    1. In the Rules format field, select Use a custom detection script.
    2. In the Script file field, select the Detecter-Antidote.ps1 script.
    3. Select No for Run script as 32-bit process on 64-bit clients and Enforce script signature check and run script silently.

    To be compatible with every Windows display language, all scripts are UTF-8 encoded with a BOM. The script content display may contain characters that appear to be incorrect, especially at the beginning of the file. You can disregard these anomalies.

  6. On the Supersedence page, add the “Previous Antidote” app created when uninstalling previous editions and select Yes for the option to Uninstall the previous version.

    If you deployed a previous edition of Antidote using Intune, add the latest edition of Antidote you deployed instead and select Yes for the option to Uninstall the previous version.

  7. On the Assignments page, assign the app to deploy it or make it available.

    Make sure to enable and configure the Restart grace period for all assignments to prevent users from losing data.

    If you provide your users access to Antidote 12 using the Available for enrolled devices assignment, you must enable Auto-update. This will enable automatic updates for installations made using the Company Portal. If you do not enable this option, your users will need to manually install each new version.

  8. Review the app configuration.

  9. Create the app. This will start the package upload. Please note that the package ranges between 1.5 GB and 2 GB, so the upload may take some time.

A pre-existing installation will be detected and deemed valid if all required modules are installed and the installed version of Antidote corresponds to, or is newer than, the one you are deploying. In this case, no changes will be made to the existing installation.

If the installation is not validated, it will be updated, missing modules will be installed and unnecessary modules will be uninstalled. Modules with a more recent version than the one deployed with Intune will be reinstalled with the version deployed.

If the app installation or uninstallation fails, the following files are relevant to include in the diagnostics collection:

%PROGRAMDATA%\Microsoft\IntuneManagementExtension\Logs\IntuneManagementExtension.log
%PROGRAMDATA%\Druide\logAntidote12.txt
%PROGRAMDATA%\Druide\logInsAntidote12.txt
%PROGRAMDATA%\Druide\logInsAntidote12_Module_Français.txt
%PROGRAMDATA%\Druide\logInsAntidote12_English_Module.txt
%PROGRAMDATA%\Druide\logInsAntidote12_Connectix.txt
%PROGRAMDATA%\Druide\logDesAntidote12.txt
%PROGRAMDATA%\Druide\logDesAntidote12_Module_Français.txt
%PROGRAMDATA%\Druide\logDesAntidote12_English_Module.txt
%PROGRAMDATA%\Druide\logDesAntidote12_Connectix.txt

To learn more, see Microsoft’s article on Troubleshooting Win32 app installations with Intune.