Slow Logoff

[slawrie]

I have a terminal server that is using local profiles and I have installed
UPH Clean. Users are having extremely long logoff times. Everything else on
the server runs extremely well. Any suggestions.

 

[Rich Raffenetti]

This may be your problem.

I learned from an earlier post that Terminal Servers do not complete their
login until after one minute. If you logoff right after logging on, it will
take a minute to logoff. If you wait one minute before logging off, the
logoff will be immediate. Most people will never experience the slow logoff
if this is the reason.

I never learned why. :-(

"slawrie" <slawrie@discussions.microsoft.com> wrote in message
news:8FDBDD86-8C36-4435-BCC7-5C56B4C96121@microsoft.com...
>I have a terminal server that is using local profiles and I have installed
> UPH Clean. Users are having extremely long logoff times. Everything else
> on
> the server runs extremely well. Any suggestions.

 

[Vera Noest [MVP]]

Rich, here's why:
901196 - A remote session does not end immediately on a computer
that is running Windows Server 2003 Service Pack 1
http://support.microsoft.com/?kbid=901196

But that is hardly Slawrie's problem.
Slawrie, can you post which OS and SP your server is running? These
kind of issues are often very different in W2K and 2003.
Have you checked the EventLog on the server for any warnings or
errors?
Have you checked in Terminal Services Manager what is happening in
the user sessions when they logoff? Which processes are running?
What exactly do the users experience? Do they see the "Windows is
saving your profile..." for an extremely long time, or another
dialog box, or....?
And how long is extremely? Seconds? Minutes? How many?
Are users connecting with the full rdp client, or with the
webclient?

I would enable verbose logging of the user environment to see what
is happening.
221833 - How to enable user environment debug logging in retail
builds of Windows
http://support.microsoft.com/?kbid=221833

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"Rich Raffenetti" <rich@raffenetti_takethisout.com> wrote on 01
aug 2007 in microsoft.public.windows.terminal_services:

> This may be your problem.
>
> I learned from an earlier post that Terminal Servers do not
> complete their login until after one minute. If you logoff
> right after logging on, it will take a minute to logoff. If you
> wait one minute before logging off, the logoff will be
> immediate. Most people will never experience the slow logoff
> if this is the reason.
>
> I never learned why. :-(
>
> "slawrie" <slawrie@discussions.microsoft.com> wrote in message
> news:8FDBDD86-8C36-4435-BCC7-5C56B4C96121@microsoft.com...
>>I have a terminal server that is using local profiles and I have
>>installed
>> UPH Clean. Users are having extremely long logoff times.
>> Everything else on
>> the server runs extremely well. Any suggestions.

 

[slawrie]

This is a windows 2003 enterprise server with dual quad processors and 16GB
memory. It is on SP2 and is current with security and critical updates. The
dialog box is "saving your profile" Extremely equals coffee break (minutes)
Users were getting tired of waiting and disconnecting.
I actually solved the problem by removing the UPH Cleaner but I will
investigate later to determine what caused the problem.

Thanks,

Steve


"Vera Noest [MVP]" wrote:

> Rich, here's why:
> 901196 - A remote session does not end immediately on a computer
> that is running Windows Server 2003 Service Pack 1
> http://support.microsoft.com/?kbid=901196
>
> But that is hardly Slawrie's problem.
> Slawrie, can you post which OS and SP your server is running? These
> kind of issues are often very different in W2K and 2003.
> Have you checked the EventLog on the server for any warnings or
> errors?
> Have you checked in Terminal Services Manager what is happening in
> the user sessions when they logoff? Which processes are running?
> What exactly do the users experience? Do they see the "Windows is
> saving your profile..." for an extremely long time, or another
> dialog box, or....?
> And how long is extremely? Seconds? Minutes? How many?
> Are users connecting with the full rdp client, or with the
> webclient?
>
> I would enable verbose logging of the user environment to see what
> is happening.
> 221833 - How to enable user environment debug logging in retail
> builds of Windows
> http://support.microsoft.com/?kbid=221833
>
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> "Rich Raffenetti" <rich@raffenetti_takethisout.com> wrote on 01
> aug 2007 in microsoft.public.windows.terminal_services:
>
> > This may be your problem.
> >
> > I learned from an earlier post that Terminal Servers do not
> > complete their login until after one minute. If you logoff
> > right after logging on, it will take a minute to logoff. If you
> > wait one minute before logging off, the logoff will be
> > immediate. Most people will never experience the slow logoff
> > if this is the reason.
> >
> > I never learned why. :-(
> >
> > "slawrie" <slawrie@discussions.microsoft.com> wrote in message
> > news:8FDBDD86-8C36-4435-BCC7-5C56B4C96121@microsoft.com...
> >>I have a terminal server that is using local profiles and I have
> >>installed
> >> UPH Clean. Users are having extremely long logoff times.
> >> Everything else on
> >> the server runs extremely well. Any suggestions.
>

 

[Vera Noest [MVP]]

Check if you run the latest version of UPHClean.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?c2xhd3JpZQ==?= <slawrie@discussions.microsoft.com> wrote
on 02 aug 2007 in microsoft.public.windows.terminal_services:

> This is a windows 2003 enterprise server with dual quad
> processors and 16GB memory. It is on SP2 and is current with
> security and critical updates. The dialog box is "saving your
> profile" Extremely equals coffee break (minutes) Users were
> getting tired of waiting and disconnecting. I actually solved
> the problem by removing the UPH Cleaner but I will investigate
> later to determine what caused the problem.
>
> Thanks,
>
> Steve
>
>
> "Vera Noest [MVP]" wrote:
>
>> Rich, here's why:
>> 901196 - A remote session does not end immediately on a
>> computer that is running Windows Server 2003 Service Pack 1
>> http://support.microsoft.com/?kbid=901196
>>
>> But that is hardly Slawrie's problem.
>> Slawrie, can you post which OS and SP your server is running?
>> These kind of issues are often very different in W2K and 2003.
>> Have you checked the EventLog on the server for any warnings or
>> errors?
>> Have you checked in Terminal Services Manager what is happening
>> in the user sessions when they logoff? Which processes are
>> running? What exactly do the users experience? Do they see the
>> "Windows is saving your profile..." for an extremely long time,
>> or another dialog box, or....?
>> And how long is extremely? Seconds? Minutes? How many?
>> Are users connecting with the full rdp client, or with the
>> webclient?
>>
>> I would enable verbose logging of the user environment to see
>> what is happening.
>> 221833 - How to enable user environment debug logging in retail
>> builds of Windows
>> http://support.microsoft.com/?kbid=221833
>>
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> "Rich Raffenetti" <rich@raffenetti_takethisout.com> wrote on 01
>> aug 2007 in microsoft.public.windows.terminal_services:
>>
>> > This may be your problem.
>> >
>> > I learned from an earlier post that Terminal Servers do not
>> > complete their login until after one minute. If you logoff
>> > right after logging on, it will take a minute to logoff. If
>> > you wait one minute before logging off, the logoff will be
>> > immediate. Most people will never experience the slow logoff
>> > if this is the reason.
>> >
>> > I never learned why. :-(
>> >
>> > "slawrie" <slawrie@discussions.microsoft.com> wrote in
>> > message
>> > news:8FDBDD86-8C36-4435-BCC7-5C56B4C96121@microsoft.com...
>> >>I have a terminal server that is using local profiles and I
>> >>have installed
>> >> UPH Clean. Users are having extremely long logoff times.
>> >> Everything else on
>> >> the server runs extremely well. Any suggestions.

 

[slawrie]

I think I was on the latest version but I'll double check.

Thanks for the feedback.

Steve

"Vera Noest [MVP]" wrote:

> Check if you run the latest version of UPHClean.
>
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> =?Utf-8?B?c2xhd3JpZQ==?= <slawrie@discussions.microsoft.com> wrote
> on 02 aug 2007 in microsoft.public.windows.terminal_services:
>
> > This is a windows 2003 enterprise server with dual quad
> > processors and 16GB memory. It is on SP2 and is current with
> > security and critical updates. The dialog box is "saving your
> > profile" Extremely equals coffee break (minutes) Users were
> > getting tired of waiting and disconnecting. I actually solved
> > the problem by removing the UPH Cleaner but I will investigate
> > later to determine what caused the problem.
> >
> > Thanks,
> >
> > Steve
> >
> >
> > "Vera Noest [MVP]" wrote:
> >
> >> Rich, here's why:
> >> 901196 - A remote session does not end immediately on a
> >> computer that is running Windows Server 2003 Service Pack 1
> >> http://support.microsoft.com/?kbid=901196
> >>
> >> But that is hardly Slawrie's problem.
> >> Slawrie, can you post which OS and SP your server is running?
> >> These kind of issues are often very different in W2K and 2003.
> >> Have you checked the EventLog on the server for any warnings or
> >> errors?
> >> Have you checked in Terminal Services Manager what is happening
> >> in the user sessions when they logoff? Which processes are
> >> running? What exactly do the users experience? Do they see the
> >> "Windows is saving your profile..." for an extremely long time,
> >> or another dialog box, or....?
> >> And how long is extremely? Seconds? Minutes? How many?
> >> Are users connecting with the full rdp client, or with the
> >> webclient?
> >>
> >> I would enable verbose logging of the user environment to see
> >> what is happening.
> >> 221833 - How to enable user environment debug logging in retail
> >> builds of Windows
> >> http://support.microsoft.com/?kbid=221833
> >>
> >> _________________________________________________________
> >> Vera Noest
> >> MCSE, CCEA, Microsoft MVP - Terminal Server
> >> TS troubleshooting: http://ts.veranoest.net
> >> ___ please respond in newsgroup, NOT by private email ___
> >>
> >> "Rich Raffenetti" <rich@raffenetti_takethisout.com> wrote on 01
> >> aug 2007 in microsoft.public.windows.terminal_services:
> >>
> >> > This may be your problem.
> >> >
> >> > I learned from an earlier post that Terminal Servers do not
> >> > complete their login until after one minute. If you logoff
> >> > right after logging on, it will take a minute to logoff. If
> >> > you wait one minute before logging off, the logoff will be
> >> > immediate. Most people will never experience the slow logoff
> >> > if this is the reason.
> >> >
> >> > I never learned why. :-(
> >> >
> >> > "slawrie" <slawrie@discussions.microsoft.com> wrote in
> >> > message
> >> > news:8FDBDD86-8C36-4435-BCC7-5C56B4C96121@microsoft.com...
> >> >>I have a terminal server that is using local profiles and I
> >> >>have installed
> >> >> UPH Clean. Users are having extremely long logoff times.
> >> >> Everything else on
> >> >> the server runs extremely well. Any suggestions.
>