The JobScheduler Agent should run jobs for Windows for a specific user account. The effictive implementation is to be decided on:
- For user specific start of a process, the API function CreateProcessAsUser can be used.
- The user under which Job Scheduler is running requires the permission "Replacing of a token at process level".
- See also http://msdn.microsoft.com/de-de/library/cc784623%28v=ws.10%29.aspx
JS-1595being ready a .NET/PowerShell interface is available that can access user credentials from the Windows Credential Manager.
- Credentials are managed independently from JobScheduler. A most simple way is used of the shell command cmdkey.
- Credentials are managed for individual machines or at enterprise level.
- Credentials are assigned to a job by use of their target name. The effective account/password are not known to JobScheduler.
- A new attribute <job credentials_key="..."> is introduced.
- A value of credentials_key is a "target name" in the Windows Credential Manager
- A new attribute <job load_user_profile="true|false"> is introduced.
- Default: false
- Loads the specified user's profile.