at commands with NT

[jmlozan]

anyone know of a good site that has a list of and explanations for the various at commands with NT? Thanks.

[cordon]

Taken from http://www.cantug.ab.ca/tips.html
Which also has some links to other tips sites.
Q. The AT command does not work
A. A requirement to use AT is a running Schedule service. To start it, type 'net start schedule' on the command line or use Control Panel/Services (if you want to use it regularly, set the Startup Type to Automatic). A common problem is that people try to use the example given in the online help: AT sometime CMD /C DIR > TEST.OUT.
Unfortunately, in NT 4.0, this does not work anymore. You must use
AT sometime CMD /C "DIR > TEST.OUT" instead. The execution of the command starts by default in %systemroot%\system32, as can be seen from the output of the above example. You should specify the complete path if the command is in a different directory,
e.g. AT sometime C:\TEMP\TEST.BAT. A further problem is that the command is executed in the security context of the LOCAL SYSTEM account, not the caller. However, the SYSTEM account does not have access to network resources, so your program cannot reside or access files on mapped drives (even if they are mapped from the local machine!). Also, environment variables (e.g. PATH) may be set differently. You can test the environment interactively with AT sometime /INTERACTIVE CMD.

AND
From http://www.ime.net.au/nttips.htm

While you can use the AT command at the command prompt it's real power lies with batch files.

To use the AT command you first need to start the Schedule Service by opening Control Panel, Services, then starting the Schedule service. Now for the gotcha! Before you close the Services dialog, double click the Schedule entry. This opens another dialog that you use to enter a user account name that has permissions for the task you want to perform. If the Schedule service was already running, make sure you stop it then start it again and, if the task you want to perform is over a network, make sure that the original network connection is broken before you run the AT command.




[This message has been edited by cordon (edited November 01, 2000).]