none
Remove Folder Redirection setting from an existing GPO

    Question

  • Hi,

    We have a main policy for our company that contained settings including folder redirections. Since last week we made a new policy that ONLY contains the folder redirections. After doing that, we put the folder redirections from the main policy to Not Configured. However, this gives issues as the folder redirections get mixed settings for the users from our company.

    So I was wondering how we could solve this. We DON'T want to remove the MAIN POLICY as it still contains other settings that we still need for the company.

    Right now, it still shows 'Not Configured' as a setting which can overwrite the other policy if not enforced or given priority with the Link Order.

    I hope to hear from you soon.

    Tuesday, February 02, 2016 4:23 PM

Answers

  • Am 03.02.2016 um 11:51 schrieb Martin Binder [MVP]:
    > {25537BA6-77A8-11D2-9B6C-0000F8080861}{88E729D6-BDC1-11D1-BD2A-00C04FB9603F}
    > Update: Remove this and its surrounding GUIDs, the whole block in square
    > brackets []
     
    Update Update :-)
    not surrounding GUIds, but brackets ...
     
    If you find something like this:
    [{25537BA6-77A8-11D2-9B6C-0000F8080861}{88E729D6-BDC1-11D1-BD2A-00C04FB9603F}]
    [{35378EAC-683F-11D2-A89A-00C04FBBCFA2}{0F6B957E-509E-11D1-A7CC-0000F87571E3}]
     
    Remove:
    [{25537BA6-77A8-11D2-9B6C-0000F8080861}{88E729D6-BDC1-11D1-BD2A-00C04FB9603F}]
     
    ... otherwise you would delete the AdmTemplate(Registry) Settings
     
    Mark
    --
    Mark Heitbrink - MVP Windows Server - Group Policy
     
    GPO Tool: http://www.reg2xml.com - Registry Export File Converter
     
    Wednesday, February 03, 2016 12:54 PM

All replies

  • Hi,
     
    Am 02.02.2016 um 17:23 schrieb Bram Buermans:
    > Right now, it still shows 'Not Configured' as a setting
     
    - get GUID of GPO and navigate to the GP Object in adsiedit.msc
    - remove
    {25537BA6-77A8-11D2-9B6C-0000F8080861}{88E729D6-BDC1-11D1-BD2A-00C04FB9603F}
    from gPCUSerExtensionsName Attribute
    - remove fdeploy* from SYSVOL\..\policies\guidofgpo
     
    Mark
     
    --
    Mark Heitbrink - MVP Windows Server - Group Policy
     
    GPO Tool: http://www.reg2xml.com - Registry Export File Converter
     
    Tuesday, February 02, 2016 5:17 PM
  • I've already tried removing the fdeploy.ini and the fdeploy1.ini but that gave an error in the policy view. I will try tomorrow with the ExensionsName attribute thing as I was not aware of that. Thank you for providing that information. It is probably the crucial part that we missed.
    Tuesday, February 02, 2016 8:00 PM
  • >After doing that, we put the folder redirections from the main policy to Not Configured.
     
    If the “Policy Removal” option has been set to “Leave the folder in the new location when policy is removed”, then the folder redirection would stay how it is currently configured with the folder(s) redirected. To stop File Redirection correctly, you should first update the GPO and set the “Policy Removal” to “Redirect the folder back to the user profile location when policy is removed” and then change the redirection option to “Not Configured”.
     
    For the detailed steps on how to stop Folder Redirection, please refer to this KB article: https://support.microsoft.com/en-us/kb/888203 (It's for Windows 2003, but the steps should hold good for other server platform)
     
    Also, please note that running “gpupdate /force” won’t update Folder Redirection policy. All users who are affected by your GPO modification must log off and back on to any computers where they have logged on before the changes are applied.
     

    Regards,

    Ethan Hua


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

    Wednesday, February 03, 2016 6:25 AM
    Moderator
  • Hi
     
    Am 02.02.2016 um 21:00 schrieb Bram Buermans:
    > I've already tried removing the fdeploy.ini and the fdeploy1.ini
     
    This is only "configuration information" for the client.
    The gPCextensionsname provides the information for GPEditor and Client,
    which component to use for displaying in editor and aswell which one to
    use to import the files on the client.
     
    Mark
    --
    Mark Heitbrink - MVP Windows Server - Group Policy
     
    GPO Tool: http://www.reg2xml.com - Registry Export File Converter
     
    Wednesday, February 03, 2016 8:03 AM
  • > {25537BA6-77A8-11D2-9B6C-0000F8080861}{88E729D6-BDC1-11D1-BD2A-00C04FB9603F}
     
    Update: Remove this and its surrounding GUIDs, the whole block in square
    brackets [].
     
    One GUID identifies the client side extension, the other identifies the
    corresponding MMC Snapin Extension for GPEdit.
     
    Wednesday, February 03, 2016 10:51 AM
  • Am 03.02.2016 um 11:51 schrieb Martin Binder [MVP]:
    > {25537BA6-77A8-11D2-9B6C-0000F8080861}{88E729D6-BDC1-11D1-BD2A-00C04FB9603F}
    > Update: Remove this and its surrounding GUIDs, the whole block in square
    > brackets []
     
    Update Update :-)
    not surrounding GUIds, but brackets ...
     
    If you find something like this:
    [{25537BA6-77A8-11D2-9B6C-0000F8080861}{88E729D6-BDC1-11D1-BD2A-00C04FB9603F}]
    [{35378EAC-683F-11D2-A89A-00C04FBBCFA2}{0F6B957E-509E-11D1-A7CC-0000F87571E3}]
     
    Remove:
    [{25537BA6-77A8-11D2-9B6C-0000F8080861}{88E729D6-BDC1-11D1-BD2A-00C04FB9603F}]
     
    ... otherwise you would delete the AdmTemplate(Registry) Settings
     
    Mark
    --
    Mark Heitbrink - MVP Windows Server - Group Policy
     
    GPO Tool: http://www.reg2xml.com - Registry Export File Converter
     
    Wednesday, February 03, 2016 12:54 PM