loading library from network share (PR#8982)

I had thought that one needed to be careful using mapped network drive 
letters to access network shares under MS Windows -- the current mapping 
for drive letters can depend on who is current logged in.   For 
non-critical interactive sessions there should be no problems with using 
mapped network drive letters -- the dangerous scenario is running 
scheduled tasks on a server.

Microsoft XP docs say:
     Connecting to network drives

     Do not use a redirected drive for scheduled jobs
     that access the network. The Schedule service
     might not be able to access the redirected drive,
     or the redirected drive might not be present if a
     different user is logged on at the time the
     scheduled task runs. Instead, use UNC paths for
     scheduled jobs. For example:

     at 1:00pm my_backup \\server\share

     Do not use the following syntax, where x: is a
     connection made by the user:

     at 1:00pm my_backup x:

(this is from the documentation for the "At" command, 
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/at.mspx?mfr=true
)

In addition to Prof Ripley's suggestion of setting up drive mapping 
using domain controllers, another workaround might be doing something 
like "net use x: \\server\share" in a scheduled task script.

-- Tony Plate

loading library from network share (PR#8982)

Thread (3 messages)