Server Fault is a question and answer site for system and network administrators. 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

My company will be upgrading our SharePoint 2007 site to SP2010 and I know how to do it. But there is one step in the migration step that I don't.

The pre-upgrade checker will give you a list of components/solutions that are referenced in the contentDBs but is not installed on the upgraded sharepoint farm.

What do you do if the component is not available for 2010? (I believe the only option is uninstall the component before migration). Even if an upgrade is available for upgraded components won't it have a different GUID and therefore not solve the migration error messages?

In other words, isn't it true that "install missing components" advice for 07 components only work if the 07 components works in 2010 (which I think is very few components.).



share|improve this question

A feature or solution that is upgraded should never ever change their guids, so that is normally not an issue.

Your options for the missing components are:

  1. Install components on new farm - actually most things works just fine in 2010
  2. Uninstall components in old farm before upgrading
  3. Copy "missing files" from old to new farm (if you don't have any solution package, WSP at hand)
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.