How to extend the scripts aborting period on SteadyState
Somebody, please help me! I'm using "Widows Steady State 2.5(WSS)" on "XP SP3", and setting WSS schedule updates. However, updates sometimes aborted due to its default specification. I found the specification in the article below. "http://social.technet.microsoft.com/Forums/en-US/windowssteadystate/thread/b9efd5f2-b6d1-4d2a-93ab-25f5f6a395e6/" Does anybody know how to extend this period? I need your help...
January 29th, 2011 1:23am

Hi, Base on my researched, I’m afraid there is impossible to extend the period of scripts, that’s by design. Thank you for your understanding. Regards, Leo HuangPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
February 1st, 2011 5:31pm

The default time-out for scripts is 30 minutes. This can be overridden by specifying a different time-out value in this registry key. Navigate to this path in the registry: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Windows SteadyState\Parameters And create a new value with the type REG_DWORD. Set this to the number of minutes you want to use as a time-out. Since the system cannot be used while it's applying updates, it may be safer to simply log on as Administrator and run updates manually if there is a particular large update that's causing problems.Thanks, Rob Elmer Development Lead Windows SteadyState
February 1st, 2011 6:13pm

The default time-out for scripts is 30 minutes. This can be overridden by specifying a different time-out value in this registry key. Navigate to this path in the registry: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Windows SteadyState\Parameters And create a new value with the type REG_DWORD. Set this to the number of minutes you want to use as a time-out. Since the system cannot be used while it's applying updates, it may be safer to simply log on as Administrator and run updates manually if there is a particular large update that's causing problems.
Free Windows Admin Tool Kit Click here and download it now
February 4th, 2011 8:09pm

The default time-out for scripts is 30 minutes. This can be overridden by specifying a different time-out value in this registry key. Navigate to this path in the registry: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Windows SteadyState\Parameters And create a new value with the type REG_DWORD. Set this to the number of minutes you want to use as a time-out. Since the system cannot be used while it's applying updates, it may be safer to simply log on as Administrator and run updates manually if there is a particular large update that's causing problems.
February 4th, 2011 8:09pm

Hi Rob, Thank you for your quick responce, and sorry for not answering soon. You gave me what I eagered to be given. I'll try it in the production environment. May I beg one more question related to WSS? That's the ralationship between WSS and WindowsUpdate. I set WindowsUpdate everynight at 23:00, and so as WSS at 25:00. Does WindowsUpdate work propery? Somepeople on the web say that WSS canceled WindowsUpdate. Is it true? Best Regards,
Free Windows Admin Tool Kit Click here and download it now
February 8th, 2011 1:23am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics