Hello,
I've been playing with the demo version for a couple days now and cant seem to get it to do what I want.

My objective is to allow users to run jobs that are scheduled on the server to run as a previledged user without giving them local admin access to the server.
Example,
Scheduled job: JOB1
Runas: domain_admin
Server: SERVER1

Now I want USER1 to be able to execute JOB1 on SERVER1 but USER1 doesn't have admin previledge.

Thanks

It is actually very simply. Create a job using any user id and in the job properties using (Run As properties) specify domain_admin for the user, doman and password. Save the job and use "Protect job" feature to set job protection level to "Run only". Now your users can run this job only. Please don't confuse how users logon to the scheduler (if security is enabled) with how jobs are run. It is a totally different game.

: Hello,
: I've been playing with the demo version for a couple days now and cant seem
: to get it to do what I want.

: My objective is to allow users to run jobs that are scheduled on the server
: to run as a previledged user without giving them local admin access to the
: server.
: Example,
: Scheduled job: JOB1
: Runas: domain_admin
: Server: SERVER1

: Now I want USER1 to be able to execute JOB1 on SERVER1 but USER1 doesn't have
: admin previledge.

: Thanks

: Now your users can
: run this job only. Please don't confuse how users logon to the scheduler
: (if security is enabled) with how jobs are run. It is a totally different
: game.

I assume you meant run the job through remote client, right? But how can the user run the job if he doesn't have access to the server? I guess my question is how can the user run remote jobs without having local admin access to the server?
Please give me a quick run down of the setup.

Thanks

They don't need local admin access. It seems to me you are confusing some things. Users simply need to connect to the scheduler. After connecting they can select a job to run and run it. The job will run in the context of the user account saved in the job properties. If no user is specified then the job is run in the context of the user account running the scheduler. Nether has anything to do with the rights of a remote user.

: I assume you meant run the job through remote client, right? But how can the
: user run the job if he doesn't have access to the server? I guess my
: question is how can the user run remote jobs without having local admin
: access to the server?
: Please give me a quick run down of the setup.

: Thanks