[THIN] Re: Very Long Logoffs
- From: "Kelsey, John" <JCKelsey@xxxxxxxx>
- To: <thin@xxxxxxxxxxxxx>
- Date: Tue, 25 Oct 2005 17:26:48 -0400
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 <mailto:JCKelsey@xxxxxxxx>
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
<mailto:JCKelsey@xxxxxxxx>
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
<mailto:jckelsey@xxxxxxxx>
*******************************
Other related posts:
