On Tue, 20 Jul 2004 20:43:16 -0700, "Tim"
<(E-Mail Removed)> wrote in
microsoft.public.win2000.cmdprompt.admin:
>I have a login script which i think may be timing out
>halfway through. It maps local network drives and then
>maps drives from another lan via a ISDN line which often
>is very busy(slow). I think that when the isdn line is
>busy eventally the script just gives up and stops where
>it is, instead of copleting the script. Is there a way of
>not letting it timeout? Or do you think my problem is
>elsewhere?
See Group Policy:
Computer Configuration/
Administrative Templates/
System/
Logon/
Maximum wait time for Group Policy scripts
<QUOTE>
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.
</QUOTE>
--
Michael Bednarek
http://mbednarek.com/ "POST NO BILLS"
Similar Threads
