[THIN] Re: Very Long Logoffs
- From: Jeremy Saunders <jeremy.saunders@xxxxxxxxxxx>
- To: thin@xxxxxxxxxxxxx
- Date: Thu, 27 Oct 2005 01:57:40 +0800
Does the same thing happen for RDP connections?
Why don't you also enable some debugging for the logon/logoff process so
that you can see what it's hanging on?
Also...what MS hotfixes have you got installed?
----------------------Beginning of reg
file------------------------------------------------------------
Windows Registry Editor Version 5.00
;This information is relevant to Windows 2000, Windows 2003 and Windows XP.
;Verbose logon and logoff messages: Start by enabling the verbose message
option for startup,
;shutdown, logon, and logoff activities. To enable this feature, start a
registry editor and
;navigate to the
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
;subkey. Add a new value entry called VerboseStatus, of type REG_DWORD,
with a value of 1.
;Log off, then log back on and search for clues in the additional messages
in the System and
;Application event logs. The additional messages might help you identify
the source of the
;problem. Remember to disable verbose mode before you return the system to
production (simply
;delete the VerboseStatus value entry).
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\system]
"VerboseStatus"=dword:00000001
;Debug the user environment settings, you can create a log file which is
placed in the following
;folder: %systemroot%\debug\usermode\userenv.log.
;I can contain different levels of information concerning your log on, log
off, and other user
;environment activity. This log file can help you debug problems related to
policy application
;and profile application and saving.
;To set the logging level associated with the userenv.log file, import this
reg file.
;Registry Entry Value
;============== ==========
;No logging 0x00000000
;Normal logging 0x00000001
;Verbose logging 0x00000002
;Output to logfile 0x00010000
;Debugger output 0x00020000
;Restart the computer for the changes to take effect.
;You can combine the values from the table above. e.g. for verbose output
to logfile, use
;value 00010002).
;User environment debugging: User environment logging usually produces more
valuable information,
;especially if the delay is related to GPO application. Using a registry
editor, locate the
;HKEY_LOCAL_MACHINE\SOFTWARE \Microsoft\Windows NT\CurrentVersion\Winlogon
subkey. Add a new
;value entry called UserEnvDebugLevel of type REG_DWORD, and give the entry
a hex value of 10002
;(0x00010002). This setting instructs the OS to write verbose messages for
startup, shutdown,
;logon, and logoff activities to the log file
%systemroot%\debug\usermode\userenv.log file.
;If you want to fine-tune the debugging messages, you can set the value of
UserEnvDebugLevel
;to any combination of these values:
;When you set the value to 10002, you instruct the OS to write verbose
messages to the log.
;The default value of this value entry is NORMAL|LOGFILE (0x00010001). Log
off and back on
;and check the log file; donât let the amount of data you see overwhelm
youâitâs easy to sift
;through the messages and locate the source of the problem. When youâre
finished, you can
;either reset this value to zero or delete the UserEnvDebugLevel item.
;The log file is written to the %Systemroot%\Debug\UserMode\Userenv.log
file. If the Userenv.log
;exists and is greater than 300 KB, the existing file will be renamed to
Userenv.bak, and a
;new log file created.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]
"UserEnvDebugLevel"=dword:00010002
----------------------End of reg
file------------------------------------------------------------
Kind regards,
Jeremy Saunders
Senior Technical Specialist
ceruleanTM
an IBM Australia Company
formerly known as Logicalis
Level 2, 1060 Hay Street
West Perth WA 6005
AUSTRALIA
Visit us at
http://www.cerulean.com.au/
P:Â +61 8 9261 8412 F:Â +61 8 9261 8536
M:Â TBA E-mail:
Jeremy.saunders@xxxxxxxxxxx
"Schneider, Chad
M"
<CMSchneider@Bemi To
s.com> thin@xxxxxxxxxxxxx
Sent by: cc
thin-bounce@freel
ists.org Subject
[THIN] Re: Very Long Logoffs
26/10/2005 08:28
PM
Please respond to
thin
When this affected our Citrix serversâ.we were forced to do a complete
removal.
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of Kelsey, John
Sent: Tuesday, October 25, 2005 4:27 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Very Long Logoffs
If I just disable the SMS client service, would that be enough?
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of M
Sent: Tuesday, October 25, 2005 17:06
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Very Long Logoffs
Earlier this year there was a thread about a version of the SMS
client causing profile unloading problems.
http://support.microsoft.com/default.aspx?scid=kb;en-us;831962
----- Original Message -----
From: Kelsey, John
To: thin@xxxxxxxxxxxxx
Sent: Tuesday, October 25, 2005 9:43 PM
Subject: [THIN] Re: Very Long Logoffs
I dont see anything being reported in the event logs from UPHClean.
No AV on any of these servers
Yes, they do have the SMS client installed on them.
Not sure why they are enterprise, just how I inherited them.
Thanks!
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx
[mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of M
Sent: Tuesday, October 25, 2005 16:35
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Very Long Logoffs
What information is UPHClean reporting to you in the event
logs ?
What AV are you running ? Symantec 10 ?
Running SMS client ?
As a matter of interest ... why 2003 Enterprise ?
Regards
----- Original Message -----
From: Kelsey, John
To: thin@xxxxxxxxxxxxx
Sent: Tuesday, October 25, 2005 3:24 PM
Subject: [THIN] Very Long Logoffs
Just recently we've had users complaining of extremely long
logoff times....anywhere from 5 to 15 minutes the screen will
just sit at "Logging off..."
Multiple servers, multiple clients.
All servers are Windows 2003 Enterprise (no service pack 1)
with Metaframe XP SP4/FR3.
All servers are also running the UPHClean service, but its not
helping. =(
Any ideas?
*******************************
John C. Kelsey
DuBois Regional Medical Center
(: 814.375.3073
2 : 814.375.4005
*: jckelsey@xxxxxxxx
*******************************
Other related posts:
