I've found the scheduled task method to be the best for most situations. It's important to note that you DO NOT need to schedule it to run at a specific time. One of the products we deploy to our clients uses the login script to determine if an admin action is required, and then a service running receives the request and pushes out the scheduled event and immediately executes it with the appropriate credentials. all of this is done in Kix, including the system service.

You can do this easily with the tcLib function library...

You will have to have completed the "install" process so your script can locate JT.EXE. Then create a script with the following logic:

Load tcLib.kxf, then call tcInit() to initialize. You can then override

Create a list of systems you want to process. You can query AD if you want all systems to be configured.

Enumerate the list of systems. For each system, create a task EVENT. The event defines the process and security, but not the schedule. Immediately run the event. Here's the code to define and run a remote task using tcLib.
 Code:
; Init the arrays
tcInit()
; Create a task event, defining the APPlication and PaRaMeters
; This should be relative to the local system - either precopy a BAT file
; or point to a UNC-referenced share. DO NOT use drive letters mapped
; by th eusre environment as they will not exist!
; Set DWD to auto-delete the task after it runs
tcDefineTask('APP=C:\temp\test.bat PRM=-t -v DWD=1')

; Set the event credentials
tcDefineTask('USR=Admin PWD=AdminPass')

; Create the event on the remote system. 
$ = tcSetEvent($RemoteSystem, 'AdminEvent')

; Execute the remote event
$ = tcExecute($RemoteSystem, 'AdminEvent')
So, with just 5 commands, you can define and execute a process on any remote system that you are authorized to access, and run it using any credentials. Note that when you run the script from your workstation, it must be run as an admin user with (NetBIOS) access to each target system.

I've been able to update several thousand systems in a day in this manner. Push a small bat file out that runs under admin credentials. the bat file is 1-2 lines and references a more complex script from a central location. This insures that there's no overhead copying stuff to each PC or dealing with missing dependencies.

Glenn
_________________________
Actually I am a Rocket Scientist! \:D