Start, stop, or restart services on Windows computers using Remote Execution.
Note: Available on Windows only.
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 Service start, Service stop, or Service restart step to the list on the left.
- Type the name of the Windows service that you want to start, stop, or restart for example Appinfo.
To find the name of a service, open Task Manager
on the remote computer and go to the
Services tab.
Note: When multiple instances of a service are running on a computer and you stop that service, all those instances will be stopped.
- Click Next.
- From the list of Devices 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.
- Click Next.
- 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.
- 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.