Seems like a band-aid to me. So what wrong with asking for a simple feature to behave the way it's supposed to? Now I need startup script and/or beg the AD guy to make changes? Joe _____ From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Jim Hathaway Sent: Thursday, January 27, 2005 2:08 PM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Change Logon /disable A GP or local policy defined Startup script with "change logon /enable" doesn't do it for ya? _____ From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Joe Shonk Sent: Thursday, January 27, 2005 1:00 PM To: thin@xxxxxxxxxxxxx Subject: [THIN] Change Logon /disable Our buddies over at Citrix added a neat little feature that allows the "change logon /disable" feature to survive a reboot. While this is great for some it, it is not ideal for all environments and our buddies did not provide an option to configure it. Does any one know how to reset this option so that logons are reenabled after a reboot? Thanks, Joe Notice: This transmission contains confidential information intended only for the use of the individual or entity to whom it is addressed. Any disclosure, copying, distribution, or action in reliance on the contents of this transmission is strictly prohibited by anyone except the party to whom it is addressed.