Basically it needs to have time for the timer jobs to run on each server (this is what makes the web.config changes), from my experience throwing them in one after the other works sometimes, but not all the time.
Ideally what you're deployment script should do is run the timer jobs on the remote servers, that way you are not waiting for a random amount of time and then continuing in the hope that it ran OK. If you look into some of the stuff with PowerShell 2.0 you can use Exec-Command to send commands to a remote machine (I think you need to be able to use the CredSSP option on that for the command to authenticate right when you call stsadm, which means server 2008 will work, server 2003 doesn't support that one). In the part where I haven't been able to call the remote commands, I usually do a cople of manual deployments to get a feel for how long it takes to complete and then a bit of time to that. Regards, Brian Farnhill Microsoft SharePoint Server MVP Microsoft Virtual Technical Solutions Professional Blog: http://blog.brianfarnhill.com<http://blog.brianfarnhill.com/> | Twitter: @BrianFarnhill<http://twitter.com/BrianFarnhill> | Mobile: 0408 289 303 ________________________________ Canberra SharePoint User Group: http://www.sharepointusers.org.au/Canberra From: [email protected] [mailto:[email protected]] On Behalf Of Paul Noone Sent: Wednesday, 7 July 2010 10:48 AM To: ozMOSS Subject: Safe delay between solution deployments Is there a safe or minimum delay that should be added between the deployment of multiple solutions, especially where a web.config modification is required? I've been typically deploying them all in tandem via a batch file and expecting SharePoint to take care of the rest but have seen issues arising with timer job lock-ups etc. Kind regards, Paul Noone --------------------------------------------------- Online Developer/Administrator Information Communication and Technology Catholic Education Office, Sydney p: (02) 9568 8461 f: (02) 9568 8483 e: [email protected]<mailto:[email protected]> w: http://www.ceosyd.catholic.edu.au/
_______________________________________________ ozmoss mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
