SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Right now we're moving from a SharePoint 2007 and SharePoint 2010 farm, my current list of solutions implemented in the 2007 farm numbers somewhere in the 100's. A few ideas I had for moving them included:

1) PowerShell scripting the entire thing, building a script to loop over every .wsp, .cab, etc. and deploy.

2) Any third party utils or pre-built scripts that can help in this?


share|improve this question
up vote 1 down vote accepted

You can script installs, but I wouldn't recommend doing a wholesale install of 100+ solutions. I would evaluate them to see which ones are still needed and perform testing on them to see if they will cause any problems. I understand that it will take a lot more work, but with that many solutions it would be pretty difficult to troubleshoot the system after the fact if there are any problems.

share|improve this answer
This would be done on an expendable dev platform first for testing, mostly these solutions are custom in-house stuff as opposed to third party, so being of a slightly lower quality I'm definitely expecting issues. – tekiegreg Jul 13 '10 at 19:23

see at

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.