Re: Running logoff script for local user

Tech-Archive recommends: Fix windows errors by optimizing your registry

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


.

Relevant Pages

  • Re: VB Script - Check user for default password on remote workgroup machine
    ... I need a VB script code to verify whether a specific Local user ID on ... Below code tries to reset the password on target machine by providing ... If some script allowed you to get around this policy then this would allow a hacker to keep on trying with an automatied script until successful. ...
    (microsoft.public.scripting.vbscript)
  • Re: WScript.Network UserProfile Property
    ... script on a local user on a machine in a workgroup... ... I use Script Internals SystemScripter 6.0. ... type feature that shows UserProfile as an available ...
    (microsoft.public.scripting.vbscript)
  • Running logoff script for local user
    ... Running logon/logoff script for a domain user is easy through group policy. ... I've figured out how to use the runonce key to run a ... local user logs off. ...
    (microsoft.public.windowsxp.configuration_manage)
  • Re: Running logoff script for local user
    ... I should have mentioned that I am in a domain environment and want this ... logoff script to affect all workstations. ... local user logs off. ...
    (microsoft.public.windowsxp.configuration_manage)
  • Re: logon scripts and workgroups ...
    ... but you'll have to set a logon script for each local user account - ... you can't do it with group policy or via AD. ...
    (microsoft.public.windows.server.general)