Scheduling a task on remote machine
From: Dmitry Khodorkovsky (dkhodor@rogers.com)
Date: 08/09/02
- Next message: dejann@: "local security policy problem (virus?)"
- Previous message: Leon: "Re: CIS Security Baseline"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "Dmitry Khodorkovsky" <dkhodor@rogers.com> Date: Thu, 8 Aug 2002 23:30:39 -0400
Hello,
I recently ran into an interesting problem of scheduling a task using Win2K
Task Scheduler's API on remote machine. Seems, there is a special sequence
of function calls to be run --- like you can't first create a task, then
set target computer name and then schedule it, persist it. --- if you do
this, then computer name is taken as "NULL", i.e. local machine and task
gets saved on local machine instead.
However, if you set target computer name right away after initializing
TaskScheduler, then it may work if your process is running under account
that has administrative privileges on the remote machine.
Have anyone experienced such? I might got wrong somewhere.
Any suggestions are appreciated.
Thanks
Dmitry
- Next message: dejann@: "local security policy problem (virus?)"
- Previous message: Leon: "Re: CIS Security Baseline"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
