Mapping Drive that's not available???

[Ken Mulh]

Is there any way to create a persistant map to a network drive that may
not be accessable when the mapping is attempted? The network drive may
not be available when the user boots and this mapping is being done from
logon scripts. I would like the map to be persistant so they can use it
when it's available.

Thanks.

 

[Lanwench [MVP - Exchange]]

In

Is there any way to create a persistant map to a network drive that
may not be accessable when the mapping is attempted? The network
drive may not be available when the user boots and this mapping is
being done from logon scripts. I would like the map to be persistant
so they can use it when it's available.

Thanks.

I don't recommend persistent drive mappings on clients - it makes your work
as an admin harder when you want to change things around. Why wouldn't the
network drive be available? Is this on a server, or another workstation?
That's the first thing I'd look at.

You can always put a shortcut to the login script on the user's desktop, I
suppose. My standard batch file login script commands include /persistent:no
for reasons mentioned above.

 

[SimonCheung]

I use KIXTART script to manual map the home share instead of use "NET
USE" command.


The KIXTART script is below

use H: /del

use H: "@HOMESHR\@HOMEDIR"


The first line is to disconnect incorrect path then reconnect share.

Hope this can help.