Joe, Does putting that command before shut down override the IMA value which re-disables logon? Steve Greenberg Thin Client Computing 34522 N. Scottsdale Rd. suite D8453 Scottsdale, AZ 85262 (602) 432-8649 (602) 296-0411 fax steveg@xxxxxxxxxxxxxx _____ From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Joe Shonk Sent: Wednesday, March 02, 2005 9:07 AM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: MetaFrame 3 Bug (feature) I thought about that but the customer is using softgrid and there is a significant delay between when the shutdown/restart command is sent and when softgrid actually restarts the server (The softgrid client intercepts logoff/shutdown/restart commands). Some of the softgrid client values can be tweaked, but only little. Joe _____ From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Landin, Mark Sent: Tuesday, March 01, 2005 12:01 PM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: MetaFrame 3 Bug (feature) Not that I know of. I just put a "change logon /enable" at the end of my reboot script, immediately before the tsshutdn command. That's all I could think of. _____ From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Joe Shonk Sent: Tuesday, March 01, 2005 12:54 PM To: thin@xxxxxxxxxxxxx Subject: [THIN] MetaFrame 3 Bug (feature) Does anyone know how to disable the stupid 'Disable logons' that survives a reboot feature that Citrix implemented? Adding a chglogon /enable to the startup script doesn't always work as IMA service may start after the startup script has executed.