Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Folder redirection policy fails after you redirect a folder to a different sub folder in Windows 7 or Windows Server 2008 R2


View products that this article applies to.

Symptoms

Consider the following scenario:
  • A client computer that is running Windows 7 or Windows Server 2008 R2 is in an Active Directory domain.
  • You use a Group Policy Object (GPO) to configure the folder redirection policy to redirect a document folder to a share folder. For example, you configure the following path: \\userst\s\1\prefs\appdata.
  • You use the GPO to configure the folder redirection policy to redirect the document folder to a different sub folder in the same share folder. For example, you configure the following path: \\userst\s\1\appdata.
  • You log on to the domain from the client computer, and then you try to open the redirected share folder.

In this scenario, the folder redirection policy fails. Therefore, you cannot open the redirected share folder. Additionally, an event that resembles the following is logged in the event log:

Note Before you redirect the folder to a different sub folder, the folder redirection policy works as expected.

↑ Back to the top


Cause

This issue occurs because the GPO does not copy the redirected folder to the destination folder when you change the redirected folder in Windows 7 or Windows Server 2008 R2 by using GPO. Instead, the GPO tries to copy the redirected folder to the offline file cache. However, before the GPO copies the files to the offline file cache, the GPO sets the share folder to offline mode. Therefore, when the source folder and the destination folder are in the same share folder, the CopyFolders function fails.

↑ Back to the top


Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.


If you experience the issue that is described in this article, pin the original share folder (the share folder that corresponds to the \\userst\s\1\prefs\appdata path in the example in the 'Symptoms' section) on the computer after you install the hotfix. To do this, follow these steps:
  1. Open Windows Explorer.
  2. Right-click the share folder that you want to pin on the computer.
  3. Click Always available offline.

Prerequisites

To apply this hotfix, you must be running one of the following operating systems:
  • Windows 7
  • Windows 7 Service Pack 1 (SP1)
  • Windows Server 2008 R2
  • Windows Server 2008 R2 Service Pack 1 (SP1)
For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To apply this hotfix, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows 7 and Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
    VersionProductMilestoneService branch
    6.1.760
    0.21xxx
    Windows 7 and Windows Server 2008 R2RTMLDR
    6.1.760
    1.22xxx
    Windows 7 and Windows Server 2008 R2SP1LDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows 7 and for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 7
File nameFile versionFile sizeDateTime
Shell32.dll6.1.7600.2134612,871,16817-Oct-201223:34
Shell32.dll6.1.7601.2213612,874,24017-Oct-201223:04

For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Shell32.dll6.1.7600.2134614,170,11218-Oct-201200:27x64
Shell32.dll6.1.7601.2213614,174,20817-Oct-201223:55x64

For all supported IA-64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Shell32.dll6.1.7600.2134621,182,97617-Oct-201223:23IA-64
Shell32.dll6.1.7601.2213621,190,65617-Oct-201223:05IA-64

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


