Hi Michael,
You don't need to go to every machine to issue the AT command, you can do it remotely. At a command prompt type
AT /? - the output will list the command's options. Here's what I get (under win2k):
The AT command schedules commands and programs to run on a computer at
a specified time and date. The Schedule service must be running to use
the AT command.
AT [\\computername] [ [id] [/DELETE] | /DELETE [/YES]]
AT [\\computername] time [/INTERACTIVE]
[ /EVERY:date[,...] | /NEXT:date[,...]] "command"
\\computername Specifies a remote computer. Commands are scheduled on the
local computer if this parameter is omitted.
id Is an identification number assigned to a scheduled
command.
/delete Cancels a scheduled command. If id is omitted, all the
scheduled commands on the computer are canceled.
/yes Used with cancel all jobs command when no further
confirmation is desired.
time Specifies the time when command is to run.
/interactive Allows the job to interact with the desktop of the user
who is logged on at the time the job runs.
/every:date[,...] Runs the command on each specified day(s) of the week or
month. If date is omitted, the current day of the month
is assumed.
/next:date[,...] Runs the specified command on the next occurrence of the
day (for example, next Thursday). If date is omitted, the
current day of the month is assumed.
"command" Is the Windows NT command, or batch program to be run.
Cheers,
Andrew
>The problem with NT4 is that users on a domain do not defaultly have permission to change the time, as well as going thru a proxy server for limited access, cannot call upon a web clock. I would like to get time sync them with a server here, but did not want to access every computer to change the permission as normally we don't want users to be able to change the clock time. I have looked at the AT command with NT SDK, but do not like that again, I have to make an entry for every computer I wish to do this.
>I would like to make a batch file that is either called up at logon or can be sent out to all the computer and ran.
If we were to introduce Visual FoxBase+, would we be able to work from the dotNet Prompt?
From Top 22 Developer Responses to defects in Software
2. "It’s not a bug, it’s a feature."
1. "I thought I fixed that."
All my FoxTalk and other articles are available on my
web site.
Unless specifically identified otherwise, anthing posted here is purely my opinion and may or may not reflect the policies or practices of Microsoft.