Home > Blogroll, MOSS, MS SharePoint Sever > Install and run the pre-upgrade scan tool

Install and run the pre-upgrade scan tool

To install the prescan.exe tool, you must install Microsoft Office SharePoint Server 2007 to a test server. After you install, search for the two files prescan.exe and preupgradescanconfig.xml, and then copy the files to the computer that runs the existing version.



You must be a member of the Administrators group on the local computer to run this tool.


1.   On the command line, change to the folder that contains the two files, and then run the following command to scan all servers in your server farm:


prescan.exe /c preupgradescanconfig.xml /all



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 /vURL parameter). If you do not supply a scoping parameter, all Web sites will be scanned.






Templates used by SharePoint Portal Server 2003 can be incorrectly identified during the pre-upgrade scan as custom templates unless you use the preupgradescanconfig.xml file when you perform the scan. This 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.








If you have already installed the new version but have not yet run the SharePoint Products and Technologies Configuration wizard, you can run the pre-upgrade scan tool from the following folder: %PROGRAMFILES% \Common Files\Microsoft Shared\web server extensions\12\BIN.


Running the scan can take several minutes or a few hours, depending on the amount of content in your environment.








2.   After the scan has completed, a summary report 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; this prescan.log file notes the time or 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 (search for “error” in the report to find the issues). 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.



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: