[THIN] Re: Logon Disabled
- From: "Walter, Chris" <christopher.walter@xxxxxxx>
- To: "'thin@xxxxxxxxxxxxx'" <thin@xxxxxxxxxxxxx>
- Date: Tue, 12 Apr 2005 18:13:35 -0400
You know what, my last email might have been a fountain of misinformation.
Just tried it on my farm and it does work like that. Here is something that
may help though.
Look to see if you have a policy "Allow Users to connect remotely using
Terminal Service" under Computer Configuration\Administrative
Templates\Windows Components\Terminal Services. This policy will override
the CHANGE LOGON command.
Sorry for the confusion.
Chris
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf
Of Joe Shonk
Sent: Tuesday, April 12, 2005 5:37 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Logon Disabled
I'm not sure I agree... For the most part, the Citrix LB works properly. If
you execute a chglogon /disable and run a qfarm /load you'll see that the
server isn't listed anymore. It has been removed from the Load Balance
list. Either something isn't updating correctly on the ZDC or the client is
caching something...
The chglogon /disabled is execute via a maintenance script, so removing the
published apps isn't an option. The script also makes use of the Citrix WMI
services, so stopping IMA is not an option.
Joe
_____
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf
Of Walter, Chris
Sent: Tuesday, April 12, 2005 2:12 PM
To: 'thin@xxxxxxxxxxxxx'
Subject: [THIN] Re: Logon Disabled
This is normal behavior. If you don't want people to connect to that server
you either have to remove the server from the published application or stop
the IMA service on the server. All 'disable logons' does is prevent people
from logging onto the server, it doesn't stop your clients from being
directed to that server to access a published application.
Chris
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf
Of Joe Shonk
Sent: Tuesday, April 12, 2005 12:51 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Logon Disabled
Hmm... Interesting issue... If we disable logons to a server (from the
console or cmd line) it seems that some of the thin-clients try and connect
to it and error out even tho there are other servers that serving up this
published desktop. Even 10 minutes later the same problems persist until:
The thin-client is rebooted or logins are re-enabled. Rebooting the
thin-client is not an option.
Any ideas?
Joe
Other related posts:
