Drive map "priority"

[Jeff Brooks-Manas]

All,

There are some drive letters that map no matter what script the users have,
and I 'm not sure why... The drives were never mapped using a net use
statement or script, and yet the continue to appear. Adding net use u:
/delete /y before the mapping statement gets rid of them, but I want to know
why they are there in the first place. The drives that map are on the
original AD controller.

Thanks!

Jeff

 

[Herb Martin]

Usually left over from some prior boot. The default is to map
"persistently"
so if a user has ever mapped that letter (without a later /d ) then it is
probably
still mapped.

 

[Jeff Brooks-Manas]

This happens on the first login. The script just maps two drives, and yet
there are 5 shares mapped.

Thanks!

Jeff

 

[Herb Martin]

First login? Then this must? be coming from either the default profile
(did you guys setup custom default profiles) or from a GPO, etc.

I don't think that the machine can do this on it's own (e.g., no "computer"
registry setting does this -- I believe.)

How about GPOs?

I don't think the "All Users" profile can do this -- it only appends stuff
to
the Start Menus & Desktops.

How about unexpect script files or startup programs? (User properties on
the Profile tab, etc....)

 

[Jeff Brooks-Manas]

GPO's was the ticket. I set up the main server so long ago that I forgot all
about that.

Thanks!

Jeff