Lost map drives upon rebstart of w2k server

  • Thread starter Thread starter Jimb
  • Start date Start date
J

Jimb

Every time I restart my w2k server all of my mapped drives
are lost. doesn't matter which subnet they point to...
they are all mapped to Snap Servers.
 
Is there any other way to keep the drives mapped after
restarting the server without using the Registry?
 
I can't think of any. It's a server so you want the drives to be mapped w/o
user intervention.

This is the best way I can think of.

What's wrong with the idea ? No experience using the Registry Run command(s) ?

Dave

| Is there any other way to keep the drives mapped after
| restarting the server without using the Registry?
 
Suppose you could write a bat/cmd file to map them and use Task
Scheduler to run the file at computer startup.
Is there any other way to keep the drives mapped after
restarting the server without using the Registry?



-----Original Message-----
If you need a mapped drive at boot up try mapping the
drives using 'net use' in
Registry:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersi
on\Run


Example:

Windows Registry Editor Version 5.00


[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersi
on\Run]

"map p"="net use p: \\\\server\\share"



Dave


.
 
Turns out that the 2000 srv login didn't match the Snap
Srv login

fixed now

-----Original Message-----
Suppose you could write a bat/cmd file to map them and use Task
Scheduler to run the file at computer startup.
Is there any other way to keep the drives mapped after
restarting the server without using the Registry?



-----Original Message-----
If you need a mapped drive at boot up try mapping the
drives using 'net use' in
Registry:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVer si
on\Run


Example:

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersi
on\Run]
"map p"="net use p: \\\\server\\share"



Dave


.

.
 
Back
Top