G
Guest
(Sorry, misposted in 'Accessibility')
After copying tasks between servers and applying passwords, the copied task
often does not run on the target machine.
It seems the scheduler simply does not see the task until it has been
manually run once.
There is no status message and no entry in the log to indicate any cause,
and the last run/next run times never change.
We are migrating nearly 200 tasks from old servers to new servers, and
cannot just run these tasks at anytime to force them to run automatically
thereafter. The scheduled tasks run-times are distributed over 24 hours
The method used to copy the tasks is:
1. RDP to the old server and copy the tasks to a network folder using drag
and drop in Windows Explorer
2. RDP to the new server, drag and drop tasks into C:\Windows\Tasks.
(Occassionally Windows Explorer crashes when pasting, but tasks still
arrive
3. Apply passwords.
4. Wait and hope!
Can anyone propose a solution or point to a problem ticket somewhere?
XP 2003 Pro, SP2
After copying tasks between servers and applying passwords, the copied task
often does not run on the target machine.
It seems the scheduler simply does not see the task until it has been
manually run once.
There is no status message and no entry in the log to indicate any cause,
and the last run/next run times never change.
We are migrating nearly 200 tasks from old servers to new servers, and
cannot just run these tasks at anytime to force them to run automatically
thereafter. The scheduled tasks run-times are distributed over 24 hours
The method used to copy the tasks is:
1. RDP to the old server and copy the tasks to a network folder using drag
and drop in Windows Explorer
2. RDP to the new server, drag and drop tasks into C:\Windows\Tasks.
(Occassionally Windows Explorer crashes when pasting, but tasks still
arrive
3. Apply passwords.
4. Wait and hope!
Can anyone propose a solution or point to a problem ticket somewhere?
XP 2003 Pro, SP2