So as long as it says "Run as" me, all they would have to do in
case of a power failure would be reboot?   Would they even have to log on
as themselves?

> From: Chris Robinson 
> You can set user credentials in the scheduled task so that if (for example)
> someone logs on who's permissions restrict them
> runnning the task for some reason (e.g. if the task copies files to/from a
> secured directory), the task will still run OK.
> Chris :o)
> "Ellen K." wrote:
>> This is actually very interesting.   I really never log off my boxes at
>> work, I just lock the workstation, but it's a good thing to know.
>> 
>> The reason for the question is my current project which is about ready
>> to go into production needs to run in the night from Sunday to Monday
>> every week no matter what, so I told ServerGuy to put my box on the list
>> of boxes that must be rebooted in the event of any weekend power outage
>> etc.... so that made me wonder whether him just rebooting it would be
>> sufficient to ensure that my process would run.
>> 
>> Thinking out loud here now that I wrote the above I'm wondering what
>> happens to network permissions etc... that process talks to the legacy
>> flat-file database and to a SQL Server database, and also has to get and
>> put files on a third server and post a bunch of reports to our
>> intranet... so now I'm thinking that just rebooting might not be
>> sufficient after all.
>> 
>> Comments?
>> 
>> On Mon, 24 Nov 2003 21:47:13 -0500, Mike N. 
>> wrote in message :
>> 
>> >On 25 Nov 2003 01:50:56 GMT, Ellen K
 wrote:
>> >
>>>>If a task is scheduled to run under my ID, do I have to be
logged on to the
> box
>> >>when it's time for it to run, or could anyone be logged on?
>> >
>>>   In fact, if it's run under your ID and you happen to be
logged in when it
> fires off, it *may* run in the foreground
>> >and will be terminated if you log out before it completes.   I say *may*
> because there may be an "interactive" task
>> >setting that will correct this problem.

--- BBBS/NT v4.01 Flag-5