![]() ![]() RunDiagnosticLoggingGroupPolicy:REG_DWORD:1 enables Group Policy event logging.RunDiagnosticLoggingGlobal:REG_DWORD:1 instructs Win2K to log all user environment activity.You can add the following value entries to the Diagnostics key to achieve the different results: When prompted, leave the class key empty. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT \CurrentVersion\ and add a new key called Diagnostics (this key doesn't appear in the registry by default). This feature is a real gift when you consider the task of troubleshooting local or domain Group Policy problems with computers or users, not to mention application management and IPsec policy. To use them, all you have to do is add a key and one or more value entries to the registry. ![]() Win2K includes several built-in environment debugging tools. (Although you can debug user environment problems in NT 4.0 if you install the debug version of userenv.dll, the solution is inconvenient because you have to reconfigure, shut down, and reboot the machine to activate the debugging features in the checked build of the DLL.) ![]() As I approached the point of total frustration, I discovered a cool technique for debugging NT 4.0 system policy and Win2K Group Policy environment problems. Of course, when things don’t work as you expect them to, it’s difficult to debug layer upon layer of adjustments you made using computer policy, user policy, and logon scripts. I’ve been madly testing user profiles and system policies with a mix of Windows 2000 and Windows NT 4.0 clients in an NT 4.0 domain. Win2K Group Policy and User Environment Debugging ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |