[THIN] Re: LogoffApp Registry Value
- From: "Jim Kenzig http://thin.ms" <jkenzig@xxxxxxxxx>
- To: thin@xxxxxxxxxxxxx
- Date: Tue, 6 Jan 2009 14:48:08 -0500
Yeah I know that was a joke. Seriously maybe it is an issue with users
having security access to the key. SP2 makes all kinds of security "fixes"
Jim Kenzig
Blog: http://www.techblink.com
On Tue, Jan 6, 2009 at 1:15 PM, Joe Shonk <joe.shonk@xxxxxxxxx> wrote:
> Logoff.exe is an executable, not a script. It would be hard to add a
> logoff script to it.
>
>
>
> Joe
>
>
>
> *From:* thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] *On
> Behalf Of *Jim Kenzig http://thin.ms
> *Sent:* Tuesday, January 06, 2009 10:13 AM
> *To:* thin@xxxxxxxxxxxxx
> *Subject:* [THIN] Re: LogoffApp Registry Value
>
>
>
> Isn't logoff a built in command line command? At least it works for me.
> Jim Kenzig
> Blog: http://www.techblink.com
>
> On Tue, Jan 6, 2009 at 9:30 AM, Carl Stalhood <cstalhood@xxxxxxxxx>
> wrote:
>
> Have you tried the local GPO? Run gpedit.msc and add a Logoff script there
> (User Config > Windows Settings > Scripts > Logoff).
>
>
>
> On Mon, Jan 5, 2009 at 11:35 PM, Jeremy Saunders <
> Jeremy.Saunders@xxxxxxxxxxxxxx> wrote:
>
> Hi All,
>
>
>
> A happy and healthy New Year to you all.
>
>
>
> Does anyone know if that old LogoffApp value under the Winlogon key still
> works under Windows 2003 SP2? I've been trying to trigger some logoff
> scripts using that value, but have not had much luck yet…didn't want to use
> a GPO at this stage, just been trying to stick with the KISS principles J
>
>
>
> Cheers.
>
>
>
> Kind regards,
>
> *Jeremy Saunders*
>
>
>
> Senior Solution Architect - Virtualisation Specialist | Datacom Systems
> WA | 29 Oxford Close, West Leederville, WA 6007 Australia
>
> Email: jeremy.saunders@xxxxxxxxxxxxxx | Ph: +61-8-9210-0806 | Mob:
> +61-413-441-846 | Fax: +61-8-9380-4226
>
> Personal Blog: http://www.jhouseconsulting.com/index.php
>
>
> ------------------------------
>
> *Confidentiality and Privilege Notice
> *This document is intended solely for the named addressee. The
> information contained in the pages is confidential and contains legally
> privileged information. If you are not the addressee indicated in this
> message (or responsible for delivery of the message to such person), you may
> not copy or deliver this message to anyone, and you should destroy this
> message and kindly notify the sender by reply email. Confidentiality and
> legal privilege are not waived or lost by reason of mistaken delivery to
> you.
> ------------------------------
>
>
>
>
>
Other related posts:
