• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 510
  • Last Modified:

Giving access to C:\WINDOWS\Tasks folder

Hi experts,

I have a windows 2003 server machine on my domain, and i have some scheduled tasks created under the folder C:\WINDOWS\Tasks.
Currently all these task are running with their assigned schedule.

I need to give access to one of the domain users to the Tasks folder, so that he can run them manuallay. My user has remote desktop access to the server.

I would appreciate any help

thanks
0
cakirfatih
Asked:
cakirfatih
  • 4
  • 2
1 Solution
 
valiconCommented:
Give the user account read and execute permissions to the folder and make sure that the actual task inherits the same permissions.
0
 
cakirfatihAuthor Commented:
Right clicking and going to properties of that folder does not display the Security tab.
is there another way of assigning permissios to my user.
0
 
valiconCommented:
I apologize I misread the folder location...
0
Cloud Class® Course: Microsoft Exchange Server

The MCTS: Microsoft Exchange Server 2010 certification validates your skills in supporting the maintenance and administration of the Exchange servers in an enterprise environment. Learn everything you need to know with this course.

 
valiconCommented:
All you need to do is to right click on the actual task and add the user with the permissions of read and execute.  Here is some further information from Technet:

Task Scheduler and security
When creating a scheduled task, you must enter a user name and password, either in the Add Scheduled Task Wizard or in the Run as box in the Task tab of the scheduled task's property dialog box. When the scheduled task runs, the program you've scheduled runs as if it were started by the user you specified, with that user's security context. For example, if the user specified for a scheduled task is a member of the Backup Operators group on the local computer, the program specified in the scheduled task file runs as if a member of the Backup Operators group is logged onto the local computer. If another user is logged on to the computer at the time a scheduled task specified for a different user runs, the task runs but is not visible to the current user.

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. For more information about groups, see Default local groups and Default groups.

Note

• A user for whom you assign permissions to the Tasks folder using cacls will be able to access scheduled tasks for all users. Choose which users to give access to the Tasks folder judiciously.
 

In Windows Server 2003 family operating systems, passwords have an expiration date. If you are scheduling recurring tasks that run indefinitely, you need to be aware of the expiration date on your passwords. If the password changes for an account on a domain, then you must update the tasks scheduled to run under that account.

When a job is created through Task Scheduler, account information for all tasks that use the same run as account is stored only once. Task Scheduler validates the run as account when a job is created, which prevents incorrect run as account information from being saved and, as a result, prevents other existing jobs that use the same account from being affected. If the password validation fails, a job file is created, but it will not run.

If the run as account password has expired or the account has been deleted and recreated, the password must be updated for jobs to run. Updating the password for one job automatically updates it for all jobs that use the same run as account.

When you create a scheduled task, the user credentials you specify for that specific task are securely stored on the local computer.

0
 
valiconCommented:
Do you need any further help with this issue?  If so please let me know :)
0
 
cakirfatihAuthor Commented:
Hi,
I have not tried your solution yet. I will let you know after i try it.

thanks
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Certified Penetration Testing

This CPTE Certified Penetration Testing Engineer course covers everything you need to know about becoming a Certified Penetration Testing Engineer. Career Path: Professional roles include Ethical Hackers, Security Consultants, System Administrators, and Chief Security Officers.

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now