Uninstalling a Previous Edition
If you deployed a previous edition of Antidote using Intune, you do not have to recreate this app, and you do not need to remove the existing app for the previous editions of Antidote. A supersedence relationship between the previous editions of Antidote and Antidote 12 will be sufficient.
You can uninstall a previous edition of Antidote in two ways: immediately on all devices before adding Antidote 12 to Intune, or when installing Antidote 12. Both options require a new app representing the previous editions to be created in Intune so they can be detected and uninstalled.
The instructions below are for uninstalling previous editions during installation. Green boxes provide instructions for immediately uninstalling them.
Complete these steps in your Microsoft Intune admin center. To learn more, see Microsoft’s Win32 app management in Microsoft Intune guide.
Applications that are currently installed on a device should already appear in the list of the discovered apps view: Apps > Monitor > Discovered Apps. To learn more, see the Intune discovered apps guide.
Creating app packages generated all required files. They can be found in the extracted installation folder Antidote_12.y_B_n_Installation
.
-
In the Apps > All apps view, select Other > Windows app (Win32) to add a new app.
-
On the App information page:
- Select the
PrecedentsAntidote.intunewin
file that was generated previously. -
Make sure these fields are filled out as follows:
-
Name: Previous Antidote
-
Description:
Previous editions of Antidote - Antidote RX - Antidote HD - Antidote 8 - Antidote 9 - Antidote 10 - Antidote 11
-
Publisher: Druide informatique inc.
-
App Version: 11
-
Information URL: https://www.antidote.info
-
Developer: Druide informatique inc.
-
- Fill out the other fields according to your policy.
- Select the
-
On the Program page:
- Change Install command to
powershell.exe -ExecutionPolicy RemoteSigned -WindowStyle Hidden -File Installer-PrecedentsAntidote.ps1
. - Change Uninstall command to
powershell.exe -ExecutionPolicy RemoteSigned -WindowStyle Hidden -File Desinstaller-PrecedentsAntidote.ps1
. - Set Install behavior to System.
- In the Device restart behavior field, select Determine behavior based on return codes.
-
Ensure the following return codes are set properly:
Return code Code type 0 Success 1707 Success 3010 Soft reboot 1641 Hard reboot 1618 Retry To immediately uninstall all previous editions of Antidote, use this table as a reference instead:
Return code Code type 0 Success 1707 Success 3010 Hard reboot 1641 Hard reboot 1618 Retry This will force a reboot after uninstalling the previous editions and will clean up the integrations.
- Change Install command to
-
On the Requirements page, fill out the fields with the following information:
- Operating system architecture: 32-bit and 64-bit
- Minimum operating system: Windows 10 1607
-
On the Detection rules page:
- In the Rules format field, select Use a custom detection script.
- In the Script file field, select the
Detecter-PrecedentsAntidote.ps1
file. - 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 safely disregard these anomalies.
-
On the Assignments page, do not assign the app. The previous editions of Antidote will be uninstalled using a supersedence relationship when you install Antidote 12.
To immediately uninstall all previous editions of Antidote, assign Uninstall to the app and enable the Restart grace period. If the Restart grace period is not enabled and configured, devices will immediately restart and users may lose data.
-
Review the app configuration.
-
Create the app. This will start the package upload.
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\logPrecedentsAntidote.txt
%PROGRAMDATA%\Druide\logDesAntidoteRX.txt
%PROGRAMDATA%\Druide\logDesAntidoteHD.txt
%PROGRAMDATA%\Druide\logDesAntidote8.txt
%PROGRAMDATA%\Druide\logDesAntidote9.txt
%PROGRAMDATA%\Druide\logDesAntidote9_Module_Français.txt
%PROGRAMDATA%\Druide\logDesAntidote9_English_Module.txt
%PROGRAMDATA%\Druide\logDesAntidote10.txt
%PROGRAMDATA%\Druide\logDesAntidote10_Module_Français.txt
%PROGRAMDATA%\Druide\logDesAntidote10_English_Module.txt
%PROGRAMDATA%\Druide\logDesAntidote10_Connectix.txt
%PROGRAMDATA%\Druide\logDesAntidote11.txt
%PROGRAMDATA%\Druide\logDesAntidote11_Module_Français.txt
%PROGRAMDATA%\Druide\logDesAntidote11_English_Module.txt
%PROGRAMDATA%\Druide\logDesAntidote11_Connectix.txt
To learn more, see Microsoft’s article on Troubleshooting Win32 app installations with Intune.