Incorrect Home Folder Mapping

21 בדצמבר 2008

אין תגובות

Symptoms

Users' Home Folder maps incorrectly on workstations.
The home folder is mapped to the base share instead of the complete path to the profile.
This only happens on PCs. When logging on to terminal servers the mapping is done correctly.

Example:
Home folder set to: \\fileServer\Company\Department\UserName
The mapping that the user receives : \\fileServer\Company
Manually mapping the path completes successfully and all files are accessible.

The users are the owners of their folders and all permissions are sufficient for drive mapping.  

 

Cause

Network delays may cause the workstation to try and map the home folder before completely initializing networking during logon.

 

Resolution

Apply the following setting using GPO :

Computer Configuration / Administrative Templates / System / Logon / Always wait for the network at computer startup and logon

 

More Information

 

Description of the Windows XP Professional Fast Logon Optimization feature
http://support.microsoft.com/kb/q305293/

 

Info from the policy's description

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.

Quote from Microsoft's Official eBook "Configuring Windows Server 2008 Active Directory"

"It is highly recommended that you enable the Always Wait For Network At Startup And Logon policy setting for all Windows XP and Windows Vista clients. Without this setting, by default, Windows XP and Windows Vista clients perform only background refreshes (of GPOs), meaning that a client might start up and a user might log on without receiving the latest policies from the domain."

הוסף תגובה
facebook linkedin twitter email

כתיבת תגובה

האימייל לא יוצג באתר. שדות החובה מסומנים *