I agree with your comment and would definitely recommend you wrap your script into a batch file either via pl2bat or by handrolling a batch file to interact with your program. Then whack it into task scheduler.

I've found this to be the best way on win32 (for me at least). On the win2k environments I work with I can also allow my programs to run as particular users. You could use the runas command to replicate this (assuming your windows platform supports it).

ie:

C:\>runas
RUNAS USAGE:

RUNAS [/profile] [/env] [/netonly] /user:<UserName> program

   /profile        if the user's profile needs to be loaded
   /env            to use current environment instead of user's.
   /netonly        use if the credentials specified are for remote acc
+ess only.
   /user           <UserName> should be in form USER@DOMAIN or DOMAIN\
+USER
   program         command line for EXE.  See below for examples
[download]

Hope that helps :)