Typical errors include:
Missing or corrupted ntuser.pol file.
Missing or corrupted registry.pol file.
Unable to read policy information from the SYSVOL.
Failure in individual registry policies will cause all registry processing to fail.
To investigate:
Turn on Userenv log or verbose event logging.
Folder redirection processing contains five steps:
Determine which folders to redirect based on changes to policy at logon time.
Determine desired redirected location and verify access.
If folder does not exist: create folders, set access control lists (ACLs).
If folder exists, check ACLs and ownership.
If desired, move contents.
Best practice: Let system create folders and set ACLs for you.
Folder redirection failures only affect the folder redirection extension on a per-folder basis.
If you’re not following the best practice as noted above, typical errors include:
Redirecting to a folder that is incorrectly ACL’d.
User is not the owner of the folder.
Destination does not exist.
To investigate:
Turn on fdeploy logging to verify policy was processed.
Error info can also be found in the Event Log. See entries with the source name folder redirection.
To create a detailed log file for folder redirection use the following registry key:
HKLM\Software\Microsoft\Windows NT\CurrentVersion\Diagnostics
Set: FdeployDebugLevel = Reg_DWORD 0x0f
Note: The log file can be found at: %windir%\debug\usermode\fdeploy.log
| 