Advanced Tab

You have further control over how the event will run using the Advanced Tab.

RUN AS

In the Run As... section you can control the credentials System Scheduler will use when running the job.

Use logged in user credentials

This is the default choice. All jobs will run using the currently logged in users credentials. If the computer is logged out it will use the Service credentials. Remember, the System Scheduler Service does not necessarily have enough rights to run everything, by default it uses the LocalSystem account, though this account is quite powerful it is not as powerful as an Administrator account.

If you find your jobs run ok while logged in, but fail to run while logged out (and the 'Logfile.txt' indicates System Scheduler tried to run the job) then likely the problem is caused by the Service having insufficient credentials. You can change this through Control Panel - Administrative Tools - Services. Note: Make sure to only change the System Scheduler Service, do not change the System Scheduler Logon service.

Service Credentials

You can specify job always runs using the service credentials, even if a user is logged in. This is particularly useful if you know your Service has the right level of credentials to run the job and you don't want it to be affected by any logged in user credentials that may be different. Also, if the logged in user has very little rights you can use the Service to run the job using higher level rights (for instance, when using the Process Watcher event, a low level logged in user may not have the rights to terminate a particular process, whereas the System Scheduler Service running as LocalSystem may have.)

Always run as this user

This is particularly useful to run a specific application using another users credentials. You need to supply the username and password for that user. Remember, if that user ever changes his/her password the System Scheduler job will then be out of sync and will need to be updated to the latest password.

If you want to create a shortcut on your desktop to run a specific System Scheduler Event, you can do this using the separate 'RunNow.exe' program that comes with System Scheduler. This is useful if from time to time you need to run applications with elevated user privileges.

Services in NT/2000/XP/2003/Vista do not have a user profiles associated with them, so if no one is logged in certain user profile options will not be available. For example, mapped network drive letters and user defined printers are not usually available to a service as these are defined by the users logged in profile. However, if you specify to run as a specific user, you can tick the box 'Load profile settings for user', this will load some of the user specific environment such as mapped drives, home drive etc. In addition the Network Drives tab contains information on which drive letters System Scheduler will attempt to remap.

If you are running a job with the Service, and you do not wish the logged in user to see it running then you can un-tick the option Interact with the desktop if logged in, then the application will run invisibly in the background. Note some application prefer to run interactively and may not exit by themselves if run invisibly in the background.

Note: 'Run As...' is only available for 'Run Application' type jobs.

Run when Logged In or Out

Normally System Scheduler will try to run a scheduled event anytime System Scheduler is actually running. If System Scheduler is configured to run before logon on 9x/ME computers or configured as a service on Windows NT/2000/XP/2003 computers then it is possible to run events either logged on or logged off.

Sometimes there are events that you only want to run if the computer is logged on or alternatively when logged off. The third alternative is to run an event when only a certain username is logged on.

This is actually quite a powerful feature, here is a table to explain the logged in/out options.

DATE/TIME RESTRICTIONS

Stop Event

You can restrict how long an Application is allowed to run. By setting the Hours and Minutes, System Scheduler will monitor the Application and if it exceeds this time it will be terminated.

Day Types

Click Working Days for more info.

Date and Time Range

You can further control when the job is allowed to run. You can set a start date and end date, also a start time and end time.

Example 1: You may want to run a job with the main scheduling option Every Day at 7pm, however you only want it to start running daily from 1st September and stop running 30th September - you can configure the start and stop date in this date range setting.

Example 2: You may want a job to run Every Minute but only between 10.45pm and 11.15pm. You can configure the time range in this time range setting.

EVENT PROCESSING

This section gives you further control of when a job can run and post job/missed job processing.

Missed Events

If an event is missed due to the computer being switched off you can specify whether you want that job to run when the computer is switched back on:

'No Action': System Scheduler will not take any action regarding the missed job. It is missed and will be rescheduled as usual depending on the 'Schedule' setting.

'Run On Startup': will run the job automatically when System Scheduler starts up. For NT/2000/XP/2003 computers this is usually when the Service starts (before logon), for 9x/ME computers this can be before logon or after logon depending on how you have System Scheduler configured.

'Run After Logon': When the user logs on any overdue events will be run.

'Prompt After Logon': User will be prompted with a list of missed events and can choose to run or dismiss them.

Run once event

This only applies to events that are scheduled to run once. System Scheduler can automatically delete it afterwards if required. For popup reminders that are scheduled to run only once the default will be for this box to be checked, for all other events the default is unchecked.

NETWORK DRIVES

This indicates which drive mappings System Scheduler will attempt to remap before running the Application. This is particularly useful if your application has a reliance on particular drive letters being available, otherwise when running the Application under another users account of as the Service the drive letters may not be there (mapped drive letters are user specific). System Scheduler wont override existing drive mappings if the letter is already mapped.

Back to Introduction