Running logon/logoff script for a domain user is easy through group policy.
I've figured out how to use the runonce key (set via Group Policy) to run a
logon script for a local user but can't figure out how to run a script when a
local user logs off. The local user is defined on most workstations and
always has the same name. It doesn't matter to me if the same script runs
for all users as long as it runs for the local users as well.

Thanks!

After serious thinking sgrigg wrote :
> Running logon/logoff script for a domain user is easy through group policy.
> I've figured out how to use the runonce key (set via Group Policy) to run a
> logon script for a local user but can't figure out how to run a script when a
> local user logs off. The local user is defined on most workstations and
> always has the same name. It doesn't matter to me if the same script runs
> for all users as long as it runs for the local users as well.

Run gpedit.msc on a workstation as you do in AD for a domain user.

--
/klaus

I should have mentioned that I am in a domain environment and want this
logoff script to affect all workstations. I'm not about to visit every
workstation and edit the local policy

"Klaus Jorgensen" wrote:

> After serious thinking sgrigg wrote :
> > Running logon/logoff script for a domain user is easy through group policy.
> > I've figured out how to use the runonce key (set via Group Policy) to run a
> > logon script for a local user but can't figure out how to run a script when a
> > local user logs off. The local user is defined on most workstations and
> > always has the same name. It doesn't matter to me if the same script runs
> > for all users as long as it runs for the local users as well.
>
> Run gpedit.msc on a workstation as you do in AD for a domain user.
>
> --
> /klaus
>
>
>

sgrigg laid this down on his screen :
> I should have mentioned that I am in a domain environment and want this
> logoff script to affect all workstations. I'm not about to visit every
> workstation and edit the local policy

It's good exercise. :-)

Haven't seen any info other than using a utilily like RegShot and see
what gpedit.msc is doing to the registry. No definite answer, though.

--
/klaus