On 2003, simply set the security either on the task security tab or by cacling the *.JOB with READ/EXECUTE on the applicable task. This will allow the user to manage the task. This will allow him/her to run the task whenever while not allowing him/her to modify the which program is executed. You should ensure also that the user does not have the ability to modify the batch file, script or executable if the task itself runs with admin or system credentials.
> On Friday, July 04, 2008 10:52 AM Jaso wrote:
> "" wrote:
>
>
> When you set up the scheduled task on the client you shoudl get the option
> to select which user the task is to be run under. For me I simply select
> administrator and punch in the admin password. When the scheduled task runs
> it runs with admin permissions.
>
> Someone who knows admin credentials needs to set up the task but once this
> has been done it should run regardless of who is logged in to the machine.
>> On Tuesday, July 08, 2008 8:23 PM pimy10 wrote:
>> Server OS: Server 2003 R2
>> Client OS: XP Pro SP2
>>
>> I am trying to allow a non-admin user to run a scheduled task on a
>> remote server. According to the Help text, the user must be a member
>> of the local Administrators group, the local Backup Operators group,
>> the domain Server Operators group, or =93have been delegated the
>> appropriate authority, on the local computer=94. I would prefer not to
>> add the user to one of the three groups I mentioned. I have given the
>> user Read+Execute on the target task. I also gave the user Read (and
>> even Full Control) to the C:\windows\tasks folder on the server using
>> CACLS, still no dice. When the user brings up the server via UNC, they
>> don=92t see Scheduled Tasks. I tried running schtasks /query /s serverA,
>> but the user gets an Access is denied message. I confirmed that the
>> user can view the scheduled tasks folder when they are a member of the
>> Backup Operators group, but when they double-click on it, it doesn=92t
>> list the scheduled tasks.
>>
>> How can I go about delegating the proper authority? Is there a group
>> policy setting in Server 2003 that will allow a user to run a
>> scheduled task remotely (i.e. \\server, double-click on scheduled
>> tasks, right-click the task and select Run)? I already tried providing
>> the user with Log on as a batch job, but that had no impact.
>> Thanks,
>> pimy
>>
>> In Windows Help:
>> To run a scheduled task immediately
>> 1. Open Task Scheduler.
>> 2. Right-click the task that you want to run, and then click Run.
>> Notes
>> =95 To perform this procedure, you must be a member of the
>> Administrators, Backup Operators, or Server Operators group, or have
>> been delegated the appropriate authority, on the local computer. As a
>> security best practice, consider using Run as to perform this
>> procedure.
>> =95 To open Task Scheduler, click Start, point to Settings, click
>> Control Panel, and then double-click Scheduled Tasks.
>> =95 You can also run a scheduled task immediately by selecting a task in
>> the details pane, and then clicking Run on the File menu
>>> On Friday, November 05, 2010 3:59 PM John Bonaccorso wrote:
>>> This answer doesn't even address the question. The question was:
>>>
>>>
>>>
>>> "How to allow non-admin to run scheduled tasks remotely?"
>>>
>>>
>>>
>>> which is something I want to know how to do as well. What this person was asking for is nothing to do with the secuirty context underwhich the task will run. He/She wanted to know how to allow a non-administrative user the permission to see, edit and run on demand an existing task. This used to be done easily in 2033 and prior. One would simply grant Modify permissions on the applicable *.JOB file in the %systemroot%\tasks filder. This is no longer the case in 2008 scheduled tasks work quite differently now.
>>> Submitted via EggHeadCafe - Software Developer Portal of Choice
>>> Fill out blank PDF form online and stream to browser with iTextSharp
>>> http://www.eggheadcafe.com/tutorials...textsharp.aspx
Similar Threads
Linear Mode
