You can upload .msi files to allow for silent MSI uninstallation.

1. On the Devices > Remote Execution page, select Create new job.
   Can't find the page in the left menu? That's probably because the Devices menu is collapsed. Click the arrow to expand it.
   
2. On the Create job page, choose the platform where you want to run automation steps.
3. Add the MSI uninstallation step to the list on the left.
4. Click Upload to upload the .msi file of your choice.
   Note:

   • You must upload the same MSI file that you have used to install an application on remote devices.
   • You can only upload an MSI file that has a built-in uninstallation feature.
   • You can reference the file from the script. You can upload one file per job with a maximum size of 1GB. Only .msi files can be used.
5. You can add Optional parameters when running an MSI installer. These must be silent options that do not require user interaction. Otherwise, uninstallation may not finish.
6. Click Next.
7. From the list of Computers define the devices or a group of devices that will receive the script.
   You can organize your devices by selecting a grouping option from the top of the list.
   

   Important: The silent switch is automatically added to allow for the silent uninstallation of the MSI. You can set additional official and custom MSI parameters if required.
8. Click Next.
9. Name the job in a way that is easy to remember later on.
   Optionally, you can schedule jobs up to one year in advance. To do so, toggle Schedule this job and set the time and date for the job to run. In the Date and time field, either type a date or click the calendar icon to choose it from a date picker.

   Remember: You can select offline devices for scheduled jobs, but when a job runs, devices must be online; otherwise, the job will fail on that device. Scheduled jobs run on each remote device's local time.
10. Click Run.
    Note: A preset timeout pertains to both the job and the step.

    A timeout for every step is set to two hours, meaning that GoTo waits two hours for the script to finish on the remote computer. When the script finishes, GoTo starts the next step and waits another two hours for that step to finish. If a step does not finish on a remote computer in two hours, then it times out and the whole job fails.