Brian Pierce
asked on
Software Deplyment GPO timeout
Is there a way of stopping GPOs timing out when applying software. There have been issues when deploying some applications (5-6Gb) where the GPO seems to time-out leaving the application partially installed. Any ideas ?
I don't have an answer to your question but I don't think that GPO is a proper way to install such a large application. Consider the required network bandwidth alone. How many machines are you talking about?
ASKER
It is not that often it needs to be done and bandwidth is not an issue. I just want to stop the GPO timing out.
Ok, then I think this could help you:
http://help.lockergnome.com/windows/Customising-hard-coded-Group-Policy-processing-timeout-ftopict556460.html
Good luck!
Daniel
http://help.lockergnome.com/windows/Customising-hard-coded-Group-Policy-processing-timeout-ftopict556460.html
Good luck!
Daniel
ASKER
As I feared the answer is - can't be done - is it different in Win2008 ?
I wait a while before I issue the points.
I wait a while before I issue the points.
Did you scroll completely down at the article? Does the fix with the registry key not fit in your situation?
Here the excerpt:
However, it is possible to
extend the time that Group Policy waits for by setting the MaxGPOScriptWait
key in HKLM\SOFTWARE\Microsoft\Wi ndows\Curr entVersion \Policies\ System, which
is the same as setting the 'Maximum wait time for Group Policy scripts' value
in Group Policy. There is more information on this registry setting here:
http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/re...try/915
If you increase this timeout from the default value of 600 seconds (10
minutes), or set it to 0 so that there is no timeout, then the computer will
wait for the specified amount of time after the 1 hour default for all Group
Policy processing to complete, before initiating the reboot. This fixed my
problem with software installation and hopefully also should fix any other
problems people might be having with the 1 hour Group Policy processing
timeout.
Here the excerpt:
However, it is possible to
extend the time that Group Policy waits for by setting the MaxGPOScriptWait
key in HKLM\SOFTWARE\Microsoft\Wi
is the same as setting the 'Maximum wait time for Group Policy scripts' value
in Group Policy. There is more information on this registry setting here:
http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/re...try/915
If you increase this timeout from the default value of 600 seconds (10
minutes), or set it to 0 so that there is no timeout, then the computer will
wait for the specified amount of time after the 1 hour default for all Group
Policy processing to complete, before initiating the reboot. This fixed my
problem with software installation and hopefully also should fix any other
problems people might be having with the 1 hour Group Policy processing
timeout.
ASKER
The link does not exist - not clear if MaxGPOScriptWait is a key or a dword?
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
Just found the same article - I'll give it a try