Try it anyway, who knows.
--
----------------------------------------------------------
http://www.g2mil.com/Dec2003.htm
-----Original Message-----
PSS ID Number: 221833
Article Last Modified on 1/24/2003
---------------------------------------------------------- ----------------------
The information in this article applies to:
a.. Microsoft Windows XP Professional
b.. Microsoft Windows 2000 Datacenter Server
c.. Microsoft Windows 2000 Advanced Server
d.. Microsoft Windows 2000 Server
e.. Microsoft Windows 2000 Professional
---------------------------------------------------------- ----------------------
This article was previously published under Q221833
IMPORTANT: This article contains information about
modifying the registry. Before you modify the registry,
make sure to back it up and make sure that you understand
how to restore the registry if a problem occurs. For
information about how to back up, restore, and edit the
registry, click the following article number to view the
article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
SUMMARY
The versions of Microsoft Windows listed at the beginning
of this article include debug logging of the user profile
and the Windows system policy processes. To turn on debug
logging, modify the registry on the computer on which the
logging occurs. The debug logging functionality is also
available with Microsoft Windows NT 4.0, but the
functionality requires a checked (debug) build of the
Userenv.dll file on Windows NT 4.0.
For additional information, click the article number
below to view the article in the Microsoft Knowledge Base:
154120 Debugging User Profiles and System Policies in Windows NT 4.0
You can use the output of this logging to troubleshoot
problems with user profiles and Group Policy processing.
MORE INFORMATION
WARNING: If you use Registry Editor incorrectly, you may
cause serious problems that may require you to reinstall
your operating system. Microsoft cannot guarantee that you
can solve problems that result from using Registry Editor
incorrectly. Use Registry Editor at your own risk.
Use Registry Editor to add the following registry value
(or modify it, if the value already exists):
Key: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon
Value: UserEnvDebugLevel
Value Type: REG_DWORD
Value Data: 10002 (Hex)
UserEnvDebugLevel can have the following values:
NONE 0x00000000
NORMAL 0x00000001
VERBOSE 0x00000002
LOGFILE 0x00010000
DEBUGGER 0x00020000
The default value is NORMAL (0x00010000). NOTE: To
disable logging, select NONE (where the value would be
[0X0000000000000]).
You can also combine the values. For example, you can
combine VERBOSE 0x00000002 and LOGFILE 0x00010000 to get
0x00010002. So if UserEnvDebugLevel is set with a value of
0x00010002, this turns on both LOGFILE and VERBOSE.
Combining these values is the same as using an AND
statement:
0x00010000 AND 0x00000002 = 0x00010002
The log file is written to the %SystemRoot%
\Debug\UserMode\Userenv.log file.
Additional query words: userenv.log enable
Keywords: kbhowto KB221833
Technology: kbwin2000AdvServ kbwin2000AdvServSearch
kbwin2000DataServ kbwin2000DataServSearch kbwin2000Pro
kbwin2000ProSearch kbwin2000Search kbwin2000Serv
kbwin2000ServSearch kbWinAdvServSearch kbWinDataServSearch
kbWinXPPro kbWinXPProSearch kbWinXPSearch
---------------------------------------------------------- ----------------------
Send feedback to Microsoft
© 2003 Microsoft Corporation. All rights reserved.
message news:
[email protected]...
