Re: Mapped F Drive - group policy update problem
- From: Dave <Dave@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 17 Mar 2006 01:46:29 -0800
Hi,
We are having the same problem. We also have a Windows2003 AD Domain with
WindowsXPSP2 Clients. This is random if you restart or logoff and back on
again the drives maps correctly.
It has been suggested that we drop Mapped Home directories in favour for
Folder Redirection for MyDocuments. This however while be a knightmare as our
users save work locally(not our policy) and on the network. This still doesnt
explain why it is happening. Microsoft please help!
There are no errors in local or server event logs either. How do you trace
this problem?
Anyone have any answers?
Regards
Dave
"Gabriel Simmons" wrote:
Although I did not know about this policy even existing and is good.
information to know, it has not been configured anywhere within our domain. I
did change the domain policy so that this policy will be disabled instead of
just Not Configured. Perhaps this will correct the problem. We'll have to
wait and see.
If this setting is disabled or not configured (Windows 2000 Server Family
behavior):
"chriss3 [MVP]" wrote:
Ensure you not have defined the follow policy setting:
User Configuration\Administrative Templates\System\User Profiles\Connect
home directory to root of the share
Within a applied GPO.
--
Regards
Christoffer Andersson
Microsoft MVP - Directory Services
No email replies please - reply in the newsgroup
------------------------------------------------
http://www.chrisse.se - Active Directory Resources
"Gabriel Simmons" <GabrielSimmons@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:106EA514-983B-4A82-8786-9C9A1E2F0A48@xxxxxxxxxxxxxxxx
We have a Windows 2003 Active Directory domain setup. When a user logs on
to
the network from a Windows XP computer with SP2 installed, the home drive
sometimes maps as it is supposed to, but not all the time. The home folder
is
set to map in the user properties of
AD to map F:\ to \\sancluster\Users$\%USERNAME%. Sometimes the F Drive is
mapped to \\sancluster\Users$ instead of to \\sancluster\Users$\%USERNAME%
like it should be based on the AD user properties.
We also have this mapping to get set in user login scripts (net use F:
\\sancluster\USERS$\%USERNAME%).
I have tried changing the login scripts to delete the mapping first so
that
it will force the user F: drive to \\sancluster\USERS$\%USERNAME%, but it
does not always map if the delete statement is also in the login script.
One other thing I have noticed is that when group policy updates in the
background refresh according to Application Event Log with ID 1704, then
the
drive is sometimes disconnected and reconnected to \\sancluster\Users$
instead of the \\sancluster\Users$\%USERNAME%. This background group
policy
update undermines the login scripts.
- Follow-Ups:
- Re: Mapped F Drive - group policy update problem
- From: Gabriel Simmons
- Re: Mapped F Drive - group policy update problem
- Prev by Date: Re: one interesting question about ntds.dit
- Next by Date: How can I get AD to ADAM sync works?
- Previous by thread: Join Domain Automatic
- Next by thread: Re: Mapped F Drive - group policy update problem
- Index(es):
Relevant Pages
|
