Re: remote desktop sessions not terminating?

So you don't want to uninstall/reinstall bu tyour worried about finding
other things wrong.....wouldn't you rather have peace of mind rather than
worrying that this server is really screwed up? If the server is as new as
you say, your actually wasting more time troubleshooting than if you would
just rebuild/reinstall (whatever). Obvoiusly this server is not in
production or ready yet.

Jeff Pitsch
http://www.sbcgatekeeper.com
Your Terminal Services Security Website

"rdyaz" <rdyaz@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:2B30DD48-F68C-48D1-B178-81DC3FC09041@xxxxxxxxxxxxxxxx
> MS support told me the delay in userinit terminating is caused by 2003
> SP1,
> which added a setting to autoenroll certificates. My trouble is that the
> policy setting they told us to change in order to stop the autoenroll is
> missing.
>
> He said change User Config/Windows Settings/Security Settings/Public Key
> Policies/ then Roaming Settings (or something similar)--but there is
> nothing
> below Public Key Policies except Enterprise Trust (which is empty). He
> said
> the policy is missing b/c something went wrong with the SP1 install and we
> should uninstall/reinstall--(which we don't want to do) and then change
> the
> (then visilbe) setting to Do Not Enroll Certificates.
>
> At this point the 60 second wait is no big deal since most users will be
> logged in that long--but what I'm worried about is that this missing
> policy
> setting is a sign of a botched SP1 install and we will find other TS
> settings
> missing in the furture. This is a server we just brought on line
> yesterday
> and we would rather start over from scratch that reinstall SP1.
>
> Is there a way to see this policy setting without doing the reinstall?
>
> Thanks,
> -Rich
>
> "Vera Noest [MVP]" wrote:
>
>> "Edward Scott" <shakermaker@xxxxxxxxxxxxx> wrote on 25 okt 2005 in
>> microsoft.public.windows.terminal_services:
>>
>> >
>> >> interestingly enough, while I had the task manager open I
>> >> noticed that after a few minutes userinit.exe terminates. when
>> >> I subsequently close the task manager the Remote Desktop
>> >> session logs off as it is supposed to. it appears that the
>> >> termination of userinit.exe is delayed, or just very slow, for
>> >> some reason.
>> >>
>> >> I'm not sure what userinit.exe is, so I am still not sure why
>> >> this is happening. it is not a disaster, however.
>> >
>> > just in case anyone happens to be following this: userinit.exe
>> > always terminates a few minutes into the Remote Desktop session,
>> > independently of whether other applications are still running or
>> > not. the problem described in my first post only occurs if I
>> > close all programs before userinit.exe has had a chance to
>> > finish, and in that case it is just a matter of waiting it out.
>> >
>> > I don't think there would be a workaround for this. most users
>> > will be using the Remote Desktop Connection for long enough that
>> > userinit.exe will have a chance to terminate, so I no longer
>> > consider this a problem.
>>
>> Exactly, it takes at least one minute for userinit to go away.
>> Documented by Citrix (who are careful to point out that this is by
>> *Microsoft* design:
>>
>> CTX106049 - Published Application Sessions Take 60 Seconds to Log
>> Off when Windows 2003, Service Pack 1 is Installed
>> http://knowledgebase.citrix.com/kb/entry.jspa?externalID=CTX106049
>>
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>


.

Relevant Pages

  • Re: remote desktop sessions not terminating?
    ... uninstall SP1. ... Just thought we might be missing something that caused this ... If the server is as new as ... >> policy setting they told us to change in order to stop the autoenroll is ...
    (microsoft.public.windows.terminal_services)
  • Re: remote desktop sessions not terminating?
    ... but on more than one server...so thought reinstall might not fix it. ... I found the described Policy setting, but not under the local policy rather ... Just thought we might be missing something that caused this ... If the server is as new as ...
    (microsoft.public.windows.terminal_services)
  • DBD::PgSPI crashes the database server (SIGSEGV)?
    ... I have tried to use "plperlu" to write server functions to encapsulate ... child process (PID 4339) was terminated by signal 11 ... terminating any other active server processes ...
    (comp.lang.perl.modules)
  • Re: webservice performance data missing
    ... If this is a Win2003 server, how come you don't have the reg.exe utility? ... >>> Networking for Costly counters failed ... >>> is terminating ... >>> compliant or invalid Linkage Key ...
    (microsoft.public.win32.programmer.wmi)
  • Re: Identifying the Closed Client..,
    ... Depending upon the situation, it may close the connection with a FIN packet(which will be received by the server as a call to recv() that succesfully receives zero bytes) or a RST packet, which will cause recv to fail with WSAECONNRESET. ... I contend that it ought to close with a RST in the event of an application terminating through an unhandled exception. ... I would assume that this would also happen if the client operating system crashed while the connection was open, but, I've never tested this. ...
    (microsoft.public.win32.programmer.networks)
Quantcast