Prescan.

exe Readme
Before you can upgrade to Microsoft Office SharePoint Server 2007 or Microsoft Windows SharePoint Services 3.0, you must run the pre-upgrade scan tool (Prescan.exe) against your existing Web sites. The pre-upgrade scan tool scans your sites and reports issues, which enables you to 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. We highly recommend 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. Note It is a best practice to run the pre-upgrade scan tool at least twice once while you are planning your upgrade to identify issues, and then again before you perform the upgrade to verify any changes you made and identify any new issues that may have resulted from changes to your environment.

For more information about upgrade, migration, and using the pre-upgrade scan tool, see the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=89572).

What the pre-upgrade scan tool does

Prescan.exe has two primary purposes: y Parse and save list definitions with the associated lists. SharePoint Portal Server 2003 Service Pack 2 parses and saves list definitions with the associated lists whenever a list is modified. However, this process should be completed for all lists, so Prescan.exe calls the method from SharePoint Portal Server 2003 Service Pack 2 to persist that data. Report on common issues that will result in a failed upgrade. Running Prescan.exe, identifying and resolving reported issues, and then rerunning Prescan.exe to verify those fixes is a best practice when planning an upgrade to Office SharePoint Server 2007 or Windows SharePoint Services 3.0.

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: y 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 wont 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. We recommend that you recover any orphaned objects before upgrading. Tip Members of the Administrators group on the Web servers can recover orphaned items before the upgrade by following the steps in Knowledge Base article 918744, Description of a new command-line operation that you

can use to repair content databases in Windows SharePoint Services (http://go.microsoft.com/fwlink/?linkid=69958&clcid=0x409). y 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. Note Heavily obfuscated custom Web Parts might need to be rebuilt and redeployed after the upgrade. y 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.

Running the pre-upgrade scan tool

You can use the pre-upgrade scan tool to scan all Web sites in your environment (by using the /all parameter) or to scan a specific URL (by using the /v <URL> parameter). If you do not supply a scoping parameter, all Web sites will be scanned. The pre-upgrade scan tool takes the following parameters: Description Scans all site collections in a server farm. Scans all site collections at a specific URL. Uses the preupgradescanconfig.xml file while scanning. This configuration file contains additional logic to identify the portal site templates as standard templates used by SharePoint Portal Server 2003 rather than as custom templates based on Windows SharePoint Services 2.0. You must use this parameter when scanning site collections based on SharePoint Portal Server 2003. This parameter has no effect when scanning site collections based on Windows SharePoint Services 2.0. Running the scan can take several minutes or a few hours, depending on the amount of content in your environment. To run Prescan.exe, perform the following steps: 1. On the command line, change to the folder that contains the file, and then run the prescan.exe command with the appropriate parameters. For example, prescan.exe /all or prescan.exe /c preupgradescanconfig.xml /all. 2. After the scan has completed, review the summary report that is displayed in the command-line window. If there were any errors or if any upgrade issues were found for your sites, you can review the full report to see the details. The report is named PreupgradeReport_uniqueID_Log.txt (where uniqueID is a number string) and it is located in the temp directory on the computer of the user who ran the tool (for example, %SYSTEMDRIVE%:\Documents and Settings\User1\Local Settings\Temp). There is also a prescan.log file in the same directory, which notes the times when the pre-upgrade scan tool was run. After you run the pre-upgrade scan tool, you can review the reports to find and troubleshoot issues. (You can search for "error" in the report to find the issues.) You Parameter /all /v <URL> /c preupgradescanconfig.xml

can also share the relevant pre-upgrade scan test results with other members of the upgrade team. For example, you can report issues such as customized site templates or custom Web Parts to the appropriate site owner, Web designer, or developer before scheduling the upgrade to give them time to investigate the issues and take preliminary steps. For example, a designer or developer might decide that it would be prudent to rebuild a heavily obfuscated Web Part before the upgrade occurs. Site owners can then verify any customizations that have been done to their sites, including site templates and changes to core Active Server Pages Extension (ASPX) files, and can note any potential issues.

Common Prescan.exe errors

For more information about common errors that are logged in the pre-upgrade scan report, see the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=89571).