[Webinar] Streamline your web hosting managementRegister Today

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 299
  • Last Modified:

Windows 2003/XP logoff script timout - 10 minutes

Not sure if this should be asked in the OS topic area or here, so I am trying here.

I have a logoff script that I need to run to zip up some rather large files (VPC's) and store them on a network location.  The script works very well when run while logged in, but when we have it execute via a logoff script it gets terminated by the OS after 10 minutes of execution.  The process takes more time than this on large files or multiple files.  It does work if we are working with small files that can get done in less than 10 minutes.

There is a Group Policy/registry setting for removing or extending the default of 600 seconds for script completion:
  "Computer Configuration/Windows Settings/Administrative Templates/System/Scripts - Maximum wait time for Group Policy Scripts"
The problem is that this does not work for logoff scripts, just logon, startup and shutdown scripts.  This seems really strange to me.  I did go ahead and set this to '0' anyways.  It did make a little change in that it no longer makes an Event Log entry stating that the script was terminated, but it still terminates the script.

I talked to MS support and they say that there is not a setting to change this.  I have trouble buying this, so I am coming to you all for ideas.

Thanks in advance for any ideas.  I am offering high point values because MS says that it can not be done.  :)
  • 2
1 Solution
TUmphressAuthor Commented:
I forgot to mention that the desktop machines are running Windows XP SP2 and are members of a Windows 2003 Domain.
TUmphressAuthor Commented:
Well, we came up with a work around.

Remove the logoff and shutdown capability from the Start menu, create our own LogOff button that calls a script to complete the needed stuff and when that is completed programatticly log the user off of the machine.
Because you have presented a solution to your own problem which may be helpful to future searches, this question is now PAQed and your points have been refunded.


Featured Post

[Webinar] Kill tickets & tabs using PowerShell

Are you tired of cycling through the same browser tabs everyday to close the same repetitive tickets? In this webinar JumpCloud will show how you can leverage RESTful APIs to build your own PowerShell modules to kill tickets & tabs using the PowerShell command Invoke-RestMethod.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now