We have used the At command line in various batches successfully. All of the PCs used run Win NT4 SP6 or Win2K and have been logged on to the network using Administrator rights. Some of the PCs use the same logon username but most differ. All users logged on to these PCs have Administrator rights. Task scheduler service has default settings to use Log On As System Account and Interact With Desktop. Something has changed, now we have permissions problem when using the At command. Example i) batch file runs from PC1, starts a process on PC1, copies the files to PC2, sends an At command across network to PC2 to start a batch process located on PC2.
ii) Once the second process on PC2 has finished, the batch file started on PC2 by the At command then has to either copy files across the network using mapped drives at logon or has to start a third batch file for further processing/response across the network.
iii) This batch file now has to access a third PC across the network and this command line opened by the task scheduler has only got rights to access other mapped drives on PCs that have been logged on with the same user name. An error message “Access Denied” appears on the screen. If you open a new command prompt whilst the one started with the At command is still open, you have access to all mapped drives across the network. This is true for Windows explorer. On Win2K machines, the mapped drives in Explorer get a red cross displayed on top of each mapped device and if you single click them they reconnect like they were not really disconnected.
Things we have tried:
Microsoft support web site to search for solutions. Manuals, other NT4/Win2K users, changing user permissions in the Task Manager Service startup properties. Re-establishing trust relationships with the server. Logging on as Administrator on workstations. Creating local user accounts on the Workstations with Admistrators rights.