Stop remembering network mappings

  • Thread starter Thread starter rb
  • Start date Start date
R

rb

Hi,

I have a laptop that I use at work and at home. At work, logon scripts maps
drives that I need while I'm there. At home, however, when I log in, vista
tries to reconnect those drives. That "freezes" the computers for a few
minutes and then a bubble pops up from System Tray saying that "could not
reconnect...".

The question is: how do I tell Vista to stop remembering mapped drives
between 2 log ins?

Thanks.
 
rb said:
Hi,

I have a laptop that I use at work and at home. At work, logon scripts
maps
drives that I need while I'm there. At home, however, when I log in, vista
tries to reconnect those drives. That "freezes" the computers for a few
minutes and then a bubble pops up from System Tray saying that "could not
reconnect...".

The question is: how do I tell Vista to stop remembering mapped drives
between 2 log ins?

Thanks.
Click to expand...


Improve your login script to remove them first
 
Improve your login script to remove them first
Click to expand...

Is that all that can be done? Is there no registry hacks or anything like
that? I mean, I work in a domain environment and logon scripts have been
developed to work for all users; not to mention that scripts "cascade" (call
other scripts).

Thanks.

rb
 
Oh, and another thing: at work, the script from a DC may first delete and
then map new drives, but that doesn't solve the problem when I get home. At
home, there *are* not scripts to run; therefore, anything previously mapped
will be destroyed.

OTOH, if I put anything in startup, at work it will run *after* logon script
and will delete anything that script already created.

Is there a way out of this maze??

Thanks.
 
rb said:
Oh, and another thing: at work, the script from a DC may first delete and
then map new drives, but that doesn't solve the problem when I get home.
At home, there *are* not scripts to run; therefore, anything previously
mapped will be destroyed.

OTOH, if I put anything in startup, at work it will run *after* logon
script and will delete anything that script already created.

Is there a way out of this maze??

Thanks.
Click to expand...

Your script in startup could detect the current situation ie whether you're
connected to work or home, and then dependent on that either delete or don't
delete the previous mappings.

That's one way. There may well be other approaches, though
 
rb submitted this idea :
Is that all that can be done? Is there no registry hacks or anything like
that? I mean, I work in a domain environment and logon scripts have been
developed to work for all users; not to mention that scripts "cascade" (call
other scripts).

Thanks.

rb
Click to expand...

If you are the domain admin, or have some say over the logon scripts, have them
(or you) remove the /persistent:yes at the end of the net use {driveletter}
line. Or make it /persistent:no - that way, the drive mappings will not be
there the next time you boot, but will be added by the logon script.
 
Back
Top