Quote:

---

SCHTASKS /Create [/S system [/U username [/P password]]]
[/RU username [/RP password]] /SC schedule [/MO modifier] [/D day]
[/I idletime] /TN taskname /TR taskrun [/ST starttime] [/M months]
[/SD startdate] [/ED enddate]


/I idletime Specifies the amount of idle time to
wait before running a scheduled
ONIDLE task.
Valid range: 1 - 999 minutes.

---

Quote:

---

Platform SDK: Task Scheduler

Idle Triggers
An idle trigger is an event-based trigger that is fired a specific amount of time after the computer becomes idle. The computer is considered to be in an idle state when no keyboard or mouse input occurs.

---

Quote:

---

...We are experiencing large amount of our users are not logging off at the end of their workday, hence bypassing the login script. Is it possible to logoff any lock workstations after x hour of inactivity daily?...

---

Quote:

---

Syntax
schtasks /create /tn TaskName /tr TaskRun /sc onidle /i {1 - 999} [/sd StartDate] [/it] [/ru {Domain\]User [/rp Password] | System}] [/s Computer [/u [Domain\]User [/p Password]]]

Remarks
The "on idle" schedule type schedules a task that runs whenever there is no user activity during the time specified by the /i parameter. In the "on idle" schedule type, the /sc onidle parameter and the /i parameter are required. The /sd (start date) is optional and the default is the current date.

Examples
To schedule a task that runs whenever the computer is idle
The following command schedules the MyApp program to run whenever the computer is idle. It uses the required /i parameter to specify that the computer must remain idle for ten minutes before the task starts.

schtasks /create /tn "My App" /tr c:\apps\myapp.exe /sc onidle /i 10

---

Quote:

---

we operate in an NT4 server environment with mix client-nt,w2k and xp

---

Quote:

---

Appendix: How to Install Task Scheduler
a. Windows 98 and Windows 2000/XP:

Nothing to do ! The task scheduler is already preinstalled on your Windows system !

b. Windows 95

On Win 95 / NT the task scheduler is not preinstalled, but you can easily install Task Scheduler through Internet Explorer 4.0 or higher. To install Task Scheduler under Windows 95, proceed as if running Windows NT4 (see below). Note: Windows 95 Plus! contains a product called System Agent. This is not the same product.

c. Windows NT4 (SP3+)

Go to the Control Panel and select Add/Remove Programs. Select Microsoft Internet Explorer 4 or 5 from the list, and when a dialog prompt you for what to do, select Add a component. Depending on the current release of your browser (4 or 5), you will eventually be given a list of additional software
you may install (Note: this may take a long time!). With IE4 you should select Task Scheduler under Additional Explorer Enhancements. With IE5 select the Offline Browsing Pack. You can also go directly to <http://www.microsoft.com/windows/ie>. From here you can select all IE software releases and add-ons. We recommend you upgrade to IE5. We've had a lot of problems reported about upgrading IE4, you would probably be better off installing IE5 anyway (it's a much better
browser). Click Yes to restart your computer when prompted.

Remark: If you are a Netscape supporter, do not worry: It is not necessary to install the shell integration component or or use Internet Explorer as your your default browser for the task scheduler to work. The task scheduler is a (more or less) independent piece of software that just happened to be be distributed via the Internet Explorer packages.

---

Quote:

---

Requirements
Client: Requires Windows XP, Windows 2000 Professional, Windows Me, and Windows 98.
Server: Requires Windows Server 2003 and Windows 2000 Server.
Redistributable: Requires Internet Explorer 4.0 or later on Windows NT 4.0 and Windows 95.
Header: Declared in Mstask.h.

---

Quote:

---

........; Used by tsDefineTask and tsActivateEvent functions - TASK parameter names
$tsTASKPARMS = "ApplicationName", "Parameters", "WorkingDirectory", "Comment", "Creator", "Priority", "MaxRunTime", "Idle", "DontStartIfOnBatteries", "KillIfGoingOnBatteries", "RunOnlyIfLoggedOn", "SystemRequired", "DeleteWhenDone", "Suspend", "StartOnlyIfIdle", "KillOnIdleEnd", "RestartOnIdleResume", "Hidden", "Interactive", "HaltOnError"....
;
;
;


......;======================================================================
;
;FUNCTION tsDefineTask(TaskAry, TaskParms)
;
;ACTION Loads the specified array with the task parameter pairs.
; The parameter pairs consist of a 3-character mnemonic, "=",
; and a value. Mnemonics represent the 20 JT parameter names,
; and are identified in the table below.
;
;SYNTAX tsDefineTask("TaskAry", TaskParm=val,...)
;
;PARAMETERS UsrAry - Name of task array to populate (as string, w/o "$")
; TaskParm - List of mnemonic=Value Parameter pairs, comma-delimited
;
; Mnemonic Parameter Name Data Type
; APP : ApplicationName String - command to run
; PRM : Parameters String - app parameters
; WKD : WorkingDirectory String
; CMT : Comment String
; CTR : Creator String
; PRI : Priority STring: IDLE, NORMAL, HIGH, REALTIME
; MRT : MaxRunTime Integer (ms)
; IDL : Idle Integer # # (wait & deadline min)
; DSB : DontStartIfOnBatteries Boolean
; KGB : KillIfGoingOnBatteries Boolean
; RLO : RunOnlyIfLoggedOn Boolean
; SRQ : SystemRequired Boolean
; DWD : DeleteWhenDone Boolean
; SUS : Suspend Boolean
; SII : StartOnlyIfIdle Boolean
; KIE : KillOnIdleEnd Boolean
; RIR : RestartOnIdleResume Boolean
; HID : Hidden Boolean
; ITV : Interactive Boolean (currently unsupported by JT)
; HOE : HaltOnError Boolean (currently unsupported by JT)
;
;REMARKS This function parses the parameter=value pairs and loads the
; value into the correct array position. Parameter pairs are separated
; by whitespace. Any character is permitted in the value portion, but
; equal signs (=) must be escaped as "==".
;
;RETURNS nothing - sets @ERROR
;
;DEPENDENCIES none
;
;EXAMPLE tsDefineTask("MyTaskArray", 'APP=kix32.exe PRM=$arg==3 WKD=C:\TEMP')
; "MyTaskArray" is the name of the array that will be loaded.......
;
;
;
;
;



..... ; Certain Trigger types do not require the TypeArguments value to be set. The
; "RQ" flag in element 9 is removed automatically for those...
If InStr("ONCE,ONIDLE,ATSTARTUP,ATLOGON", $tsTrigAry[$tsTrigId,8]) <> 0
$tsTrigAry[$tsTrigId,9] = "" ; remove ReQuired flag for these Types
EndIf..........

---