More Information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Additional file information for Windows 7 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7
File nameX86_7d0f6a0de916179ebf7333bf2ab64a85_31bf3856ad364e35_6.1.7601.22136_none_d84a6838486af6a6.manifest
File versionNot applicable
File size695
Date (UTC)18-Oct-2012
Time (UTC)10:37
File nameX86_e29add52a6bfeaaa699a8cd382020fec_31bf3856ad364e35_6.1.7600.21346_none_197c888390228dd5.manifest
File versionNot applicable
File size695
Date (UTC)18-Oct-2012
Time (UTC)10:37
File nameX86_microsoft-windows-shell32_31bf3856ad364e35_6.1.7600.21346_none_6cb545188c4be907.manifest
File versionNot applicable
File size1,059,457
Date (UTC)18-Oct-2012
Time (UTC)04:51
File nameX86_microsoft-windows-shell32_31bf3856ad364e35_6.1.7601.22136_none_6ea6720a896a3902.manifest
File versionNot applicable
File size1,059,457
Date (UTC)18-Oct-2012
Time (UTC)06:32

Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameAmd64_08c29b331e15dcf67a98c61725c2734e_31bf3856ad364e35_6.1.7600.21346_none_7e72fe13ef0ddeb5.manifest
File versionNot applicable
File size699
Date (UTC)18-Oct-2012
Time (UTC)10:37
File nameAmd64_10583788859032ab20ecedc319bc339d_31bf3856ad364e35_6.1.7601.22136_none_af52e661fb6e3747.manifest
File versionNot applicable
File size1,040
Date (UTC)18-Oct-2012
Time (UTC)10:37
File nameAmd64_ed8cda80bed7b61e45c72f97482c017f_31bf3856ad364e35_6.1.7601.22136_none_31d930d09a4e6fd1.manifest
File versionNot applicable
File size699
Date (UTC)18-Oct-2012
Time (UTC)10:37
File nameAmd64_f9256ed059c7d58da904c60301efea68_31bf3856ad364e35_6.1.7600.21346_none_f5a4629cdad48eb9.manifest
File versionNot applicable
File size1,040
Date (UTC)18-Oct-2012
Time (UTC)10:37
File nameAmd64_microsoft-windows-shell32_31bf3856ad364e35_6.1.7600.21346_none_c8d3e09c44a95a3d.manifest
File versionNot applicable
File size1,058,443
Date (UTC)18-Oct-2012
Time (UTC)04:46
File nameAmd64_microsoft-windows-shell32_31bf3856ad364e35_6.1.7601.22136_none_cac50d8e41c7aa38.manifest
File versionNot applicable
File size1,058,443
Date (UTC)18-Oct-2012
Time (UTC)07:24
File nameWow64_microsoft-windows-shell32_31bf3856ad364e35_6.1.7600.21346_none_d3288aee790a1c38.manifest
File versionNot applicable
File size1,054,916
Date (UTC)18-Oct-2012
Time (UTC)04:47
File nameWow64_microsoft-windows-shell32_31bf3856ad364e35_6.1.7601.22136_none_d519b7e076286c33.manifest
File versionNot applicable
File size1,054,916
Date (UTC)18-Oct-2012
Time (UTC)04:39

Additional files for all supported IA-64-based versions of Windows Server 2008 R2
File nameIa64_892b065ac3eac3fdf7348dff66c8399a_31bf3856ad364e35_6.1.7601.22136_none_5fa4e3614eed9730.manifest
File versionNot applicable
File size1,038
Date (UTC)18-Oct-2012
Time (UTC)10:37
File nameIa64_ae8d2a50a5ccfb0045225cd8674ca493_31bf3856ad364e35_6.1.7600.21346_none_0e1595dde6605f87.manifest
File versionNot applicable
File size1,038
Date (UTC)18-Oct-2012
Time (UTC)10:37
File nameIa64_microsoft-windows-shell32_31bf3856ad364e35_6.1.7600.21346_none_6cb6e90e8c49f203.manifest
File versionNot applicable
File size1,058,441
Date (UTC)18-Oct-2012
Time (UTC)04:43
File nameIa64_microsoft-windows-shell32_31bf3856ad364e35_6.1.7601.22136_none_6ea81600896841fe.manifest
File versionNot applicable
File size1,058,441
Date (UTC)18-Oct-2012
Time (UTC)04:15
File nameWow64_microsoft-windows-shell32_31bf3856ad364e35_6.1.7600.21346_none_d3288aee790a1c38.manifest
File versionNot applicable
File size1,054,916
Date (UTC)18-Oct-2012
Time (UTC)04:47
File nameWow64_microsoft-windows-shell32_31bf3856ad364e35_6.1.7601.22136_none_d519b7e076286c33.manifest
File versionNot applicable
File size1,054,916
Date (UTC)18-Oct-2012
Time (UTC)04:39

↑ Back to the top


Keywords: kb, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbexpertiseadvanced, kbexpertisebeginner, kbsurveynew

↑ Back to the top

Article Info
Article ID : 2771101
Revision : 1
Created on : 1/7/2017
Published on : 12/12/2012
Exists online : False
Views : 192