Re: Mapped F Drive - group policy update problem

Dave,
This has been an ongoing problem that we have been fighting and I am not
sure that the problem is resolved. Recently I found this Group Policy Setting
and applied it. Up to today, we have not had the problem reported. Perhaps
this will help your environment also. Let me know, and we can find a solution
together since Microsoft hasn't been very helpful with this posting.

This is not the only location that I have posted this issue, I also posted
it in other newsgroups but have only received replies here.

Domain Policy
Computer Configuration - Administrative Templates - System - Logon
Always wait for the network at computer startup and logon
Enabled
----
Ever since XP has been added to our domain environment, we have seen all
types of logon issues happen and I believe the problem is because MS has
changed the order in which things occurr such as when group policy applies,
when authentication happens, DHCP renewals and leases, etc. but it is
difficult to prove. I believe that this group policy description helps
confirm my theories, but you be your own judge....

---
Determines whether Windows XP waits for the network during computer startup
and user logon. By default, Windows XP does not wait for the network to be
fully initialized at startup and logon. Existing users are logged on using
cached credentials, which results in shorter logon times. Group Policy is
applied in the background once the network becomes available.

Note that because this is a background refresh, extensions such as Software
Installation and Folder Redirection take two logons to apply changes. To be
able to operate safely, these extensions require that no users be logged on.
Therefore, they must be processed in the foreground before users are actively
using the computer. In addition, changes that are made to the user object,
such as adding a roaming profile path, home directory, or user object logon
script, may take up to two logons to be detected.

If a user with a roaming profile, home directory, or user object logon
script logs on to a computer, Windows XP always waits for the network to be
initialized before logging the user on.

If a user has never logged on to this computer before, Windows XP always
waits for the network to be initialized.

If you enable this setting, logons are performed in the same way as for
Windows 2000 clients, in that Windows XP waits for the network to be fully
initialized before users are logged on. Group Policy is applied in the
foreground, synchronously.

If you disable or do not configure this setting, Windows does not wait for
the network to be fully initialized and users are logged on with cached
credentials. Group Policy is applied asynchronously in the background.

Note: If you want to guarantee the application of Folder Redirection,
Software Installation, or roaming user profile settings in just one logon,
enable this setting to ensure that Windows waits for the network to be
available before applying policy.

Note: For servers, the startup and logon processing always behaves as if
this policy setting is enabled.

"Dave" wrote:

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.



.

Relevant Pages

  • Re: Mapped F Drive - group policy update problem
    ... where is the fast optimization group policy that you ... Always wait for the network at computer startup and logon ... Determines whether Windows XP waits for the network during computer startup ...
    (microsoft.public.windows.server.active_directory)
  • Re: Huh? "Login failure: the user has not been granted the requested logon type at this compute
    ... I'm a pretty experienced Windows user and programmer, ... the user has not been granted the requested logon type ... on the appropriate OU to see the Group Policy for that OU]. ... > administrators' group to the domain controller. ...
    (microsoft.public.security)
  • RE: Login scripts not executing
    ... We are using windows 2003 in bothe the forests. ... We are not using Group Policy for logon scripts, ... controller and given the path in the user properties-profiles-logon scripts. ...
    (microsoft.public.win2000.active_directory)
  • Re: Mapped F Drive - group policy update problem
    ... XP but also causes time problems with the network services connecting fully. ... Recently I found this Group Policy Setting ... Computer Configuration - Administrative Templates - System - Logon ... Determines whether Windows XP waits for the network during computer startup ...
    (microsoft.public.windows.server.active_directory)
  • Re: Problem using folder redirection and TweakUI automatic logon
    ... my understanding on this issue is: the Windows logon ... the network to be fully initialized during startup and the logon process. ... logon] group policy to disable fast logon feature to test: ...
    (microsoft.public.windows.server.sbs)