Sharpoint 2010 migration

I am performing a sharepoint migration from sharepoint 2007 to 2010,where the new destination 2010 sharepoint server is hosted on a new sql server.

I backed up all content databases and restored them to the new database server and installed sharepoint 2010 standard using all recommended procedures.

The upgrsde of the content databases and failing because of missing plugins that are not installed on the destination sharepoint server. Is there any powershell command or method to use that will capture the plugins on sharepoint 2007 in a backup and restore or migrate the plugins to the destination server in the migration?
Who is Participating?
BembiConnect With a Mentor CEOCommented:
You may have a look here:


First is to see all features which are installed and second one shows everything in Sharepoint.

Also see what is installed as farm solutions in central admin.

I guess, if there are any problem with the old configuration even a in place upgrade will fail. If really nothing helps, a lab environment can help, at least you can delete sites to see, which site may produce the error. Of course some homework.

But as more or less everything in Sharepoint should come up as solution, either a farm solution or a user solution, you should see it with the tools above or you should at least get an error message with an guid, which can identify the problem. Even keep in mind, if allowed, that a user may have installed something if they are allowed to do. Possibly a web part or a user solution.

Hope one of the tools can gibe you a clue.
You may check this article for premigration steps:

What affects features, you may check your sites, which features are activated or installed. As a web site reflects to these features via a guid, the migration may fail, when the featiure, whcih is references in the web application or site colletion or site is not instlled or activated on the new system.

You may check this:
The tool is available from CodePlex and show you all installed features and relations in the old environment.

Or use Test-SPContentDatabase Powershell, an article about this Power Shell command you can find here:

Revove all unneeded features or install them on the new system first.
jkeegan123Author Commented:
using any of these tools, I am still not able to complete the migrations.  The deeper I go, the more it looks like the only thing that is going to work is an in-place upgrade, and I don't want to do this.

The upgrade is failing because of the plugins...and I cannot disturb the production environment to perform this migration.  

Are there any other tips you can give?  Microsoft PSS is also unable to take us any further.  I've also tried 3rd party migration tools, and we are still not able to progress.

I'm considering taking a copy of the SQL server, the Sharepoint Server, and a domain controller and creating a walled-garden type lab so that I can break the systems quite thoroughly and easily roll back when different methods don't work.

jkeegan123Author Commented:
This project is still ongoing...we have not been completely successful yet.  We have broken the site out to a lab and done an in place migration to the same version on a stand-alone server successfully.  Now we're trying to do the in-place upgrade in the lab and we'll see how we do.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.