RE: Remote Task Scheduler access problem

Tech-Archive recommends: Fix windows errors by optimizing your registry

Hi,

What is the exact OS version?

This post is in microsoft.public.windows.server.general queue, so I suspect
the OS is Windows server 2003. This is by design in Windows 2003,they have
tightened the security in 2003. The OS won't let you schedule a job with a
standard user account.

Sorry for any inconvenience.


Best regards,

Vincent Xu
Microsoft Online Partner Support

======================================================
Get Secure! - www.microsoft.com/security
======================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others
may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties,and confers no rights.
======================================================



--------------------
From: "Brian L." <699df88b-2059788708@xxxxxxxxxxxxxx>
Subject: Remote Task Scheduler access problem
Date: Thu, 1 Jun 2006 14:48:20 -0400
Lines: 43
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2869
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
X-RFC2646: Format=Flowed; Original
Message-ID: <OIZCNLbhGHA.4252@xxxxxxxxxxxxxxxxxxxx>
Newsgroups: microsoft.public.windows.server.general
NNTP-Posting-Host: 204-60-67-237.connecticare.com 204.60.67.237
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP04.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.general:97324
X-Tomcat-NG: microsoft.public.windows.server.general

Hello all,

I am trying to grant a few users access to see (as well as run and stop)
scheduled tasks on one of our servers. I have been looking at the help
pages
for Task Scheduler, and I'm not having any luck. They are able to see the
Scheduled Tasks folder, listed with the other shares on the system, if
they
navigate to it in the network (or start -> run -> \\server). However, if
they double-click on the Scheduled Tasks folder it doesn't open. The only
way around this has been to put the users into the local Administrators
group of the server. I'd like to avoid this if possible.

The answer seems to be in one section of the help page, but I haven't
been
able to get this to work:

By default, to schedule a task, you must be a member of the
Administrators,
Backup Operators, or Server Operators group on the local computer. By
default, when creating a scheduled task, you cannot enter a user who
belongs
to a group that has more rights than the group you belong to. For
example,
if you are a member of the Backup Operators group on the local computer,
you
cannot specify a member of the Administrators group when creating a
scheduled task. However, a member of the Administrators group can enable
a
member of any group to create or modify scheduled tasks, by using the
cacls
command to modify the discretionary access control list (DACL) of the
Tasks
folder. By default, the Tasks folder is located in the \Windows folder on
the hard drive of the local computer, for example C:\Windows\Tasks. For
more
information about using cacls, see Cacls.


Now the above excerpt says that I can grant someone access, using cacls,
to
the C:\Windows\Tasks folder on the server. So I created a group on the
domain, put one of the users into the group, used cacls to grant access
to
the C:\Windows\Tasks folder (at first Change, then I tried Full Control),
then logged out and back in to make sure group membership took effect.
The
folder still behaved the same way - visible but I can't open it.

Does anyone know what I'm doing wrong? Or is the help file incorrect, and
that method won't work? Any help is appreciated! Thanks.

-Brian






.

Relevant Pages

  • Re: Grant Object Access
    ... Have you examined the IIS settings for the web app in IIS for differences ... > Now that I had resolved the issues on my test server, ... > "Roger Abell" wrote in message ... >>> has no control over the scheduled tasks in themselves (all the user can ...
    (microsoft.public.windows.server.security)
  • Re: Remote Task Scheduler access problem
    ... The server OS is Windows Server 2003 Standard Edition SP1, ... create or modify scheduled tasks, by using the cacls command to modify the ... the Administrators group to access scheduled tasks, then it saves me a lot ...
    (microsoft.public.windows.server.general)
  • RE: Collect Server Performance Data is taking a long time
    ... Thank you for posting in the SBS newsgroup. ... Please check the Scheduled Tasks log for more info. ... You can also open the properties of the "Collect Server Performance Data" ... I recommend you to reinstall SBS Monitoring component. ...
    (microsoft.public.windows.server.sbs)
  • RE: Shutdown.exe
    ... How can I configure it to restrat an exchange 2003 server running on server ... and then click Scheduled Tasks. ... you may utilize Event Log Monitor software to accomplish this task. ... Microsoft does not control these sites and has not tested any software ...
    (microsoft.public.win2000.new_user)
  • Re: HOW ==> Users View Scheduled Tasks on a Server ??
    ... task is set to run under a domain admin account which he does not know). ... i see no risk at all in just lettting him VIEW the scheduled tasks! ... > server in order to be able to manage or even see the scheduled tasks on ... >> will run mytask.job on the remote server...but only if you are an admin. ...
    (microsoft.public.win2000.security)