Navigation
Most popular FAQs 
- HP Install Network Printer Wizard 4.0 - Configuring a ... (18145 views)
- How to configure Apache versions 1.3.x - 2.0.x ? ... (16501 views)
- Why in my workgroup user names in statistics and ... (16205 views)
- The application failed to initialize properly (0xc0000142). Click on ... (14237 views)
- Moving XP User Profile (12399 views)
- How to set proxy for my Windows XP computer ... (11559 views)
- HP Jetdirect Print Servers - Installing and Configuring a ... (10660 views)
- Windows Vista: SuperFetch and External Memory Devices (8804 views)
- Shutdown is very slow - Windows XP (8088 views)
- Troubleshooting Windows XP Shutdown Issues (7272 views)
Latest FAQs 
- What is HSLAB HTTP Monitor? (2010-03-09 07:39)
- Why in my workgroup user names in statistics and ... (2010-03-09 07:36)
- For maintenance of the exact accounting you should to ... (2010-03-09 07:32)
- Only Guest account when mapping to network drive (2010-03-09 07:30)
- How I Can Completely Remove Windows Vista/7 Printer Drivers ... (2010-03-03 21:04)
Sticky FAQs
HSLAB Shutdown Folder
Maximum wait time for Group Policy scripts
Computer Configuration\Administrative Templates\System\Logon
Description
Determines how long the system waits for scripts applied by Group Policy to run.
This policy limits the total time allowed for all logon, startup, and shutdown scripts applied by Group Policy to finish running. If the scripts have not finished running when the specified time expires, the system stops script processing and records an error event.
By default, the system lets the combined set of scripts run for up to 600?seconds (10?minutes), but you can use this policy to adjust this interval.
To use this policy, in the Seconds box, type a number from 1?to?32,000 for the number of seconds you want the system to wait for the set of scripts to finish. To direct the system to wait until the scripts have finished, no matter how long they take, type?0.
This interval is particularly important when other system tasks must wait while the scripts complete. By default, each startup script must complete before the next one runs. Also, you can use the Run logon scripts synchronously policy to direct the system to wait for the logon scripts to complete before loading the desktop.
An excessively long interval can delay the system and inconvenience users. However, if the interval is too short, prerequisite tasks might not be done, and the system can appear to be ready prematurely.
Tags: -
Related entries:
- How to configure For Apache versions 2.2.x ?
- What is HSLAB HTTP Monitor?
- What is HSLAB Sys Monitor?
- What is HSLAB Force Down?
- What is HSLAB Prefetch Manager?
- About Performance Monitoring
- Locating Performance Bottlenecks
- Free Website Monitoring
- How to configure Apache Module mod_status
- How to install and configure mod_status?
- Setting mod_status up
- Current Apache status is with the mod_status module
- What is HSLAB Print Logger PE?
- What is the suspicious Rundll32.exe process?
- Windows stops responding during Windows XP shut down
Last update: 2007-07-25 02:05
Author: Oleg
Revision: 1.0
You cannot comment on this entry