...
The Windows JobScheduler is installed as a Windows service with the local system account.
The service has the name sos_schedulerscheduler_id_ where the scheduler_id was set during the setup.
...
You have multiple options to start/stop the JobScheduler service. You need elevated administrator permissions to start the service.
- using shortcuts in the start menu
No Format "SOS JobScheduler -> -id[scheduler_id] -> Start service" "SOS JobScheduler -> -ih1. [scheduler_id] -> Stop service"
- using JobScheduler start script (./bin/jobscheduler.cmd)
No Format the JobScheduler start script calls the net.exe and asks for elevated administrator permissions if you start the JobScheduler service the JobScheduler start script calls the JobScheduler command <modify_spooler cmd'terminate'/> to stop itself open a _Command Prompt_
Code Block language bash > bin\jobscheduler.cmd start_service > bin\jobscheduler.cmd stop
- using Windows services dialog
No Format select the service _SOS JobScheduler -id=[scheduler_id]_ and use the function start or stop in the context menu
- using net.exe
No Format open a _Command Prompt_ with elevated administrator permissions
Code Block language bash > net.exe start sos_scheduler_[scheduler_id] > net.exe stop sos_scheduler_[scheduler_id]
- using sc.exe
No Format open a _Command Prompt_ with elevated administrator permissions
Code Block language bash > sc.exe start sos_scheduler_[scheduler_id] > sc.exe stop sos_scheduler_[scheduler_id]