Perform post-upgrade steps for an in-place upgrade (Office SharePoint Server)
Updated: March 5, 2009
Applies To: Office SharePoint Server 2007
After you have upgraded your sites, there may still be a few things that you need to do before you are ready to finish the upgrade. Depending on your environment, you may need to:
Migrate data from SharePoint Portal Server 2003 backwards-compatible Web Storage System document libraries, if you have any in your environment.
After you have completed these steps, you can proceed to Finalize upgrade (Office SharePoint Server).
Search: install or upgrade additional files needed by Search
Install new wordbreaker and filter binaries.
Resolve any crawl rule conflicts from indexes and upgrade noise words and thesaurus files.
Language files for different languages will be made available at different times; check the Microsoft Download Center (http://go.microsoft.com/fwlink/?LinkId=89124) periodically if you need a language pack that is not yet available.
Search: reconfigure performance-level settings and site-hit rules
The performance-level settings and site-hit rules are not upgraded from your SharePoint Portal Server 2003 environment. You must configure the performance-level settings and site-hit rules again in your Office SharePoint Server 2007 environment. For more information about configuring the performance level of the index server and creating site-hit rules, see Configure the Office SharePoint Server Search service (Office SharePoint Server) and Manage crawler impact (Search Server 2008).
Migrate data from SharePoint Portal Server 2003 backwards-compatible Web Storage System document libraries
If you have any data in a SharePoint Portal Server 2003 backwards-compatible Web Storage System document library, you can migrate the data into new document libraries. Document libraries in Office SharePoint Server 2007 have workflow capabilities, plus the ability to use multiple content types within one library, making it much easier to maintain the same library structure that you may have used in Microsoft SharePoint Portal Server 2001.
To migrate content from your SharePoint Portal Server 2003 backwards-compatible Web Storage System document libraries to Office SharePoint Server 2007 document libraries, you can manually copy the documents to a file share, and then use Explorer view or the multiple file upload feature to import the documents to the new document libraries. Note that any metadata associated with the documents, including versioning, workflow state, and so on, will not be imported.
There are also community-supported tools that can help you migrate documents from a SharePoint Portal Server 2003 backwards-compatible Web Storage System document library to an Office SharePoint Server 2007 document library. Microsoft does not provide support for community-developed or third-party migration tools.
Remove Windows SharePoint Services previous version language packs
You must install the Windows SharePoint Services 3.0 language packs before you can upgrade sites in the corresponding previous version language. After you have upgraded the sites to use the new language packs, you can remove the old version of the language pack.
Language packs for different languages will be made available at different times; check the Microsoft Download Center (http://go.microsoft.com/fwlink/?LinkId=89124) periodically if you need a language pack that is not yet available.
User profiles: start a full import
The user profiles for personal sites are not upgraded from your SharePoint Portal Server 2003 environment. Before you can create personal sites or manage user profiles, you must start a full import of user profile information from connections to directory services, such as Active Directory Domain Services or LDAP. For more information, see Import user profiles (Office SharePoint Server).
Move a missing Web site to the correct location
You may find that after you upgrade a server, you cannot open a particular Web site. This can happen if the URL is too long. If this is the case, the Web site will be in the holding Web site, known as Unmovable Webs, directly under the root of the Web server. You must change the length of the URL, which can have no more than 256 characters. Then you can manually move the content from the holding Web site to the correct location.
Reapply blocked file type settings
After you upgrade, you can reapply the blocked file type settings that you saved before you upgraded.
For information about how to save blocked file type settings, see Save blocked file type settings (Office SharePoint Server).
Use the following procedure to reapply the blocked file type settings after you upgrade.
Reapply blocked file type settings
Open the Notepad file that contains the file name extensions that you saved before the upgrade.
On the Edit menu, click Select All, and then click Copy.
In Windows SharePoint Services 3.0, on the Central Administration page, in the Security Configuration section, click Blocked file types.
Right-click in the area where the file name extensions are listed, and paste a copy of the previously saved file name extensions at the end of this list.
The application allows duplicate file name extensions to appear on the list, so you do not need to delete anything.
Click OK to save the file.
Site collection owners might need to be added manually after upgrade
Only the person who is listed as a site owner when the portal was created will be added as a site collection owner in the upgraded version of Office SharePoint Server. All other root Web administrators will be administrators; they will not be site collection administrators. If these administrators must be site collection administrators, you must manually add them as site collection administrators.
Download this book
This topic is included in the following downloadable book for easier reading and printing:
See the full list of available books at Downloadable content for Office SharePoint Server 2007 .