You can install and update Windows applications on remote computers.
Important: To use this feature, the user must be authenticated with zero trust authentication, which serves the security of the session. Authentication is required only once when you run a Remote Execution step.
- On the 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.
- On the Create job page, choose the platform where you want to run automation steps.
- Add the relevant step to the list on the left.
- To install a new app, add the Winget install step.
- To update and existing app to the latest version, add the Winget upgrade step.
- Type the Application id and Version information to the relevant fields.
To get this information, open a command prompt and type
winget search <name of the application>. For example,
winget search notepad. If you do not specify a version, you'll get the latest version of the application.
- Click Next.
- From the list of Devices define the devices or a group of devices that will receive the script.
- Optional: Select Add filters at the top of the device list to refine your list. You can filter devices by connection status, zero trust status, BitLocker encryption type, and categories, such as labels and tenants.
- Click Next.
- Name the job in a way that is easy to remember later on.
Optionally, with a
LogMeIn Resolve Premium plan 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.
- Optional: Toggle Retry job for offline devices to let LogMeIn Resolve keep trying to rerun the job on devices that come back online. You can set the retry interval for up to 24 hours in the Retry time drop-down.
- 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 LogMeIn Resolve waits two hours for the script to finish on the remote computer. When the script finishes, LogMeIn Resolve 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.