NT 'at' permissions??

[killRoy]

Sorry, not entirely programming related...

When I run a batch file on a server at its console to copy some files from it to another machine, it works.

When I use the 'at' utility to execute it in a scheduled way, it doesn't.

I'm thinking it might be a permissions problem. When I run from the console, I am logged in as Administrator.

Can anyone tell me what permission set 'at' belongs to in Windows NT? Is it SYSTEM? The computer name?

Dazed and confused

Thanks for any help!

- killRoy

[Andyb]

I'm not sure is 'at' uses a 'run as' feature.

i.e. run as adminsistrator. Long time since I looked at at. Sorry.

[coolbiz]

Most of the time it will queue it as Administrator (or at least someone with administrative rights). Note also that you need administrative rights to queue something remotely.

AT is a little wacky to use. It took me a while to get it right with all the parameters and stuff. There is another utility called RUNNOW (if I'm not mistaken) which simplifies AT a lot.

I resolved to write my own UI to work with Scheduler APIs to schedule stuff because of those complications.

Good Luck,
-Cool Bizs