Home > Blogroll, MOSS, MS SharePoint Sever > Pre-upgrade scan tool (Office SharePoint Server)

Pre-upgrade scan tool (Office SharePoint Server)

You must use the pre-upgrade scan tool to scan your sites, and then fix any errors before you perform an upgrade. If you have not successfully run this tool and you attempt to upgrade your environment, when you attempt to run the SharePoint Products and Technologies Configuration wizard, the wizard will exit and prompt you to run the tool. It is highly recommended that the server administrator run the pre-upgrade scan tool before the upgrade, and resolve any problems that can be resolved before scheduling the upgrade.



You might need to run the pre-upgrade scan tool more than once. For example, if you run the tool to evaluate your server farm but you are not going to be performing the upgrade for a few weeks, you will need to run the tool again just before you perform the upgrade to scan any new sites and to ensure that no additional issues have appeared in the meantime. Also, after you resolve any issues from your first scan, you will need to run the tool again; otherwise, when you try to run the SharePoint Products and Technologies Configuration wizard, you might see an error message that pre-scan has not been run.


Issues that are reported by the pre-upgrade scan tool:

For each SharePoint site, issues reported by this tool include the existence of the following objects:

·    Customized site templates   You need to know which site templates have been customized for a particular site so you can verify the customizations again after the upgrade.

·    Orphaned objects   Objects such as list items, lists, documents, Web sites, and site collections can be orphaned — that is, the objects exist but are not associated with a particular site. Because orphaned objects do not work in the previous version, they won’t work after the upgrade. If you perform an in-place upgrade, the orphaned items will still exist but will not work. If you perform a gradual upgrade, orphaned items will not be copied to the new site. It is recommended that you clean up any orphaned objects before upgrading.

·    Custom Web Parts   Report the existence of custom Web Parts to the appropriate site administrator or developer before upgrading, to give the administrator or developer time to investigate.


Heavily obfuscated custom Web Parts may need to be rebuilt and redeployed after the upgrade.


·    Sites that are based on languages or that use controls that are not installed   If the database contains a Web site based on a language template pack that is not currently installed on the front-end Web servers, or a Web site that uses controls (such as the Microsoft Office Web Components) that are not currently installed on the front-end Web servers, install the missing language packs or controls before upgrading.


Use the information gathered from the pre-upgrade scan tool to determine:

·    Whether to perform an in-place or a gradual upgrade.

It is important to consider the report generated by the pre-upgrade scan tool when making this decision. Generally, if you find significant issues, use a gradual upgrade rather than an in-place upgrade so you can resolve the issues.

·    Whether to upgrade some or all site collections that contain customized sites.

·    Which sites need to have customizations reapplied or redone after upgrade and therefore might take longer than others in the review stage.


When you run the pre-upgrade scan tool, the metadata on all lists and libraries in your sites is updated. This means that lists and libraries in the environment will show that they have been updated after the pre-upgrade scan tool is run. The dates for individual list items and documents are not changed by this process.


  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: