I need to package a scheduled task to run on NT4 w/s. What is the best way to do it bearing in mind it needs to run as system and be capable of un-installation?

I find delivering as a .job file into %windir%\tasks will set up the task with the privileges of the account logged in at the time of install. Using the AT command gives the task a name and ID sequentially generated by the task scheduler on each w/s. These values would then need to be quoted to remove the task.

Any ideas?

Using Wise PS v5.
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


This is possible as my old company used to run AT jobs to reboot the PCs scheduled basis.

I'm sure they used to create a Wise Script that would set the AT commands. Once the script was compiled it could be released via Altiris as an unattended installation. I will try and get you more details on this and post as and when I have them. Regards
Answered 11/01/2004 by: Jim101
Orange Belt

Please log in to comment
If you ARE or have ACCESS to a programmer, I'm pretty sure there is an API for setting, modifying, and deleting tasks.

Wise can handle MOST API calls (even ones needing to pass structures) so if you need more control, consider using the API.

In general, I think the previous answer of executing an AT command is the best idea - much less hassle that way.


- Sean Roberts
Answered 11/01/2004 by: sean_c_roberts
Senior Purple Belt

Please log in to comment
OK if you download a copy of Shutdown.exe from the web; I have found the following site; http://www.budja.com/shutdown/

then set a DOS job as follows;

\\computername 01:30 /interactive /every:su,m,t,w,th,f shutdown.exe

As I am sure you have seen already for all the dos switches type AT /?

Hope this helps.
Answered 11/02/2004 by: Jim101
Orange Belt

Please log in to comment