Microsoft DOS schtasks command

Microsoft DOS schtasks charge 

About schtasks 

Empowers a manager to make, erase, question, change, run and end planned errands on a neighborhood or remote framework. 

Accessibility 

The schtasks order is an outer charge that is accessible in the underneath Microsoft working frameworks as schtasks.exe. 

Windows Vista 

Windows 7 

Windows 8 

Windows 10 

Schtasks linguistic structure 

SCHTASKS/parameter [arguments] 

/Make 

Makes another booked undertaking. 

/Erase 

Erases the planned task(s). 

/Inquiry 

Shows every booked undertaking. 

/Change 

Changes the properties of planned errand. 

/Run 

Runs the planned errand on request. 

/End 

Stops the as of now running booked undertaking. 

/ShowSid 

Demonstrates the security identifier comparing to a booked undertaking name. 

SCHTASKS/Make [/S framework [/U username [/P [password]]]] [/RU username [/RP password]]/SC plan [/MO modifier] [/D day] [/M months] [/I idletime]/TN taskname/TR taskrun [/ST starttime] [/RI interval] [ {/ET endtime |/DU duration} [/K] [/XML xmlfile] [/V1]] [/SD startdate] [/ED enddate] [/IT |/NP] [/Z] [/F] [/HRESULT] [/?] 

/S 

framework 

Indicates the remote framework to which it ought to associate. On the off chance that discarded, the framework parameter defaults to the neighborhood framework. 

/U 

username 

Indicates the client setting under which SchTasks.exe ought to execute. 

/P 

[password] 

Indicates the secret key for the given client setting. Prompts for input if excluded. 

/RU 

username 

Indicates the "keep running as" client account (client setting) under which the undertaking runs. For the framework account, legitimate esteems are "", "NT AUTHORITY\SYSTEM" or "Framework". For v2 assignments, "NT AUTHORITY\LOCALSERVICE" and "NT AUTHORITY\NETWORKSERVICE" are accessible and also the outstanding SIDs for each of the three. 

/RP 

[password] 

Determines the secret key for the "keep running as" client. To incite for the secret word, the esteem must be either "*" or none. This secret word is disregarded for the framework account. Must be joined with either/RU or/XML switch. 

/SC 

plan 

Indicates the calendar recurrence. Substantial calendar writes: MINUTE, HOURLY, Every day, Week after week, Month to month, ONCE, ONSTART, ONLOGON, ONIDLE, ONEVENT. 

/MO 

modifier 

Refines the timetable sort to permit better control over calendar repeat. Substantial esteems are recorded in the Modifiers area beneath. 

/D 

days 

Indicates the day of the week to run the assignment. Legitimate esteems: MON, TUE, Marry, THU, FRI, SAT, SUN and for Month to month plans 1 - 31 (days of the month). Trump card "*" determines all days. 

/M 

months 

Indicates month(s) of the year. Defaults to the main day of the month. Substantial esteems: JAN, FEB, Blemish, APR, MAY, JUN, JUL, AUG, SEP, OCT, NOV, DEC. Trump card "*" determines all months. 

/I 

idletimes 

Determines the measure of sit still time to hold up before running a planned ONIDLE assignment. Substantial range: 1 - 999 minutes. 

/TN 

taskname 

Indicates a name which exceptionally distinguishes this planned undertaking. 

/TR 

taskrun 

Indicates the way and document name of the program to be keep running at the booked time. Case: C:\windows\system32\calc.exe 

/ST 

starttime 

Indicates the begin time to run the assignment. The time design is HH:mm (24 hour time) for instance, 14:30 for 2:30 PM. Defaults to current time if/ST isn't determined. This choice is required with/SC ONCE. 

/RI 

interim 

Indicates the redundancy interim in minutes. This isn't pertinent for plan writes: MINUTE, HOURLY, ONSTART, ONLOGON, ONIDLE, ONEVENT. Substantial range: 1 - 599940 minutes. On the off chance that either/ET or/DU is determined, at that point it defaults to 10 minutes. 

/ET 

endtime 

Determines the end time to run the undertaking. The time arrange is HH:mm (24 hour time) for instance, 14:50 for 2:50 PM. This isn't appropriate for plan composes: ONSTART, ONLOGON, ONIDLE, ONEVENT. 

/DU 

length 

Determines the length to run the errand. The time arrange is HH:mm. This isn't pertinent with/ET and for plan composes: ONSTART, ONLOGON, ONIDLE, ONEVENT. For/V1 undertakings, if/RI is indicated, span defaults to 60 minutes. 

/K 

Ends the undertaking at the endtime or span time. This isn't relevant for plan composes: ONSTART, ONLOGON, ONIDLE, ONEVENT. Either/ET or/DU must be indicated. 

/SD 

startdate 

Determines the main date on which the undertaking runs. The configuration is mm/dd/yyyy. Defaults to the present date. This isn't pertinent for plan writes: ONCE, ONSTART, ONLOGON, ONIDLE, ONEVENT. 

/ED 

enddate 

Indicates the last date when the errand should run. The configuration is mm/dd/yyyy. This isn't pertinent for plan composes: ONCE, ONSTART, ONLOGON, ONIDLE, ONEVENT. 

/EC 

ChannelName 

Indicates the occasion channel for OnEvent triggers. 

/IT 

Empowers the undertaking to run intuitively just if the/RU client is presently signed on at the time the activity runs. This errand runs just if the client is signed into the PC. 

/NP 

