Hi, I'm faced with the need to implement the functions of
TaskScheduler.dll from an ASP page on a Win2K SP4 server, the goal
being to have the web page kick off a process in the context of domain
administrator or other privileged user with a full profile available.
(See
http://mysite.verizon.net/res1ur2j/ re the DLL, section about
scripting MSTASK)
I have found that this object can't even read the Task Scheduler
unless I have the web application running with low protection
(process, instead of pooled or isolated). Supposely another
workaround would be to give IWAM_machine "act as part of the OS"
privileges.
Am I not risking the health of all the web sites on the box if I leave
the protection for this app set to low?
What security holes am I subjecting myself to if I give IWAM that
extra privilege?
Is it feasible to instead add TaskScheduler.dll to Component Services,
to get it to work in a privileged account context? If so, how could I
go about that? The docs I've found so far are rather obtuse at my
current skill level.
Thanks for any guidance,
Brad
brad dott berson at bytebrothers dott org
FAQ
Profile
Private Messages
Log in
