Hi. We have a AD domain and there some windows 2003 and 2000 servers. In some of these servers we have schedule task running as local/domain administrator. But now all these scheduled tasks cannot start. Does there have some policy for running the schedule? How can I fix the problem? Thanks
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Schedule can start after reboot
- Thread starter Oh
- Start date
- Thread starter
- #3
First thank for your help. Yes, All these tasks are local, not shared. We have 5 servers and 10 schedules jobs. All these tasks work well untill last month. We have to start each job one by one now. I guess some thing wrong in AD group policy. Need help!!
Tasks don't have anything to do with group policy, unless you asign them through GP, then that has nothing to do with the running. If the .job file is local, it monitors the system clock, and an event is triggered at the specified time. It it possible, but unlikely that the .job files have been corrupted as such. What I suggest you try.
First thing is a test.
Copy all the job files to another folder. Delete them from the scheduled tasks folder. Reboot.
create a new task, with the scheduled task wizzard, and just set it to start notepad in like 2 minutes. Just to make sure your task registration is working correctly. If notepad or whatever, launches, then your system is working fine. You either have a problem with your tasks registrations, or your actual .job files themselves.
Copy the job files one by one back to the scheduled tasks folder. When each one is created, it is registered as a new task, and creates a time stamp marker for it. It may be that the registrations for the tasks had been got at by any one of many possible reasons.
Also, if that doesn't work, remove the tasks again. Try recreating, again, through the wizzard one of your specified tasks, just as it should have been in the old ones. This may help if for some bizzar reason, your task files have been corrupted.
Hope this Helps.
Neil J Cotton
njc Information Systems
Systems Consultant
First thing is a test.
Copy all the job files to another folder. Delete them from the scheduled tasks folder. Reboot.
create a new task, with the scheduled task wizzard, and just set it to start notepad in like 2 minutes. Just to make sure your task registration is working correctly. If notepad or whatever, launches, then your system is working fine. You either have a problem with your tasks registrations, or your actual .job files themselves.
Copy the job files one by one back to the scheduled tasks folder. When each one is created, it is registered as a new task, and creates a time stamp marker for it. It may be that the registrations for the tasks had been got at by any one of many possible reasons.
Also, if that doesn't work, remove the tasks again. Try recreating, again, through the wizzard one of your specified tasks, just as it should have been in the old ones. This may help if for some bizzar reason, your task files have been corrupted.
Hope this Helps.
Neil J Cotton
njc Information Systems
Systems Consultant
- Status
Similar threads
- Locked
- Question
- Locked
- Question
