none
Folder Redirection Policy Change

    Question

  • There exists in the default domain policy a folder redirection policy for Documents to go to a file server directory.  We recently replaced file server and changed the redirection to go to new location.  Most of the clients have taken this new folder redirectoin path and applied it.  However many clients still point to the old server for folder redirection despite many reboots and "gpudate /forces".  How can I move these remaining clients to the new server without affecting clients that have already transferred successfully.  Is there something wrong with the group policy on these windows 7 machines that I can check?  The servers are running 2012 r2 and 2008 r2 domain controllers.

    Wednesday, June 01, 2016 1:06 AM

Answers

  • Hi,

    Have you tried the below settings?

    Enabling "Always wait for the network at computer startup and logon" via group policy should resolve it as we need to give system more time to initiate network before proceeding with the logon process.

    We could also enable "Startup Policy Processing Wait Time" and setting wait time to an appropriate value to let the software installation GPOs working with minimal boot delays. We could know the accurate policy processing time via the Group Policy Operational Log Event. Please refer to the following article to get more details:

    Optimizing Group Policy Performance

    https://technet.microsoft.com/en-us/magazine/2008.01.gpperf.aspx


    There are two ways to enable this option:

    Group Policy
    Computer Configuration > [Policies] > Administrative Templates > System >Group Policy > Startup Policy Processing Wait Time – Enable the option and set wait time to 10 - 60 seconds
    Note 1: This option is only supported by Windows Vista and later clients and may be not present on Server 2003 domain controllers
    Note 2: Group policy description tells that the default wait time is 30 seconds, which obviously raises the question how setting time-out to less than 30 seconds can fix the problem. It seems that default 30 seconds interval is not always used and Windows often employs its own algorithms to calculate the time-out (if it's not enforced by Group Policy or Registry)

    Registry
    On Client Computer:

    1. Start > Regedit.exe

    2. Navigate to  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon

    3. Create New DWORD value with name GpNetworkStartTimeoutPolicyValue and set Value data (decimal) to the required timeout interval in seconds

    4. Restart the computer

    Hope the above information is helpful to you.

    Best Regards,

    Alvin Wang


    Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, June 03, 2016 5:23 AM
    Moderator

All replies

  • Hi,

    I would do the following:

    -  Perform a gpresut on one of the affected machines and see if there are any error messages

    - Check the following log and paste any error messages that are in there:

    Application and services log\Microsoft\Windows\Folder Redirection\Operational

    Jason

    Wednesday, June 01, 2016 2:16 AM
  • Hi,

    Thanks for your post.

    Please try to disable the original redirection policy, logoff users and enable the new policy.

    Here is an article which provided many suggestions about Folder Redirection. You can have a try on the steps like Repair Folder Redirection part.

    Folder Redirection

    http://msmvps.com/blogs/acefekay/archive/2009/09/08/folder-redirection.aspx

    Besides, I would like suggest you go through the below similar threads for details:

    Changed Folder Redirection GPO, but setting will not take affect

    http://social.technet.microsoft.com/Forums/en-US/winserverGP/thread/25f2d9ba-881b-430c-bb72-03a124254dc3

    Moving Redirected Folder Location

    http://social.technet.microsoft.com/Forums/en-US/winserverGP/thread/09991589-5137-43c9-b29d-3102dc3ededd/

    Hope this helps.

    Best Regards,

    Alvin Wang


    Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, June 01, 2016 6:10 AM
    Moderator
  • Hi Jason,

    It looks like the folder redirection is getting applied according to the operational log you specified.  However in the standard application log in event viewer it is showing warning 510 the folder redirection is delayed until the next login due to group policy logon optimization in effect.  It keeps saying this every day.  i also have wait for network to start now before logging in but it doesn't seem to matter.

    Thursday, June 02, 2016 4:09 AM
  • Hi,

    Have you tried the below settings?

    Enabling "Always wait for the network at computer startup and logon" via group policy should resolve it as we need to give system more time to initiate network before proceeding with the logon process.

    We could also enable "Startup Policy Processing Wait Time" and setting wait time to an appropriate value to let the software installation GPOs working with minimal boot delays. We could know the accurate policy processing time via the Group Policy Operational Log Event. Please refer to the following article to get more details:

    Optimizing Group Policy Performance

    https://technet.microsoft.com/en-us/magazine/2008.01.gpperf.aspx


    There are two ways to enable this option:

    Group Policy
    Computer Configuration > [Policies] > Administrative Templates > System >Group Policy > Startup Policy Processing Wait Time – Enable the option and set wait time to 10 - 60 seconds
    Note 1: This option is only supported by Windows Vista and later clients and may be not present on Server 2003 domain controllers
    Note 2: Group policy description tells that the default wait time is 30 seconds, which obviously raises the question how setting time-out to less than 30 seconds can fix the problem. It seems that default 30 seconds interval is not always used and Windows often employs its own algorithms to calculate the time-out (if it's not enforced by Group Policy or Registry)

    Registry
    On Client Computer:

    1. Start > Regedit.exe

    2. Navigate to  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon

    3. Create New DWORD value with name GpNetworkStartTimeoutPolicyValue and set Value data (decimal) to the required timeout interval in seconds

    4. Restart the computer

    Hope the above information is helpful to you.

    Best Regards,

    Alvin Wang


    Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, June 03, 2016 5:23 AM
    Moderator