Sorry for the delay, I do "not" have a script on start up. I was
speaking to the Citrix engineer again and he mentioned putting in a change
request for inclusion in the next release. Hell for all I car, add another
box in that section that says "Logons Disabled on Reboot" or something.
He mentioned something about publishing/depublishing apps from a server
feature so that the server is accessible, but users won't hit the box if
there are no apps. (As long as that feature does not take 30 minutes to
accomplish like that script does. That script is great as an after market
solution, but as a Citrix coded answer, it would have to be within 10-20
seconds)
------------------------------
*From:* thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] *On
Behalf Of *Joe Shonk
*Sent:* Thursday, May 18, 2006 1:53 PM
*To:* thin@xxxxxxxxxxxxx
*Subject:* [THIN] Re: Disabled Logins & Rebooting
Have you check the system shutdown script to see if a chglogon /enable is
being set right before restart?
Joe
------------------------------
*From:* thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] *On
Behalf Of *Eilers, Lee (CDC/OCOO/ITSO) (CTR)
*Sent:* Thursday, May 18, 2006 10:33 AM
*To:* thin@xxxxxxxxxxxxx
*Subject:* [THIN] Re: Disabled Logins & Rebooting
That was suggested earlier and I did create that evaluator.
I also had pressed on our engineer at Citrix and he mentioned that it is a
"feature" of MPS 3.0. In the CMC, for MPS3 with SP4 and PS4, under
Metaframe Settings, Control Options, it says* The "logon" setting remains
in effect after restarting server. * Their interpretation is that this
means it will be enabled on reboot. I read this to mean that what ever
setting I do, it will* "remain in effect"* after a restart.
[image: Picture (Metafile)]
________________________________
From: thin-bounce@xxxxxxxxxxxxx
[mailto:thin-bounce@xxxxxxxxxxxxx<thin-bounce@xxxxxxxxxxxxx>]
On Behalf Of Maddox, Cole
Sent: Thursday, May 18, 2006 1:01 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Disabled Logins & Rebooting
Lee,
Rather than disabling your logins, have you considered using a load
evaluator? You could create one using the scheduling rule, remove the
"times of day" when the server is available, and then assign it to the
server you wish to reboot. This will prevent users from getting access but
you could still connect via the console, which you can't do if you disable
logons. Also, this will stay set regardless of whether or not you reboot
and regardless of whether you are running version 3 or 4. (Thanks to
BriForum 2006 for this tip).
Cole.
________________________________
From: thin-bounce@xxxxxxxxxxxxx
[mailto:thin-bounce@xxxxxxxxxxxxx<thin-bounce@xxxxxxxxxxxxx>]
On Behalf Of Eilers, Lee (CDC/OCOO/ITSO) (CTR)
Sent: Thursday, May 18, 2006 11:08 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Disabled Logins & Rebooting
Windows 2000 SP4 and MPS3.0 with SP4 (we are migrating to 2003 and MPS4
later this year.)
________________________________
From: thin-bounce@xxxxxxxxxxxxx
[mailto:thin-bounce@xxxxxxxxxxxxx<thin-bounce@xxxxxxxxxxxxx>]
On Behalf Of Landin, Mark
Sent: Thursday, May 18, 2006 10:11 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Disabled Logins & Rebooting
Specify what OS and Citrix release you are using. They behave differently
in this area.
________________________________
From: thin-bounce@xxxxxxxxxxxxx [
mailto:thin-bounce@xxxxxxxxxxxxx <thin-bounce@xxxxxxxxxxxxx>] On Behalf Of
Eilers, Lee (CDC/OCOO/ITSO) (CTR)
Sent: Thursday, May 18, 2006 8:24 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Disabled Logins & Rebooting
Here's the situation:
I disable logins to one of my servers. I did this via the CMC and
via the command-line, "change logon /disable", just to be sure.
No users on the box.
Start, Shutdown, Restart box
In the CMC, Load Evaluators, I am seeing the users being directed
to various other boxes. All of a sudden, 14 users are sent to the box that
was offline and in the process of rebooting. The box evidently is marked by
Citrix to enabled mode prior to the reboot.
This has been a REAL pet PIEVE of mine about when rebooting
servers, that they come backup enabled and ready to accept connections, but
I had not realized the impact it was having as they went down for a reboot.
Why is it that a server would be enabled just as it is being
rebooted? and to make matters worse, users are being directed to that box
while it is going down, where the logic?!?!? <RANT>
So, am I missing something, or has everyone been suffering along
on this issue?
