How to enable folder redirection logging to gather verbose troubleshooting information in Windows 2000
This article has been archived. It is offered "as is" and will no longer be updated.
Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows registry
This article describes how to enable folder redirection logging to gather verbose troubleshooting information in Microsoft Windows 2000. This verbose troubleshooting information is useful when you are investigating folder redirection errors on a client computer.
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
Besides logging events in the Application log, folder redirection provides a detailed log that you can use to troubleshoot Group Policy issues. By default, folder redirection Client-Side Extensions (CSE) logging is set to only log errors. To avoid using unnecessary disk space, leave folder redirection logging at the default setting.
To enable folder redirection logging on the client computer, follow these steps:
- Log on to the computer on which you want to enable folder redirection logging.
Note You must log on as an administrator.
- Click Start, click Run, type regedit in the Open box, and then click OK.
- Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Diagnostics
- On the Edit menu, point to New, and then click DWORD.
- Type FdeployDebugLevel, and then press ENTER.
- Right-click FdeployDebugLevel, click Modify, type 0x0000000F in the Value data box, and then click OK.
Note FdeployDebugLevel can have the following values:
- Ordinary: 0x00000000
- Verbose: 0x0000000F
Article ID: 907355 - Last Review: 12/09/2015 03:15:18 - Revision: 1.3
Microsoft Windows 2000 Server, Microsoft Windows 2000 Advanced Server
- kbnosurvey kbarchive kbhowto KB907355