Setting up a domain account for the Scheduler service
The Scheduler service is installed to run under the local Windows™ system account, which is only applicable if the service is running on the local machine. To run Scheduler that uses a Scheduler database that is installed on a different machine, then the service needs to log on using a domain user name and password. The user and password are set in the Windows Services application.
Directories and files | Min. permission |
|---|---|
The Scheduler directory that contains the file Scheduler.mdb | Modify |
| Scheduler.mdb | Read, Write |
Directory containing the DLLs and EXEs for iBase Scheduler | List Folder Contents |
DLLs and EXEs for iBase Scheduler | Execute |
Directory containing the file on which a file trigger is created--- no permissions are required on the file itself. | List Folder Contents |
Directory containing the batch scripts or plug-ins that are required to execute as task actions. Alternatively, you might assign List Folder Contents permission to the directory and Read and Execute permission to the files. | Read & Execute |
Data files for import or the directories that contain the data files. You require Write permission if the file is to be altered by a batch script or plug-in, and Modify permission if the file is to be deleted by a task action. | Read |
Directory containing the iBase security file. | Modify |
iBase security file | Read, Write |
iBase database directory (JET databases only) | Modify |
iBase database file (JET databases only) | Read, Write |
iBase database file (SQL Server databases only) | Read |
The Windows Services application automatically grants the domain account the permissions that are required to run services.
If you are using Windows integrated security (NTLM authentication), then the domain account needs to have permit access for the relevant SQL Server databases.