AT command
From: Pedro (anonymous_at_discussions.microsoft.com)
Date: 05/31/04
- Next message: Khurram Naseem: "Memory Leak"
- Previous message: Jaime Dominguez: "black screen appears after several days up"
- Next in thread: Lanwench [MVP - Exchange]: "Re: AT command"
- Reply: Lanwench [MVP - Exchange]: "Re: AT command"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 31 May 2004 02:53:25 -0700
Thanks for your reply.
Please can you or anyone else tell me as to what command
line I should use to schedule a task. For example, I
want to launch a prog.exe at 10am on 31 July 2004. What
is the exact AT command line I should use for this task ?
I have seen all online help and 2KB articles:
http://support.microsoft.com/?id=220149
http://support.microsoft.com/?id=313565
I failed to find the AT command line necessary for the
task I want to schedule. My question is simple: Does
anyone know this command line please.
Thanks a lot.
Pedro
>-----Original Message-----
>AtSchedules commands and programs to run on a computer
at
>a specified time and date. You can use at only when the
>Schedule service is running. Used without parameters, at
>lists scheduled commands.
>
>Syntax
>at [\\ComputerName] [{[ID] [/delete] | /delete [/yes]}]
>
>at [[\\ComputerName] Hours:Minutes [/interactive]
>[{/every:Date[,...] | /next:Date[,...]}] Command]
>
>Parameters
>\\ComputerName
>Specifies a remote computer. If you omit this parameter,
>at schedules the commands and programs on the local
>computer.
>ID
>Specifies the identification number assigned to a
>scheduled command.
>/delete
>Cancels a scheduled command. If you omit ID, all of the
>scheduled commands on the computer are canceled.
>/yes
>Answers yes to all queries from the system when you
delete
>scheduled events.
>Hours:Minutes
>Specifies the time when you want to run the command.
Time
>is expressed as Hours:Minutes in 24-hour notation (that
>is, 00:00 [midnight] through 23:59).
>/interactive
>Allows Command to interact with the desktop of the user
>who is logged on at the time Command runs.
>/every:
>Runs Command on every specified day or days of the week
or
>month (for example, every Thursday, or the third day of
>every month).
>Date
>Specifies the date when you want to run the command. You
>can specify one or more days of the week (that is, type
>M,T,W,Th,F,S,Su) or one or more days of the month (that
>is, type 1 through 31). Separate multiple date entries
>with commas. If you omit Date, at uses the current day
of
>the month.
>/next:
>Runs Command on the next occurrence of the day (for
>example, next Thursday).
>Command
>Specifies the Windows command, program (that is, .exe
>or .com file), or batch program (that is, .bat or .cmd
>file) that you want to run. When the command requires a
>path as an argument, use the absolute path (that is, the
>entire path beginning with the drive letter). If the
>command is on a remote computer, specify Universal
Naming
>Convention (UNC) notation for the server and share name,
>rather than a remote drive letter.
>/?
>Displays help at the command prompt.
>Remarks
>Schtasks is another command-line scheduling tool that
you
>can use to create and manage scheduled tasks. For more
>information about schtasks, see Related Topics.
>
>Using at
>To use at, you must be a member of the local
>Administrators group.
>
>Loading Cmd.exe
>At does not automatically load Cmd.exe, the command
>interpreter, before running commands. If you are not
>running an executable (.exe) file, you must explicitly
>load Cmd.exe at the beginning of the command as follows:
>
>cmd /c dir > c:\test.out
>
>Viewing scheduled commands
>When you use at without command-line options, scheduled
>tasks appear in a table formatted similar to the
following:
>
>Status ID Day Time Command Line
>OK 1 Each F 4:30 PM net send group leads
>status due
>OK 2 Each M 12:00 AM chkstor > check.file
>OK 3 Each F 11:59 PM backup2.bat
>
>Including identification number (ID)
>When you include identification number (ID) with at at a
>command prompt, information for a single entry appears
in
>a format similar to the following:
>
>Task ID: 1
>
>Status: OK
>
>Schedule: Each F
>
>Time of Day: 4:30 PM
>
>Command: net send group leads status due
>After you schedule a command with at, especially a
command
>that has command-line options, check that the command
>syntax is correct by typing at without command-line
>options. If the information in the Command Line column
is
>incorrect, delete the command and retype it. If it is
>still incorrect, retype the command with fewer command-
>line options.
>
>Viewing results
>Commands scheduled with at run as background processes.
>Output is not displayed on the computer screen. To
>redirect output to a file, use the redirection symbol
(>).
>If you redirect output to a file, you need to use the
>escape symbol (^) before the redirection symbol, whether
>you are using at at the command line or in a batch file.
>For example, to redirect output to Output.text, type:
>
>at 14:45 c:\test.bat ^>c:\output.txt
>
>The current directory for the executing command is the
>systemroot folder.
>
>Changing system time
>If you change the system time at a computer after you
>schedule a command to run with at, synchronize the at
>scheduler with the revised system time by typing at
>without command-line options.
>
>Storing commands
>Scheduled commands are stored in the registry. As a
>result, you do not lose scheduled tasks if you restart
the
>Schedule service.
>
>Connecting to network drives
>Do not use a redirected drive for scheduled jobs that
>access the network. The Schedule service might not be
able
>to access the redirected drive, or the redirected drive
>might not be present if a different user is logged on at
>the time the scheduled task runs. Instead, use UNC paths
>for scheduled jobs. For example:
>
>at 1:00pm my_backup \\server\share
>
>Do not use the following syntax, where x: is a
connection
>made by the user:
>
>at 1:00pm my_backup x:
>
>If you schedule an at command that uses a drive letter
to
>connect to a shared directory, include an at command to
>disconnect the drive when you are finished using the
>drive. If the drive is not disconnected, the assigned
>drive letter is not available at the command prompt.
>
>Tasks stopping after 72 hours
>By default, tasks scheduled using the at command stop
>after 72 hours. You can modify the registry to change
this
>default value.
>
>Start Registry Editor (regedit.exe).
>Locate and click the following key in the registry:
>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Sche
du
>le
>On the Edit menu, click Add Value, and then add the
>following registry value: Value Name: AtTaskMaxHours
Data
>type: REG_DWORD Radix: Decimal Value Data: 0. A value of
0
>in the value data field indicates no limit, does not
stop.
>Values from 1 through 99 indicates the number of hours.
> Caution
>
>Incorrectly editing the registry may severely damage
your
>system. Before making changes to the registry, you
should
>back up any valued data on the computer.
>Task Scheduler and the at command
>You can use the Scheduled Tasks folder to view or modify
>the settings of a task that was created by using the at
>command. When you schedule a task using the at command,
>the task is listed in the Scheduled Tasks folder, with a
>name such as the following:At3478. However, if you
modify
>an at task through the Scheduled Tasks folder, it is
>upgraded to a normal scheduled task. The task is no
longer
>visible to the at command, and the at account setting no
>longer applies to it. You must explicitly enter a user
>account and password for the task.
>
>Examples
>To display a list of commands scheduled on the Marketing
>server, type:
>
>at \\marketing
>To learn more about a command with the identification
>number 3 on the Corp server, type:
>
>at \\corp 3
>To schedule a net share command to run on the Corp
server
>at 8:00 A.M. and redirect the listing to the Maintenance
>server, in the Reports shared directory, and the
Corp.txt
>file, type:
>
>at \\corp 08:00 cmd /c "net share
>reports=d:\marketing\reports >>
>\\maintenance\reports\corp.txt"
>To back up the hard drive of the Marketing server to a
>tape drive at midnight every five days, create a batch
>program called Archive.cmd, which contains the backup
>commands, and then schedule the batch program to run,
type:
>
>at \\marketing 00:00 /every:5,10,15,20,25,30 archive
>To cancel all commands scheduled on the current server,
>clear the at schedule information as follows:
>
>at /delete
>To run a command that is not an executable (that
is, .exe)
>file, precede the command with cmd /c to load Cmd.exe as
>follows:
>
>cmd /c dir > c:\test.out
>Formatting legend
>Format Meaning
>Italic Information that the user must supply
>Bold Elements that the user must type exactly as shown
>Ellipsis (...) Parameter that can be repeated several
>times in a command line
>Between brackets ([]) Optional items
>Between braces ({}); choices separated by pipe (|).
>Example: {even|odd} Set of choices from which the user
>must choose only one
>Courier font Code or program output
>
>>-----Original Message-----
>>Hello
>>
>>Windows Server 2000 SP4.
>>
>>How cand I schedule a task for a precise date using AT
>>command. For example: launch a prog.exe at 10am on 7
>>July 2004.
>>
>>Many thanks
>>
>>Pedro
>>.
>>
>.
>
- Next message: Khurram Naseem: "Memory Leak"
- Previous message: Jaime Dominguez: "black screen appears after several days up"
- Next in thread: Lanwench [MVP - Exchange]: "Re: AT command"
- Reply: Lanwench [MVP - Exchange]: "Re: AT command"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
