Good Morning All,
I realize that the members of this group probably have more experience using the task scheduler than the Win2K Pro Group:
I have a W2K Pro production box that 5 users have access to for bank polling and such.
*Each of the 5 users are setup as power users locally on that machine.
*Each of the 5 users are mapped to the Q drive (a location where the output generated from the bank polling goes).
*John is the user who has the scheduled task that kicks off the bank polling.
*Each user has the rights to execute the bank polling script (i've tested)
*The task kicks off each weekday morning at 7:20am
*The box remains on all the time
Is there a way John's scheduled task will work if say, Delbert, or any other of the 5 users is logged in? It will not let me launch an identical task under Delbert because the name of the task is the same as John's.
Audit will not let us create a generic ID for that box to kick off the tasks. Is there a better method to accomplish this weekday launching?
Caio,
Matt
I realize that the members of this group probably have more experience using the task scheduler than the Win2K Pro Group:
I have a W2K Pro production box that 5 users have access to for bank polling and such.
*Each of the 5 users are setup as power users locally on that machine.
*Each of the 5 users are mapped to the Q drive (a location where the output generated from the bank polling goes).
*John is the user who has the scheduled task that kicks off the bank polling.
*Each user has the rights to execute the bank polling script (i've tested)
*The task kicks off each weekday morning at 7:20am
*The box remains on all the time
Is there a way John's scheduled task will work if say, Delbert, or any other of the 5 users is logged in? It will not let me launch an identical task under Delbert because the name of the task is the same as John's.
Audit will not let us create a generic ID for that box to kick off the tasks. Is there a better method to accomplish this weekday launching?
Caio,
Matt