No secret word is put away. The errand runs non-intuitively as the given client. Just neighborhood assets are accessible. 

/Z 

Imprints the assignment for erasure after its last run. 

/XML 

xmlfile 

Makes an assignment from the errand XML determined in a document. Can be joined with/RU and/RP switches, or with/RP alone, when undertaking XML as of now contains the foremost. 

/V1 

Makes an assignment unmistakable to pre-Vista stages. Not good with/XML. 

/F 

Compellingly makes the undertaking and stifles notices if the predefined assignment as of now exists. 

/RL 

level 

Sets the Run Level for the activity. Substantial esteems are Restricted and Most elevated. The default is Constrained. 

/Deferral 

delaytime 

Determines the hold up time to postpone the pursuing of the undertaking the trigger is let go. The time arrange is mmmm:ss. This choice is substantial for plan writes ONSTART, ONLOGON, ONEVENT. 

/HRESULT 

For better analyze capacity, the procedure leave code will be in the HRESULT arrange. 

Make modifiers: 

Substantial esteems for the/MO switch per plan write: 

MINUTE: 1 - 1439 minutes. 

HOURLY: 1 - 23 hours. 

Every day: 1 - 365 days. 

Week by week: weeks 1 - 52. 

ONCE: No modifiers. 

ONSTART: No modifiers. 

ONLOGON: No modifiers. 

ONIDLE: No modifiers. 

Month to month: 1 - 12, or In the first place, SECOND, THIRD, FOURTH, LAST, LASTDAY. 

ONEVENT: XPath occasion inquiry string. 

Hop to illustrations including schtasks erase cases. 

SCHTASKS/Erase [/S framework [/U username [/P [password]]]]/TN taskname [/F] [/HRESULT] [/?] 

/S 

framework 

Indicates the remote associated framework. 

/U 

username 

Indicates the client setting under which schtasks.exe ought to execute. 

/P 

[password] 

Determines the secret word for the given client setting. Prompts for input if discarded. 

/TN 

taskname 

Determines the name of the planned undertaking to erase. Special case "*" might be utilized to erase all errands. 

/F 

Mightily erases the undertaking and stifles notices if the predetermined errand is presently running. 

/HRESULT 

For better analyze capacity, the procedure leave code will be in the HRESULT organize. 

Bounce to cases including schtasks erase cases. 

SCHTASKS/Inquiry [/S framework [/U username [/P [password]]]] [/FO arrange |/XML [xml_type]] [/NH] [/V] [/TN taskname] [/HRESULT] [/?] 

/S 

framework 

Determines the remote associated framework. 

/U 

username 

Determines the client setting under which schtasks.exe ought to execute. 

/P 

[password] 

Determines the secret key for the given client setting. Prompts for input if discarded. 

/FO 

arrange 

Determines the arrangement for the yield. Substantial esteems: TABLE, Rundown, CSV. 

/NH 

Determines that the section header ought not show in the yield. This is legitimate just for TABLE and CSV arrange. 

/V 

Showcases verbose errand yield. 

/TN 

taskname 

Indicates the errand name for which to recover the data, else every one of them. 

/XML 

[xml_type] 

Showcases errand definitions in XML design. 

In the event that xml_type is ONE then the yield will be one legitimate XML document. 

On the off chance that xml_type is absent then the yield will be the connection of all XML assignment definitions. 

/HRESULT 

For better analyze capacity, the procedure leave code will be in the HRESULT organize. 

Hop to cases including schtasks question illustrations. 

SCHTASKS/Change [/S framework [/U username [/P [password]]]]/TN taskname { [/RU runasuser] [/RP runaspassword] [/TR taskrun] [/ST starttime] [/RI interval] [ {/ET endtime |/DU duration} [/K] ] [/SD startdate] [/ED enddate] [/Empower |/DISABLE] [/IT] [/Z] } [/HRESULT] [/?] 

/S 

framework 

Determines the remote associated framework. 

/U 

username 

Determines the client setting under which schtasks.exe ought to execute. 

/P 

[password] 

Indicates the secret key for the given client setting. Prompts for input if excluded. 

/TN 

taskname 

Indicates which booked assignment to change. 

/RU 

username 

Changes the client name (client setting) under which the booked undertaking needs to run. For the framework account, legitimate esteems are "", "NT AUTHORITY\SYSTEM" or "Framework". For v2 undertakings, "NT AUTHORITY\LOCALSERVICE" and "NT AUTHORITY\NETWORKSERVICE" are accessible and in addition the outstanding SIDs for each of the three. 

/RP 

secret key 

Indicates another secret word for the current client setting or the watchword for another client account. This secret word is disregarded for the framework account. 

/TR 

taskrun 

Indicates the new program that the planned assignment runs. 

/ST 

starttime 

Indicates the begin time to run the undertaking. The time design is HH:mm (24 hour time) for instance, 14:30 for 2:30 PM. 

/RI 

interim 

Indicates the redundancy interim in minutes. Substantial range: 1 - 599940 minutes. 

/ET 

endtime 

Determines the end time to run the errand. The time organize is HH:mm (24 hour time) for instance, 14:50 for 2:50 PM. 

/DU 

length 

Determines the span to run the errand. The time organize is HH:mm. This isn't pertinent with/ET. 

/K 

Ends the assignment at the endtime or span time. 

/SD 

startdate 

Determines the principal date on which the errand runs. The organization is mm/dd/yyyy. 

/ED 

enddate 

Determines the last date when the errand should run. The fo