When you have trouble using endpoint protection, patch management, or remote execution in LogMeIn Resolve, make sure the system time on your devices is accurately set.

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 Synchronize time step to the list on the left.
4. Click Next.
5. From the list of Devices define the devices or a group of devices that will receive the script.
   Tip: Device groups are dynamic: when you add a device to a group, it will be included in all scheduled remote execution jobs for that group. Likewise, removing a device from a group will exclude it from future scheduled jobs. However, if you add a device to a group after a recurring remote execution job has already started, that job will not run on the newly added device.

   You can organize your devices by selecting a grouping option from the top of the list.
   
6. 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.
7. Click Next.
8. Name the job in a way that is easy to remember later on.
   Optionally, with a LogMeIn Resolve Complete 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.
9. 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 Queue time drop-down.
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 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.