Hello,

I'm working on using Group Policy Preferences for drive mapping, and
am a little confused about the reconnect option.

http://social.technet.microsoft.com/wiki/contents/articles/12221.troubleshooting-the-drive-maps-preference-extension-in-group-policy-replace-mode-only-maps-the-drive-every-other-logon.aspx
is pretty much exactly the scenario I'm curious about (reconnect not
set). It says:

-----
Expected Result: Drive Z: is mapped to \\CONTOSO-DC\netlogon every
time the user logs on to their computer.

Actual Result: Drive Z: is only mapped to \\CONTOSO-DC\netlogon every
other time the user logs on.

Note: This difference in when Drive Z is mapped will only be
noticeable if either the administrator first deletes all mapped drives
at the start of processing Group Policy or the user has changed Drive
Z during their previous session.
-----

I am confused about that Note. It seems to imply that the Z drive will
be mapped correctly on subsequent logons (assuming no one has changed
or deleted Drive Z), even though the drive maps preference extension
doesn't apply preferences on every logon (because some logons process
GP asynchronously).

Is it the case that if the user does not modify the drive mappings,
the drive mapping will be 'correct' on next logon? This implies there
is some sort of caching of drive mappings other than the caching that
would occur if 'reconnect' were set. Is that correct?

Those of you that use GPP for drive mappings, do you have the
'reconnect' option set or not? Why?

Thanks,
Elijah Buck

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

Reply via email to