Automatically populating missing uninstall commands

Uninstall commands are required when exporting applications to Intune, therefore when Change360 encounters an application in Discovery that doesn't have an uninstall command it will attempt to determine and validate an uninstall command from information found during Discovery.

Detecting Uninstall commands

Uninstall commands are detected by scanning the following uninstall registry keys:

• HKCU\Software\Microsoft\Windows\CurrentVersion\Uninstall
• HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
• HKCU\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall
• HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall

And identifying uninstall commands in the following priority order:

• QuietUninstallString
• UninstallString

If no uninstall string registry keys are found the discovered executables are scanned for uninstall.exe and if found a silent uninstall command is constructed using the discovered file.

Validating Uninstall Commands

If an uninstall command can't be found or created from the discovered files the command is executed and validated by:

• Ensuring the command terminates by itself, i.e. no user interaction is required
• Checking the exit code to ensure it terminates without error
• Validating detection rules to ensure resources have actually been removed.

If successfully validated the uninstall command in the application record is updated.  For applications imported from Patch360 validated uninstall commands are fed back into the catalog to improve future imports.  If the uninstall command cannot be validated successfully then it will need to be manually updated if you want to export the application to Intune.