Homerboy
Lifer
I'm not sure how to explain this clearly, but here it goes...
I have a scheduled task on a 2K3 server that runs a small .bat file that opens an application that is stored on a Win2K3 Storage Server machine.
The application is to run on the 2k3 server, but requires mapped resources from the Storage Server. (specifically a mapped "F" drive).
If this task runs while I am logged into the 2k3 server, it runs fine and completes.
When the task attempts to run while I am logged out of the 2k3 machine, it does not run.
Tossing a netuse into the .bat file and generating a makeshift logfile, it seems the networked drives aren't mapping properly when the task runs itself with me logged out.
C:\WINDOWS>net use
New connections will be remembered.
Status Local Remote Network
-------------------------------------------------------------------------------
Unavailable E: \\files\storage Microsoft Windows Network
Unavailable F: \\files\cls Microsoft Windows Network
What's super odd is when I run this on a Win2K3 machine and the remote server is Win2k3 also (not Storage Server flavor) it works perfectly fine.
Long story short, is there some issue with network drives being mapped via schedule task login when the server side OS is Storage Server?
I know that's all confusing as hell.... I can't even figure out how to describe the issue at this point.
I have a scheduled task on a 2K3 server that runs a small .bat file that opens an application that is stored on a Win2K3 Storage Server machine.
The application is to run on the 2k3 server, but requires mapped resources from the Storage Server. (specifically a mapped "F" drive).
If this task runs while I am logged into the 2k3 server, it runs fine and completes.
When the task attempts to run while I am logged out of the 2k3 machine, it does not run.
Tossing a netuse into the .bat file and generating a makeshift logfile, it seems the networked drives aren't mapping properly when the task runs itself with me logged out.
C:\WINDOWS>net use
New connections will be remembered.
Status Local Remote Network
-------------------------------------------------------------------------------
Unavailable E: \\files\storage Microsoft Windows Network
Unavailable F: \\files\cls Microsoft Windows Network
What's super odd is when I run this on a Win2K3 machine and the remote server is Win2k3 also (not Storage Server flavor) it works perfectly fine.
Long story short, is there some issue with network drives being mapped via schedule task login when the server side OS is Storage Server?
I know that's all confusing as hell.... I can't even figure out how to describe the issue at this point.
