Why won't the AT command run .cmd files?

  • Thread starter Thread starter Bob
  • Start date Start date
They work fine for me.

What does "assoc .cmd" tell you?

Are you trying to execute a .cmd file on network drive that the AT account
does not have permissions to?

Ray at work
 
Ray-

I might have found out what's taking place. The .cmd works
as stand alone but not called when using the AT command.
What I found was Microsoft has two other utils in the
resource toolkit that do better jobs than the AT command.
They are psexec.exe and jt.exe I will look at both and
see which works best. Thanks for the quick response!!!

Bob
 
Bob wrote in
Ray-

I might have found out what's taking place. The .cmd works
as stand alone but not called when using the AT command.
What I found was Microsoft has two other utils in the
resource toolkit that do better jobs than the AT command.
They are psexec.exe and jt.exe I will look at both and
see which works best. Thanks for the quick response!!!

JT.EXE is what you want to do Task Scheduler mods from the cmd-line.
PSEXEC (Sysinternals) is very useful, but not for scheduling per se.
 
Back
Top