default drive mapping issues

  • Thread starter Thread starter David
  • Start date Start date
D

David

I need mapped drives to automatically be available to a service when the
W2000 server is rebooted. The application cannot use UNC conventions.
Currently, the drives are mapped by the a net use command fired off by the
scheduler on boot. I thought that I had thoroughly tested this setup, but
when I rebooted the server today the scheduler showed errors and the drives
were not available to the service. They were mapped when I logged into the
box, but I had to remove the mapping and fire off the commands in scheduler
before the service worked properly. While my hope is that this was an
anomaly of some sort, I could not take the time to experiment with it again
today, as the application needed to be available.
Has anyone found a failproof method to make this work reliably? I thought
that I had, but found out differently the hard way.
 
Hi David.

I don't know if this will help, but try mapping the drives persistently and then have
the application refer to them by the drive letter that they are mapped to. I know
that the connection is reestablished during boot up but it may be worth a try. A
startup script using net use may be another thing to try. Startup scripts run in
system context. Starup scripts can be configured via Local Group Policy/computer
confiuration/Windows settings.--- Steve
 
What was odd when I had the problem was that net use showed the drives as
mapped, but the application could not access them. I assume that, since the
default is persistent, that the mapping survived the reboot because of that.
Why they were not usable is another issue entirely. Another thought was to
do the net use statement using the scheduler, but flag it to not be
persistent. I will most likely not get to test this until Monday, but I
will update the results here.
 
Back
Top