Pre-Scan and Analysis Tool
The Pre-Scan Tool is an assessment and reporting tool that provides feedback on the upgrade process based on the specific SharePoint instance. You can download the tool from Microsoft
You must run the Pre-Scan tool against an existing SharePoint instance. Although running the Pre-Scan process appears to be an optional step, it's not. Instead, it's a required prerequisite before you can execute the actual upgrade. The Pre-Scan process scans the sites and flags the database to indicate that the scan has been completed. Later, the upgrade process (psconfig.exe
) uses the information collected during the Pre-Scan process.
If you try to run the upgrade process without running the Pre-Scan, you'll get an error message stating that the Pre-Scan needs to be performed before the Upgrade process can continue.
During the scan, the Pre-Scan tool reports on these elements:
- Custom Web Parts: Pre-Scan detects and reports the existence of any custom Web Parts.
- Orphaned Objects: Finds objects that have become orphans, for example, a list that exists in the database but is not linked to any site.
- Sites using customized site templates: This is for user reference, so that the user can verify the customizations after the upgrade process has been executed. For more information on upgrading custom templates please refer to the documentation.
- Sites based on custom site definitions: This is for user reference as well.
- Sites based on specific languages: Informs the user that a specific language pack needs to be installed.
- Unghosted Pages: Pre-Scan provides a list of unghosted pages along with their URLs.
It is important to understand that this list merely provides a good starting point; there is always a possibility that the upgrade process may encounter other issues that Pre-Scan failed to find.
Pre-Scan is a command line tool. To execute it, use one of the following commands:
PRESCAN /c preupgradescanconfig.xml /all
The second option accepts a specialized XML file (preupgradescanconfig.xml
in the example) as a parameter. Use that option when you want to exclude sites based on custom site templates (.STP
files) from the Pre-Scan reports.
Pre-Scan generates the following three files as output:
- Pre-Scan Log (Text File): This file logs the time when the scan was performed.
- Pre-Upgrade Report Log (Text File): This file contains the checks performed and the issues detected. Figure 2 illustrates a sample log.
- Pre-Upgrade Report Summary (XML File): Figure 3 shows a sample summary report.
|Figure 2. Sample Pre-Upgrade Report Log: In this report, you can see the checks the Pre-Scan tool performed and any issues that were detected.||
|Figure 3. Sample Pre-Upgrade Report Summary: Here's an example of the XML-formatted summary report.||
Using the Pre-Scan reports, you can take the appropriate actions to rectify any reported issues and then select a migration approach, but first you need to ensure that your current hardware will run the upgrade, and you should backup your system.
Verify Hardware Requirements and Back Up
You have multiple options when upgrading from SPS2003 to MOSS 2007, but before you attempt to execute any of them, you should be aware that while it may be possible to run MOSS 2007 on your current hardware, the system requirements for MOSS 2007 are higher than those for SPS2003. Therefore, you should check to ensure your current hardware meets the MOSS 2007 system requirements. To do that, download the system requirements for MOSS 2007
and compare your system specifications against those requirements.
You should also backup your existing SharePoint system and make a test of the backup to ensure that it works. That way, you can go back to the existing version if the upgrade process fails or corrupts the existing instance for some unpredictable reason. I recommend that you follow the procedures described in the TechNet article "SharePoint 2003 Disaster Recovery