S
Shawn R.
User Environment logging is most useful in two main
circumstances. The first is when you are experiencing
slow logon. The timestamp that you get when you have set
UserEnvDebugLevel=dword:0x10002 can be used to see what
processes are hanging up logons. The second is when you
see UserEnv errors in your application event log. This
appears to be something I have seen before. If you
scroll up in the log, who or what it logging on when this
is happening? I usually ignore a lot of what I see in
the UserEnv logs unless it pertains to a symptom or an
error I am seeing.
What is the symptom you are trying to troubleshoot?
There really isn't anything I can think of when it comes
to how to read UserEnv logs, but a lot of it is self-
explanatory when you read what is going on or if you were
to compare two logs of a domain and a non-domain user.
--Shawn
This posting is provided "AS IS" with no warranties, and
confers no rights.
circumstances. The first is when you are experiencing
slow logon. The timestamp that you get when you have set
UserEnvDebugLevel=dword:0x10002 can be used to see what
processes are hanging up logons. The second is when you
see UserEnv errors in your application event log. This
appears to be something I have seen before. If you
scroll up in the log, who or what it logging on when this
is happening? I usually ignore a lot of what I see in
the UserEnv logs unless it pertains to a symptom or an
error I am seeing.
What is the symptom you are trying to troubleshoot?
There really isn't anything I can think of when it comes
to how to read UserEnv logs, but a lot of it is self-
explanatory when you read what is going on or if you were
to compare two logs of a domain and a non-domain user.
--Shawn
This posting is provided "AS IS" with no warranties, and
confers no rights.