Survey
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Download Upgrade sites (Windows SharePoint Services)
Transcript
Contents WSSDeployment2.Cover ............................................................................................................................................................... 6 Upgrading to Windows SharePoint Services 3.0 technology ..................................................................................... 6 WSSDeployment2.Copy................................................................................................................................................................. 7 Roadmap to Windows SharePoint Services 3.0 content .................................................................................................. 8 Windows SharePoint Services 3.0 content by audience ............................................................................................... 9 Windows SharePoint Services 3.0 IT professional content by stage of the IT life cycle ............................... 11 Download this book ................................................................................................................................................................ 16 I. Plan and prepare for upgrade (*WSS*) ............................................................................................................................. 17 Subhead........................................................................................................................................................................................ 17 Chapter overview: Plan and prepare for upgrade ............................................................................................................ 18 Download this book ................................................................................................................................................................ 18 Determine upgrade approach ................................................................................................................................................. 19 Choose an upgrade approach ............................................................................................................................................. 20 Special cases ............................................................................................................................................................................... 21 Download this book ................................................................................................................................................................ 22 How the upgrade process works (Windows SharePoint Services) ............................................................................ 24 In-place upgrade ....................................................................................................................................................................... 25 Gradual upgrade ....................................................................................................................................................................... 26 How URL redirects are handled during gradual upgrade ........................................................................................ 28 Download this book ................................................................................................................................................................ 30 Review system requirements for upgrade (Windows SharePoint Services) .......................................................... 31 Stand-alone installation ......................................................................................................................................................... 32 Server farm installation ........................................................................................................................................................... 33 Worksheet.................................................................................................................................................................................... 34 Estimate how long the upgrade process will take and the amount of space needed (Windows SharePoint Services) ................................................................................................................................................................ 35 Estimate the amount of space needed for the upgrade ........................................................................................... 36 Estimate how long the upgrade will take ........................................................................................................................ 38 Worksheet.................................................................................................................................................................................... 40 Create communication plan (Windows SharePoint Services) ...................................................................................... 41 When and what to communicate to the upgrade team ........................................................................................... 42 When and what to communicate with site users ......................................................................................................... 43 Download this book ................................................................................................................................................................ 43 Use a trial upgrade to find potential issues (Windows SharePoint Services) ........................................................ 44 Review common issues .......................................................................................................................................................... 44 Perform a trial upgrade .......................................................................................................................................................... 47 Test custom Web Parts ........................................................................................................................................................... 48 Download this book ................................................................................................................................................................ 48 Determine how to handle customizations (Windows SharePoint Services) .......................................................... 49 Carefully monitor your use of customizations and Web Parts ............................................................................... 51 Worksheet.................................................................................................................................................................................... 51 Develop new custom site definitions and create upgrade definition files (Windows SharePoint Services) .......................................................................................................................................................................................................... 52 Before you develop new custom site definitions ......................................................................................................... 52 Develop new custom site definitions ................................................................................................................................ 53 About upgrade definition files ............................................................................................................................................ 53 Create upgrade definition files ............................................................................................................................................ 54 Record upgrade definition file information on a worksheet ................................................................................... 54 Download this book ................................................................................................................................................................ 54 II. Perform pre-upgrade steps (*WSS*) ................................................................................................................................. 55 Subhead........................................................................................................................................................................................ 55 Chapter overview: Perform pre-upgrade steps (Windows SharePoint Services) ................................................. 56 Download this book ................................................................................................................................................................ 56 Install Service Pack 2 for Windows SharePoint Services 2.0 ........................................................................................ 57 Download this book ................................................................................................................................................................ 57 Install all pre-requisites (Windows SharePoint Services) ............................................................................................... 58 Install Microsoft .NET Framework 3.0 ............................................................................................................................... 59 Enable Microsoft ASP.NET 2.0 ............................................................................................................................................. 59 Download this book ................................................................................................................................................................ 59 Communicate downtime to site owners and users (Windows SharePoint Services) ......................................... 60 Download this book ................................................................................................................................................................ 60 Run and test a full backup in SQL Server (Windows SharePoint Services) ............................................................ 61 Back up a database .................................................................................................................................................................. 61 Test the backups ....................................................................................................................................................................... 63 Download this book ................................................................................................................................................................ 63 Create new domain names (gradual upgrade only) (Windows SharePoint Services) ........................................ 64 Download this book ................................................................................................................................................................ 64 Run the pre-upgrade scan tool (Windows SharePoint Services) ............................................................................... 65 Issues that are reported by the pre-upgrade scan tool ............................................................................................ 65 Install and run the pre-upgrade scan tool ...................................................................................................................... 67 Download this book ................................................................................................................................................................ 68 Deploy upgrade definition files and new site definitions (Windows SharePoint Services) ............................. 69 Before you deploy upgrade definition files and site definitions ............................................................................ 69 Deploy upgrade definition files and site definitions .................................................................................................. 69 Upgrade custom Web Part packages (Windows SharePoint Services) .................................................................... 71 Upgrade custom Web Part packages ............................................................................................................................... 71 Download this book ................................................................................................................................................................ 71 Save blocked file type settings (Windows SharePoint Services) ................................................................................ 72 III. Perform an in-place upgrade (*WSS*) ........................................................................................................................... 73 Subhead........................................................................................................................................................................................ 73 Chapter overview: Perform an in-place upgrade (Windows SharePoint Services).............................................. 74 Download this book ................................................................................................................................................................ 74 Install and configure Windows SharePoint Services for an in-place upgrade ...................................................... 75 Before you begin....................................................................................................................................................................... 76 Install Windows SharePoint Services 3.0 ......................................................................................................................... 76 Run the SharePoint Products and Technologies Configuration Wizard ............................................................. 78 Install and configure Windows SharePoint Services 3.0 using the command line ......................................... 80 Review the log files and resolve any issues .................................................................................................................... 80 Install available language template packs (Windows SharePoint Services) ........................................................... 81 About installing language template packs and upgrading sites ........................................................................... 82 About changing languages................................................................................................................................................... 82 Install language template packs ......................................................................................................................................... 83 IV. Perform a gradual upgrade (*WSS*) .............................................................................................................................. 85 Subhead........................................................................................................................................................................................ 85 Chapter overview: Perform a gradual upgrade (Windows SharePoint Services) ................................................. 86 Download this book ................................................................................................................................................................ 86 Install and configure Windows SharePoint Services for a gradual upgrade ......................................................... 87 Before you begin....................................................................................................................................................................... 88 Install Windows SharePoint Services 3.0 ......................................................................................................................... 88 Install and configure Windows SharePoint Services 3.0 on other front-end Web servers in the farm .. 89 Run the SharePoint Products and Technologies Configuration Wizard ............................................................. 90 Install and configure Windows SharePoint Services 3.0 using the command line ......................................... 91 Review the log files and resolve any issues .................................................................................................................... 92 Upgrade sites (Windows SharePoint Services) .................................................................................................................. 93 Upgrade sites by using Central Administration pages .............................................................................................. 93 Upgrade sites by using the command line ..................................................................................................................... 95 Upgrade sites after installing a language template pack ......................................................................................... 97 Download this book ................................................................................................................................................................ 97 V. Deploy a new server farm, then migrate content databases ................................................................................ 98 Subhead........................................................................................................................................................................................ 98 Chapter overview: Deploy a new farm, then migrate databases (Windows SharePoint Services)................ 99 Download this book .............................................................................................................................................................. 100 Prepare the new Windows SharePoint Services 3.0 environment ........................................................................... 101 Download this book .............................................................................................................................................................. 102 Migrate content databases ..................................................................................................................................................... 103 Before you begin..................................................................................................................................................................... 103 Set the previous version databases to be read-only ................................................................................................ 104 Back up the previous version databases by using SQL Server tools .................................................................. 104 Restore the backup copy to the new farm ................................................................................................................... 106 Add the databases to the Web applications................................................................................................................ 108 Add a content database to a Web application by using the Stsadm command-line tool .................... 109 Review the upgrade log files for any issues ................................................................................................................. 110 Repeat the restore and add database procedures for all content databases ................................................ 111 Download this book .............................................................................................................................................................. 111 Migrate content databases from WMSDE to Windows Internal Database .......................................................... 112 Detach the databases from your WMSDE instance .................................................................................................. 112 Copy and attach the database files to SQL Server .................................................................................................... 113 Add the databases to the Web applications................................................................................................................ 115 Add a content database to a Web application by using the command-line tool .................................... 115 Review the upgrade log files for any issues ................................................................................................................. 117 Repeat the restore and add database procedures for all content databases ................................................ 117 Download this book .............................................................................................................................................................. 117 VI. Perform post-upgrade steps (*WSS*) ........................................................................................................................... 118 Subhead...................................................................................................................................................................................... 118 Chapter overview: Perform post-upgrade steps (Windows SharePoint Services) ............................................. 119 Download this book .............................................................................................................................................................. 119 Verify upgrade (Windows SharePoint Services) .............................................................................................................. 120 View the upgrade log ............................................................................................................................................................ 120 Force a software upgrade .................................................................................................................................................... 121 View the Servers in Farm page .......................................................................................................................................... 122 Review upgraded sites (Windows SharePoint Services) .............................................................................................. 123 Download this book .............................................................................................................................................................. 124 Revert to a previous version site (Windows SharePoint Services) ........................................................................... 125 Download this book .............................................................................................................................................................. 125 Troubleshoot and resume upgrade (Windows SharePoint Services) ..................................................................... 126 General information about troubleshooting and restarting upgrade ............................................................... 126 Known issues for pre-upgrade scanning ....................................................................................................................... 127 Upgrade is blocked if you use Localhost as your server name ........................................................................ 127 Known issues for in-place upgrade ................................................................................................................................. 128 You must use a domain account, not Network Service, for server farm upgrades .................................. 128 Some settings are not preserved on the Web application when you perform an in-place upgrade ............................................................................................................................................................................................... 128 Upgrade finishes on the first front-end Web server but has failures ............................................................ 128 SPConfigurationDatabase2 sequence error in the upgrade log...................................................................... 129 For in-place upgrades on stand-alone servers, run upgrade from the command-line if you get an error with a login failure or connection failure to the database ................................................................. 130 Known issues for gradual upgrade .................................................................................................................................. 130 You must use a domain account, not Network Service, for server farm upgrades .................................. 130 Additional steps are required to gradually upgrade an SSL-only servers ................................................... 131 I finalized the upgrade, but some sites were not upgraded yet, what can I do? ...................................... 132 Known issues for database migration ............................................................................................................................ 132 You cannot add the same content database more than once to a farm, even on different Web applications ...................................................................................................................................................................... 132 Known issues for customized sites .................................................................................................................................. 133 An application error can result when disallowed customizations are made to Web.config files ....... 133 Download this book .............................................................................................................................................................. 133 Perform post-upgrade steps for an in-place upgrade (Windows SharePoint Services) ................................. 134 Remove Windows SharePoint Services 2.0 language packs .................................................................................. 135 Reapply blocked file type settings ................................................................................................................................... 135 Download this book .............................................................................................................................................................. 136 Perform post-upgrade steps for a gradual upgrade (Windows SharePoint Services)..................................... 137 Delete any upgraded and confirmed 2.0 sites ............................................................................................................ 138 Remove Windows SharePoint Services 2.0 language packs .................................................................................. 138 Reapply blocked file type settings ................................................................................................................................... 138 Download this book .............................................................................................................................................................. 139 Finalize upgrade (Windows SharePoint Services) .......................................................................................................... 140 Download this book .............................................................................................................................................................. 140 Migrate content or sites after upgrade (Windows SharePoint Services) .............................................................. 141 Migrate content by using import/export ...................................................................................................................... 142 Migrate a site collection by using backup/restore .................................................................................................... 142 Download this book .............................................................................................................................................................. 142 Add servers to an upgraded farm (Windows SharePoint Services) ........................................................................ 143 Add a front-end Web server to an upgraded server farm ..................................................................................... 144 Add a back-end database server to an upgraded server farm ............................................................................. 145 WSSDeployment2.Cover Topic Last Modified: 2009-02-19 Upgrading to Windows SharePoint Services 3.0 technology Microsoft Corporation Published: February 2009 Author: Microsoft Office System and Servers Team ([email protected]) Abstract This book provides information and guidelines to lead a team through the process of upgrading to Windows SharePoint Services 3.0. The audiences for this book are business application specialists, lineof-business specialists, information architects, IT generalists, program managers, and infrastructure specialists who are upgrading a solution based on Windows SharePoint Services 3.0. The content in this book is a copy of selected content in the Windows SharePoint Services technical library (http://go.microsoft.com/fwlink/?LinkId=81199) as of the date above. For the most current content, see the technical library on the Web. Additional resources are also available on the Microsoft Web site, including the MSDN Resource Center: Migration and Upgrade Information for SharePoint Developers (http://msdn2.microsoft.com/enus/office/aa905505.aspx) WSSDeployment2.Copy Topic Last Modified: 2009-02-17 The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication. This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, place or event is intended or should be inferred. © 2009 Microsoft Corporation. All rights reserved. Microsoft, Access, Active Directory, Excel, Groove, InfoPath, Internet Explorer, OneNote, Outlook, PerformancePoint, PowerPoint, SharePoint, SQL Server, Visio, Windows, Windows Server, and Windows Vista are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. The names of actual companies and products mentioned herein may be the trademarks of their respective owners. Page 7 of 146 Roadmap to Windows SharePoint Services 3.0 content Topic Last Modified: 2015-03-09 In this article: Windows SharePoint Services 3.0 content by audience Windows SharePoint Services 3.0 IT professional content by stage of the IT life cycle Page 8 of 146 Windows SharePoint Services 3.0 content by audience Each audience for Windows SharePoint Services 3.0 can go to a specific Web site for content that is tailored to that audience. The following table lists the audiences and provides links to the content for each audience. Information Workers IT Professionals Developers Content available on Content available on: Content available on: Office Online TechNet MSDN Home page — a central portal for Information Worker resources (http://go.microsoft.com/fwli nk/?LinkId=88898&clcid=0x 409) Help and How-to — an index for Information Worker content (http://go.microsoft.com/fwli nk/?LinkId=88899&clcid=0x 409) TechCenter — a central portal for IT professional resources (http://go.microsoft.com/fwli nk/?LinkID=73953&clcid=0x 409) Developer Center — a central portal for Developer resources (http://go.microsoft.com/fwli nk/?LinkId=88910&clcid=0x4 09) Technical Library — an index for IT professional content (http://go.microsoft.com/fwli nk/?LinkId=88902&clcid=0x4 09) MSDN Library — an index for Developer content (http://go.microsoft.com/fwli nk/?LinkID=86923&clcid=0x 409) Newly published content — an article that lists new or updated content in the Technical Library (http://go.microsoft.com/fwli nk/?LinkId=88906&clcid=0x4 09) Downloadable books — an article that lists the books available for download (http://go.microsoft.com/fwli nk/?LinkId=88907&clcid=0x4 09) Page 9 of 146 Additionally, there is information for all users of SharePoint Products and Technologies at the community and blog sites listed in the following table. Community content and blogs SharePoint Products and Technologies community portal — a central place for community information (blogs, newsgroups, etc.) about SharePoint Products and Technologies (http://go.microsoft.com/fwlink/?LinkId=88915&clcid=0x409) SharePoint Products and Technologies team blog — a group blog from the teams who develop the SharePoint Products and Technologies (http://go.microsoft.com/fwlink/?LinkId=88916&clcid=0x409) Support Center for Microsoft Windows SharePoint Services 3.0 — a central place for issues and solutions from Microsoft Help and Support (http://go.microsoft.com/fwlink/?LinkId=89561&clcid=0x409) Page 10 of 146 Windows SharePoint Services 3.0 IT professional content by stage of the IT life cycle IT Professional content for Windows SharePoint Services 3.0 includes content appropriate for each stage of the IT life cycle — evaluate, plan, deploy, and operate — plus technical reference content. The following sections describe each stage in the IT life cycle and list the content available to assist IT professionals during that stage. The most up-to-date content is always available on the TechNet Web site. We also offer downloadable books that cover each stage of the IT life cycle, plus books that cover all stages of the life cycle for a specific solution. For an updated list, see Downloadable books for Windows SharePoint Services (http://go.microsoft.com/fwlink/?LinkId=88907&clcid=0x409). Evaluate During the evaluation stage, IT professionals (including decision makers, solution architects, and system architects) focus on understanding a new technology and evaluate how it can help them address their business needs. The following table lists resources that are available to help you evaluate Windows SharePoint Services 3.0. Content Description Links Online content Includes the most Evaluation for Windows SharePoint Services 3.0 technology up-to-date (http://go.microsoft.com/fwlink/?LinkID=88902&clcid=0x409) content. The Technical Library on TechNet is continually refreshed with new and updated content. Page 11 of 146 Content Description Links Evaluation Guide Provides an Windows SharePoint Services 3.0 Evaluation Guide overview, (http://go.microsoft.com/fwlink/?LinkId=86962&clcid=0x409) information about what's new, and conceptual information for understanding Windows SharePoint Services 3.0. Plan During the planning stage, IT professionals have different needs depending on their role within an organization. If you are focused on designing a solution, including determining the structure, capabilities, and information architecture for a site, you might want information that helps you to determine which capabilities of Windows SharePoint Services 3.0 you want to take advantage of, and that helps you to plan for those capabilities and to tailor the solution to your organization's needs. On the other hand, if you are focused on the hardware and network environment for your solution, you might want information that helps you to structure the server topology, plan authentication methods, and understand system requirements for Windows SharePoint Services 3.0. We have planning content, including worksheets, to address both of these needs. The following table lists resources that are available to help you plan for using Windows SharePoint Services 3.0. Content Description Links Online content Includes the most Planning and architecture for Windows SharePoint Services up-to-date 3.0 content. The (http://go.microsoft.com/fwlink/?LinkId=88954&clcid=0x409) Technical Library on TechNet is continually refreshed with new and updated content. Page 12 of 146 Content Description Links Planning Guide, Provides in-depth Planning and architecture for Windows SharePoint Services, Part 1 planning part 1 (http://go.microsoft.com/fwlink/?LinkId=79600) information for application administrators who are designing a solution based on Windows SharePoint Services 3.0. Planning Guide, Provides in-depth Planning and architecture for Windows SharePoint Services, Part 2 planning part 2 (http://go.microsoft.com/fwlink/?LinkId=85553) information for IT professionals who are designing the environment to host a solution based on Windows SharePoint Services 3.0. Deploy During the deployment stage, you configure your environment, install Windows SharePoint Services 3.0, and then start creating SharePoint sites. Depending on your environment and your solution, you may have several configuration steps to perform for your servers, for your Shared Services Providers, and for your sites. Additionally, you may have templates, features, or other custom elements to deploy into your environment. The process of upgrading from a previous-version product, such as Microsoft Office SharePoint Portal Server 2003, Microsoft Content Management Server 2002, or Windows SharePoint Services, is also part of the deployment stage of the IT life cycle. We have content that addresses planning for upgrade, performing the upgrade, and performing post-upgrade steps. The following table lists resources that are available to help you deploy or upgrade to Windows SharePoint Services 3.0. Content Description Links Page 13 of 146 Content Description Links Online content Includes the most Deployment for Windows SharePoint Services 3.0 up-to-date (http://go.microsoft.com/fwlink/?LinkID=80752&clcid=0x409) content. The Technical Library on TechNet is continually refreshed with new and updated content. Deployment Guide Provides in-depth Deployment for Windows SharePoint Services deployment (http://go.microsoft.com/fwlink/?LinkID=79602) information for Windows SharePoint Services 3.0. Upgrade Guide Provides overview Upgrading to Windows SharePoint Services 3.0 and in-depth (http://go.microsoft.com/fwlink/?LinkId=85554) information for upgrading from a previous version product to Windows SharePoint Services 3.0. Migration and Provides cross- Migration and Upgrade Information for SharePoint Upgrade for audience (IT and Developers SharePoint developer) Developers information for (http://go.microsoft.com/fwlink/?LinkId=89129&clcid=0x409) migration and upgrade from a previous version product to Windows SharePoint Services 3.0. Operate Page 14 of 146 After deployment, in which you install and configure your environment, you move to the operations stage. During this stage, you are focused on the day-to-day monitoring, maintenance, and tuning of your environment. The following table lists resources that are available to help with day-to-day operations for Windows SharePoint Services 3.0. Content Description Links Online content Includes the most Operations for Windows SharePoint Services 3.0 up-to-date (http://go.microsoft.com/fwlink/?LinkId=89152&clcid=0x409) content. The Technical Library on TechNet is continually refreshed with new and updated content. Security and Protection Because security and protection are concerns during all phases of the IT life cycle, appropriate content for security and protection is included in the content for each life cycle stage. However, an aggregate view of this content is provided in a Security and Protection section of the documentation. The following table lists resources that are available to help you understand security and protection for Windows SharePoint Services 3.0. Content Description Links Online content Includes the most Security and protection for Windows SharePoint Services 3.0 up-to-date (http://go.microsoft.com/fwlink/?LinkId=89154&clcid=0x409) content. The Technical Library on TechNet is continually refreshed with new and updated content. Technical Reference Page 15 of 146 Technical reference information supports the content for each of the IT life cycle stages by providing the technical information you need to work with Windows SharePoint Services 3.0. For example, the Technical Reference content has information about how permissions work, how to perform operations from the command line, and how to use Setup.exe from the command line. The following table lists resources that are available to help you work with Windows SharePoint Services 3.0. Content Description Links Online content Includes the most Technical Reference for Windows SharePoint Services 3.0 up-to-date (http://go.microsoft.com/fwlink/?LinkID=88902&clcid=0x409) content. The Technical Library on TechNet is continually refreshed with new and updated content. Solutions In addition to these IT life cycle-specific resources, we also offer several solution guides that help you plan, deploy, and operate a specific type of solution based on Windows SharePoint Services 3.0. For a current list of solution guides for Windows SharePoint Services 3.0, see Downloadable books for Windows SharePoint Services 3.0 (http://go.microsoft.com/fwlink/?LinkId=89165&clcid=0x409). Download this book This topic is included in the following downloadable book for easier reading and printing: Deployment for Windows SharePoint Services 3.0 technology Getting started with Windows SharePoint Services 3.0 See the full list of available books at Downloadable books for Windows SharePoint Services. Page 16 of 146 I. Plan and prepare for upgrade (*WSS*) Topic Last Modified: 2007-03-09 Insert introduction here. Subhead Insert section body here. Subhead Insert section body here. Page 17 of 146 Chapter overview: Plan and prepare for upgrade Topic Last Modified: 2009-03-10 The upgrade process is not as simple as inserting a CD and running Setup. You need to plan your approach carefully, anticipate any issues that might come up during or after the process, and consider your specific environment. This chapter includes information and recommendations that can help you plan and prepare for the upgrade process. In this chapter: Determine upgrade approach How the upgrade process works (Windows SharePoint Services) Review system requirements for upgrade (Windows SharePoint Services) Estimate how long the upgrade process will take and the amount of space needed (Windows SharePoint Services) Create communication plan (Windows SharePoint Services) Use a trial upgrade to find potential issues (Windows SharePoint Services) Determine how to handle customizations (Windows SharePoint Services) Develop new custom site definitions and create upgrade definition files (Windows SharePoint Services) In addition to these upgrade-specific planning steps, you should also follow the steps and recommendations for planning for security, capacity, and performance found in Planning and architecture for Windows SharePoint Services 3.0 technology. Download this book This topic is included in the following downloadable book for easier reading and printing: Upgrading Windows SharePoint Services See the full list of available books at Downloadable books for Windows SharePoint Services. Page 18 of 146 Determine upgrade approach Topic Last Modified: 2015-03-09 In this article: Choose an upgrade approach Special cases Page 19 of 146 Before you run any upgrade process, you need to determine which upgrade approach to take. Use the information in this article to help compare the pros and cons for each approach, and review information about special cases that might influence your approach. Choose an upgrade approach The following table lists and compares the different upgrade approaches. Approach Description Pros Cons Best for In-place upgrade Upgrades the Easiest approach. Environment is Single server or content and Sites retain original offline while it configuration data URLs. Updates runs. No ability to in-place, at one existing databases revert to original time. and servers using site. small server farm. existing hardware. Gradual upgrade Installs the new Enables a more More complex and Medium or large version side-by- granular approach: resource-intensive. server farms side with the You can upgrade Must redirect URLs (without shared previous version. at the site during upgrade services) with The server collection level. process, which many sites for administrator Reduces time any causes issues for which you must determines which single user is some client limit downtime. site collections to affected. Sites applications, such Good for when upgrade and when retain original as Microsoft Office. your environment to upgrade them. URLs. Can revert to Requires extra has many original site. Uses storage in SQL customizations. existing hardware. Server. Windows SharePoint Services 2.0 scalable hosting mode is not supported. Page 20 of 146 Approach Description (Advanced) Pros Cons Best for Requires the server Enables moving to Complex process Those who are Database administrator to new farm or new that requires many moving to new migration install the new hardware. manual steps and hardware or a new version on a Windows a higher risk of architecture. separate farm or SharePoint error. Requires Customers who separate hardware, Services 2.0 additional manual need to maximize and then manually environment is steps to retain upgrade migrate the available and is original URLs for throughput. This databases into the untouched by sites. Requires new approach is new environment. upgrade. server farm, and required for twice the amount Microsoft of SQL Server Windows storage space. SharePoint Services 2.0 environments that are using scalable hosting mode or Active Directory directory service account creation mode. For more information about how in-place and gradual upgrade work, see How the upgrade process works (Windows SharePoint Services). Special cases You might have other requirements or additional goals that you want to accomplish when you perform your upgrade. The following table lists special cases and describes which upgrade approach is appropriate for each case. Case Upgrade approach to take Page 21 of 146 Case Upgrade approach to take Changing languages? You have two choices, depending on whether a single site or your entire environment is changing languages: To change the language for a specific site, upgrade in the same language, and then install the new language pack and change to that language. Caution: You must have the appropriate language packs installed to upgrade any sites based on a localized site definition. If you do not have the new language pack, the sites will not be accessible. Wait for the new language packs to be released before attempting to upgrade those sites. Moving to Windows Server 2008? To change the installation language for your servers, use the database migration approach to migrate your data from the old version and language to the new version and language. First upgrade to Windows SharePoint Services 3.0 by using either in-place or gradual upgrade, and then upgrade to Windows Server 2008. Upgrading from SharePoint Team Services? Upgrade to Windows SharePoint Services 2.0, and then to Windows SharePoint Services 3.0. Upgrading directly from SharePoint Team Services is not supported. Upgrading from an environment that included the These components will continue to work in the Microsoft Office Web Components new version if you upgrade using in-place or (http://go.microsoft.com/fwlink/?LinkId=71517)? gradual upgrade. However, the database migration approach does not work for these components, because they can only be installed in a Windows SharePoint Services 2.0 environment. Download this book This topic is included in the following downloadable book for easier reading and printing: Page 22 of 146 Upgrading Windows SharePoint Services See the full list of available books at Downloadable books for Windows SharePoint Services. Page 23 of 146 How the upgrade process works (Windows SharePoint Services) Topic Last Modified: 2015-03-09 In this article: In-place upgrade Gradual upgrade How URL redirects are handled during gradual upgrade You can choose among three upgrade approaches: in-place, gradual, and database migration. An inplace upgrade is used to upgrade all Microsoft® SharePoint® sites at one time, which is best suited for single server or small deployments. A gradual upgrade allows finer control of the upgrade process by allowing one or more site collections to be upgraded at a time. Both in-place and gradual upgrades take place on the same hardware on which your previous version is installed. A database migration allows you to move your content to a new farm or new hardware. Tip: For larger deployments, a gradual upgrade is a better option than an in-place upgrade because it enables the administrator performing the upgrade to control how many site collections to upgrade at one time. In this way, large deployments can be upgraded gradually over several weekends while continuing to host the previous version sites. This is possible because you can continue to host the sites that have not yet been upgraded on the same server as the upgraded sites. In an in-place upgrade: The previous version is overwritten with the new version, and the content databases are changed. Because of this, an in-place upgrade is not a reversible process — that is, you cannot roll back to the previous version. The original sites are upgraded in place, and you cannot view the previous versions of the sites after upgrade. All sites are unavailable to site visitors during upgrade. The period during which the sites are unavailable is the full time it takes to upgrade the entire server or server farm. Site visitors continue to use the same URLs after upgrade. In a gradual upgrade: As each group of site collections is upgraded, the upgrade process copies the data in them from the original database to a new database before upgrading the data. The original data is maintained Page 24 of 146 in the original database until explicitly deleted by the server administrator. Because of this, upgraded sites can be easily rolled back to the previous version if necessary. Most sites are available to site visitors during the upgrade; only those site collections that are currently being upgraded are offline. (Note that the previous version sites are marked as updates only after they have been copied in preparation for upgrade.) The upgrade impact is limited to only those users who need the site or sites being upgraded. After upgrade, the original URLs point to the upgraded version of the sites. This way, users can continue to use the same URLs they used before the upgrade. A database migration is essentially an in-place upgrade that you perform on a copy of the content. In a database migration: You copy all databases except for the configuration database, and then add the databases to a new stand-alone or server farm installation. When you attach the databases to the new server farm, the upgrade process runs and upgrades the data in place. Important: Because of the downtime, and the risk that upgrade may take longer than expected or that some sites may need some rework after upgrade, it is critical that the server administrator communicate with site owners and users about what to expect during the process. For more information, see Create communication plan (Windows SharePoint Services). In-place upgrade An in-place upgrade takes place on the same hardware as your previous version installation. When you run an in-place upgrade, the process upgrades your entire installation in a pre-set sequence. The following steps explain what happens as the in-place upgrade process runs: 1. After performing all pre-upgrade steps, the server administrator installs Windows SharePoint Services 3.0 to the server running the previous version of Windows SharePoint Services and chooses In-place Upgrade. 2. The upgrade process runs and upgrades the configuration database and the Central Administration site. 3. The upgrade process runs on each virtual server and upgrades each site collection in that virtual server. 4. After all sites have been upgraded, the upgrade process ends. 5. Repeat the upgrade action on each server in a server farm environment. 6. The administrator confirms that upgrade is complete and then uninstalls the previous version of Windows SharePoint Services. Page 25 of 146 Gradual upgrade Similar to an in-place upgrade, a gradual upgrade takes place on the same hardware that is used for your previous version installation. However, a gradual upgrade allows you to control when upgrade takes place for each individual site collection, and it also allows you to continue running the previous version and the new version side by side on that hardware. When you perform a gradual upgrade, the starting and ending topologies have the same configuration, similar to an in-place upgrade except for the following differences: During and after upgrade, the front-end Web servers run both Windows SharePoint Services 2.0 and Windows SharePoint Services 3.0. Any upgraded site collections run under Windows SharePoint Services 3.0, whereas site collections that could not be upgraded or that were not selected for upgrade continue to run under Windows SharePoint Services 2.0. Note: Scenarios in which you may not want to upgrade sites include: you may need to keep some sites in the previous version until a needed language pack is available for Windows SharePoint Services 3.0, or you may need to wait for a new custom site definition to be created. During and after upgrade, both the Windows SharePoint Services 2.0 and the Windows SharePoint Services 3.0 databases are available. Content for upgraded sites is stored in the Windows SharePoint Services 3.0 databases; content for sites that could not be upgraded or that need to remain as they were continue to be stored in the Windows SharePoint Services 2.0 databases. Configuration databases exist for both Windows SharePoint Services 3.0 and Windows SharePoint Services 2.0. Page 26 of 146 The following figure illustrates the gradual upgrade process: The following steps correspond to the callout numbers in the preceding figure and explain what happens as the gradual upgrade process runs. 1. After performing all pre-upgrade steps, the server administrator installs Windows SharePoint Services 3.0 to the first front-end Web server in the farm and then chooses Gradual Upgrade. Page 27 of 146 Note: It is recommended that you back up your environment before running the upgrade. For more information, see Run and test a full backup in SQL Server (Windows SharePoint Services). 2. The upgrade process creates a Windows SharePoint Services 3.0 Web application to host SharePoint Central Administration, and the Central Administration site is created. 3. The upgrade process creates a new configuration database to store configuration data for Windows SharePoint Services 3.0. Configuration data from the Windows SharePoint Services 2.0 configuration database is copied into the new database. 4. The administrator selects a virtual server to upgrade and specifies the target Web application. The upgrade process creates the target Web application and adds any Web Parts deployed to the Windows SharePoint Services 2.0 virtual server to the new Web application. 5. The upgrade process creates a temporary content database for each content database that exists in the previous version. The upgrade process copies the site list from Windows SharePoint Services 2.0 into the new environment. The administrator selects the site collections to upgrade. The upgrade process copies the data for those sites into the temporary content database, and then upgrades those sites in that temporary content database. Each site is temporarily unavailable while being copied into the temporary content database. 6. After the content has been upgraded, the upgrade process moves the data to the Windows SharePoint Services 3.0 content database and then deletes the temporary content database. 7. At the end of the upgrade process, Windows SharePoint Services 2.0 and Windows SharePoint Services 3.0 are both running and available. After all sites have been upgraded, the administrator confirms that upgrade is complete. If Windows SharePoint Services 2.0 is no longer needed, the administrator uninstalls Windows SharePoint Services 2.0. How URL redirects are handled during gradual upgrade Two sites cannot share the same URL. Therefore, during a gradual upgrade, when you have both the old version and the new version of each site, you need two different domain URLs for each site (for example, http://company_name/sites/SiteA and http://company_name_old/sites/SiteA). During upgrade, a temporary domain URL is needed to host the original previous version sites. The new version takes over the domain URL that points to the content prior to upgrade, and user requests will be routed to their content whether or not it has been upgraded. The following process occurs during upgrade to make this redirection possible: 1. Before you begin the upgrade, create a temporary URL domain for your previous version sites. 2. When you run the upgrade, the upgrade process will ask you for the domain you specified above. The process moves the previous version site to the temporary URL domain, and the new version site takes over the original URL domain. Page 28 of 146 3. A redirect is created automatically for each site collection to send requests for the original URL to the old site until the site is upgraded. 4. After each site has been upgraded, the redirect for that site is dropped. 5. After all sites have been upgraded, and after you have deleted all of the old sites and completed the upgrade process, you can manually remove the temporary URL domain from the Domain Name System (DNS). Page 29 of 146 During this process, browse access to the original URL always works. However, certain client applications (such as Microsoft Office client applications) cannot use these types of redirects. Before a site is upgraded, the original URL points to the previous version; after a site has been upgraded, the original URL points to the new version. The following table illustrates how the URLs work during gradual upgrade. Stage Original site URL Upgraded site URL Notes Before upgrade http://company_name n/a The server administrator creates /sites/SiteA http://company_name_old for use during gradual upgrade. During upgrade http://company_name_old http://company_name Requests for /sites/SiteA http://company_name/sites /sites/SiteA /SiteA are redirected to http://company_name_old /sites/SiteA until it is upgraded. After upgrade http://company_name_old http://company_name The redirect is removed /sites/SiteA (until deleted) /sites/SiteA after upgrade is complete and the results are validated. Be aware that this URL redirection can cause hard-coded links within sites or documents to break. For example, Microsoft Office InfoPath® forms sometimes contain hard-coded links to a data location (such as a specific SharePoint list, Web service, or XML file). Because the link is hard-coded, it cannot be automatically updated to point to the temporary URL used for sites that have not yet been upgraded during a gradual upgrade. Use a trial upgrade to identify such issues before you begin your official upgrade process. That way, you can identify any sites that need to be upgraded quickly so that they can use the original URL again, and you can avoid the support calls that result from loss of functionality in forms or other items containing hard-coded links. Download this book This topic is included in the following downloadable book for easier reading and printing: Upgrading Windows SharePoint Services See the full list of available books at Downloadable books for Windows SharePoint Services. Page 30 of 146 Review system requirements for upgrade (Windows SharePoint Services) Topic Last Modified: 2015-03-09 In this article: Stand-alone installation Server farm installation Worksheet Page 31 of 146 Not only do you need to meet the system requirements to run the new version, but your system must have the appropriate processor power and memory to run the upgrade process. Before you begin the upgrade process, make sure your system meets the recommendations below for your servers. Caution: It is important that your hardware meets these recommendations; otherwise, you may run into issues during the upgrade process. For example, if your database server does not have enough memory or processor power, it may not be able to keep up with the number of transactions that occur during the upgrade process, and the upgrade may fail with an error and a comment in the upgrade log. The Upgrade.log file is located at %COMMONPROGRAMFILES%\Microsoft Shared\web server extensions\12\LOGS. If you experience problems with your hardware capacity, you can increase the capacity, and then try running the upgrade again by using the following command on the command line: stsadm -o upgrade For more information about running upgrade from the command line, see Upgrade sites (Windows SharePoint Services). For more information about system requirements, see Determine hardware and software requirements (Windows SharePoint Services) in the Planning Guide. To learn about the process of mapping your solution design to a farm size and set of hardware that will support your business goals, see Plan for performance and capacity (Windows SharePoint Services). Important: It is important to track the three resource components for a server running SQL Server: CPU, memory, and I/O subsystem. When one or more of the components seem at capacity, analyze the appropriate course of action based on the current and projected work load, and determine whether to add more resources or to scale out to a new server running SQL Server. In general, we recommend that you consider scaling out, in addition to adding more resources. We recommend that you deploy an additional server running SQL Server when you have more than four fully loaded, front-end Web servers. Stand-alone installation You can install Windows SharePoint Services 3.0 on a single computer by either choosing Basic, or choosing Advanced and then selecting Stand-alone in Windows SharePoint Services 3.0 Setup. Hardware requirements The following table lists the minimum and recommended hardware requirements for deploying Windows SharePoint Services 3.0, including the deployment of Windows Internal Database, for a standalone installation. Page 32 of 146 Component Minimum Recommended Processor 2.5 gigahertz (GHz) Dual processors that are each 3 GHz or faster RAM 1 gigabyte (GB) 2 GB Disk NTFS file system–formatted NTFS file system–formatted partition with a minimum of 3 GB partition with 3 GB of free space of free space plus adequate free space for your Web sites Drive DVD drive DVD drive or the source copied to a local or network-accessible drive Display 1024x768 1024x768 or higher resolution monitor Network 56 kilobits per second (Kbps) 56 Kbps or faster connection connection between client between client computers and computers and server server Server farm installation The primary difference between a single server and a server farm topology is that you can use one or more computers to host the following server roles: Front-end Web server Database server Page 33 of 146 This section details the minimum and recommended system requirements for each server role. If you install more than one role onto a single computer, ensure that the computer meets the minimum requirements for both roles. Front-end Web server The following table lists the minimum and recommended hardware requirements for deploying a Windows SharePoint Services 3.0 front-end Web server. Component Minimum Recommended Processor 2.5 GHz Dual processors that are each 3 GHz or faster RAM 2 GB More than 2 GB Disk NTFS file system–formatted NTFS file system–formatted partition with a minimum of 3 GB partition with 3 GB of free space of free space plus adequate free space for your data storage requirements Drive DVD drive DVD drive or the source copied to a local or network-accessible drive Display 1024x768 1024x768 or higher resolution monitor Network 56 Kbps connection between client computers and server For connections between computers in your server farm, 100 megabits per second (Mbps) connection 56 Kbps or faster connection between client computers and server For connections between computers in your server farm, 1 gigabit per second (Gbps) connection Worksheet Use the Upgrade server requirements worksheet (http://go.microsoft.com/fwlink/?LinkId=76765&clcid=0x409) to determine if you need to increase your server capacity before upgrade. Page 34 of 146 Estimate how long the upgrade process will take and the amount of space needed (Windows SharePoint Services) Topic Last Modified: 2016-05-08 In this article: Estimate the amount of space needed for the upgrade Estimate how long the upgrade will take Related worksheet Page 35 of 146 Every environment is unique and includes different hardware capabilities and different site characteristics. The amount of space and the length of time needed to run an upgrade will vary greatly depending on your environment. The best way to estimate how much space will be needed and how long the upgrade process will take is to perform a trial upgrade pass, and then review the sizes and times. For more information about performing a trial upgrade, see Use a trial upgrade to find potential issues (Windows SharePoint Services). Estimate the amount of space needed for the upgrade Depending on the upgrade approach you choose, you will need different amounts of available disk space to perform your upgrade. With the in-place upgrade and database migration approaches, you need to plan for very little expansion in the databases; however, there are a lot of transactions taking place while the upgrade process runs, and so the log files will need to expand to accommodate the changes that are occurring. With a gradual upgrade, you must have space for three sets of databases: the original databases, the temporary databases where the upgrade process takes place, and the upgraded databases. In addition, you need space for the log files and additional search indexes (if needed). For key recommendations and best practices to help you plan and monitor your SQL Server storage requirements to support optimal performance and operation of your server farms, see Planning and Monitoring SQL Server Storage for Windows SharePoint Services: Performance Recommendations and Best Practices (white paper). Estimate space for an in-place upgrade or a database migration For an in-place upgrade or a database migration, you do not need to plan for a lot of extra database space. For a content database migration, you simply need to plan on having as much space available on the new hardware as is required for your current databases, plus room to expand over time. To find out how large your databases currently are, use Enterprise Manager in Microsoft SQL Server. In addition to database space, you also need to have room for the following items: The temporary databases. Ensure that you have enough database space to enable quick growth of the temporary databases. If you do not have enough space, the upgrade process might time out and the upgrade will fail. The upgrade log files. The transaction log files for the databases. These log files must grow quickly to accommodate the number of changes taking place in the databases; be sure that you have enough disk space for these log files. Note: In very large environments, there is a possibility that the default growth rate for the transaction log files (10%) is not enough to keep up with the upgrade process; this can cause a timeout. Again, a trial upgrade is the best way to determine if the transaction log files can keep up with the upgrade process. If your environment is very large, or if the Page 36 of 146 process timed out during a trial upgrade, consider pre-growing the SQL Server transaction log files to be sure you have room for the number of transactions that need to be processed. For more information about pre-growing the SQL Server transaction logs, see the "Expanding a Database" topic in the SQL Server 2000 or 2005 documentation. Estimate space for a gradual upgrade If you are following a gradual upgrade path, you need to have enough database space to accommodate an amount of data approximately three times the size of your largest site collection. To find out how large your databases currently are, use Enterprise Manager in SQL Server. If you cannot afford to allocate this much disk space, you can reduce this overhead by upgrading sites in batches. After you have upgraded a few batches and confirmed with the sites' owners that the old versions are no longer needed, you can start cleaning up and deleting the previous version sites (after taking a backup). If you continue in this way, upgrading new batches and deleting sites from the old version, you can regulate the amount of space needed. In addition to database space, you also need to have room for the following items: The upgrade log files. The transaction log files for the databases. These log files must grow quickly to accommodate the number of changes taking place in the databases; be sure that you have enough disk space for these log files. Page 37 of 146 Note: In very large environments, there is a possibility that the default growth rate for the transaction log files (10%) is not enough to keep up with the upgrade process; this can cause a timeout. Again, a trial upgrade is the best way to determine if the transaction log files can keep up with the upgrade process. If your environment is very large, or if the process timed out during a trial upgrade, consider pre-growing the SQL Server transaction log files to be sure you have room for the number of transactions that need to be processed. For more information about pre-growing the SQL Server transaction logs, see the "Expanding a Database" topic in the SQL Server 2000 or 2005 documentation. For more information about how disk space is used during a gradual upgrade, see How the upgrade process works (Windows SharePoint Services). Estimate how long the upgrade will take With your disk space estimates in hand, you can now calculate a rough estimate of how long the actual upgrade process will take. Upgrade times vary widely among environments. The performance for an upgrade depends greatly on the hardware being used, the complexity of the sites, and the particular characteristics of your implementation. For example, if you have a lot of large document libraries, these may take longer to upgrade than a simpler site. The upgrade approach you've chosen will also make a big difference in how long the process will take. Upgrading by way of a database migration is the quickest method (keep in mind, however, that the preupgrade and post-upgrade steps for this approach take much longer than other approaches). A gradual upgrade is the slowest method because of the extra data copying steps involved. An in-place upgrade falls somewhere in between. The best way to estimate overall time is to do a trial upgrade of a small portion of the data, and then review the upgrade log files. You can also use the log files to check your progress during the upgrade process. The upgrade.log file located at %COMMONPROGRAMFILES%\Microsoft Shared\web server extensions\12\LOGS contains the duration. However, the estimate you arrive at based on your data set is for the actual upgrade process for the data; it does not include all of the steps you have to perform before and after this step, which can take more time than the upgrade of the data itself. When estimating how long the upgrade will take, in addition to the data processing, you must also estimate how long the activities during the pre-upgrade and post-upgrade phases will take. Pre-upgrade steps: Creating custom elements Creating a site definition or new page layouts, or upgrading Web Parts, will take some time. The process of creating custom elements should begin early, during the evaluation phase of your project. Backing up the databases You must perform a full backup — not a differential backup — to be sure you can recover in the remote possibility that the upgrade fails and you need to rebuild your Page 38 of 146 server farm. For large environments, this step can take a significant amount of time. In particular, if you are backing up to a network location, network latency issues can slow this process down. Creating new Domain Name System (DNS) names for a gradual upgrade The Domain Name System will take time to propagate changes across the network. For more information about precreating the DNS names for a gradual upgrade, see Create new domain names (gradual upgrade only) (Windows SharePoint Services). Post-upgrade steps: Verifying sites and making changes or reverting to template Allow enough time for users to validate their sites after the upgrade. This may take several days. For more information, see Review upgraded sites (Windows SharePoint Services). Additional factors in your environment can also contribute to longer upgrade times, including: Very large document libraries A document library with more than 250,000 documents all in the root of the document library (rather than in folders) will take a long time to upgrade, and the upgrade might not be successful. Following the 2.0 guidelines for using folders to break up large document libraries can help you manage the library size. For example, if you rearrange the same document library so that the 250,000 documents are divided into 125 folders, it should upgrade more easily. Very large databases Databases larger than 100 GB can take a long time to upgrade. If your databases are larger than that, it is recommended that you divide them up into smaller databases before running the upgrade. Larger databases not only take longer to upgrade, but they can make it harder to recover if the upgrade does not complete successfully. There are community-supported tools available to move site collections between databases. Page 39 of 146 Caution: If you have a very large database (more than 100 GB) that you cannot break up (because the majority of content is in a single site collection), you may also want to reconsider your upgrade approach. A gradual upgrade approach can handle somewhat larger databases because, with a gradual approach, you can upgrade site collections individually. A database migration approach is more difficult with very large databases, simply because backing up and restoring such large databases is problematic. Of course, a gradual approach requires more space, so you need to consider your options carefully. For more information about using database migration to upgrade sites after finalizing a gradual upgrade, see article 926718, How to attach a content database backup during a gradual upgrade of a Windows SharePoint Services 2.0 farm to Windows SharePoint Services 3.0 in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkId=113886&clcid=0x409). Be sure you are following the capacity planning guidelines from the old and new versions before you attempt the upgrade. If you have exceeded the guidelines for best performance, the upgrade process might take longer, or it might not succeed (for example, the process might time out repeatedly on the same large document library). If your deployment does not meet the recommended capacity guidelines, consider whether you need to do some work to meet those guidelines before attempting the upgrade. Again, a trial upgrade can help you with that decision. Worksheet Use the Estimate database space and time for upgrade worksheet (http://go.microsoft.com/fwlink/?LinkID=798133&clcid=0x409) to determine how much disk space you need to perform the upgrade and how long the upgrade process might take. Page 40 of 146 Create communication plan (Windows SharePoint Services) Topic Last Modified: 2007-12-13 In this article: When and what to communicate to the upgrade team When and what to communicate with site users For small deployments in which sites have not been customized to any great degree, the upgrade team might consist of only one person. For larger deployments, on the other hand, several people with different roles can be required, as shown in the following list. Server administrators The server administrator performs most of the upgrade tasks. There must be at least one server administrator on the upgrade team because running the Setup wizard requires someone who is a member of the local Administrators group on each front-end Web server. Note: Farm administrators might or might not be local administrators for the server. Site collection owners You need to be able to notify site collection owners that the upgrade process is about to happen, and alert them to any issues you find when you upgrade their sites. If you are performing a gradual upgrade, you must also communicate with site collection owners to determine whether their sites have been completely upgraded and any customizations re-applied before you delete or deactivate the old sites. Site designers and developers If you have custom templates, Web Parts, Web services, or other custom elements associated with your sites, you need to work with the people responsible for developing or customizing those elements to ensure that you can create new versions of these custom elements, or to verify that these elements have upgraded correctly. For more information about potential issues with custom elements, see Use a trial upgrade to find potential issues (Windows SharePoint Services). Site users Although site users won't need to be included in making decisions about the upgrade process, you need to tell site users when it will take place and what they should expect. Sponsors and other stakeholders You might have other people in your organization involved in the upgrade planning process. Be sure to include them in your communication plan appropriately. Page 41 of 146 Note: An upgrade team can include one or more members in each role depending upon your organization. When and what to communicate to the upgrade team In general, the server administrators set the timeline for upgrade, and site owners are notified only when the process is about to begin. However, because team members have their own tasks to perform at particular points in the overall upgrade process, it is critical that you have a solid plan to communicate the progress of the upgrade to all team members so that everyone knows when it is time to perform their particular tasks. The entire upgrade team needs to work together to determine: The upgrade approach to use The Determine upgrade approach topic provides information to help you decide which type of upgrade to perform. The report generated by the pre-upgrade scan tool is also important to take into consideration when making this decision. Dates and times to perform the upgrade We recommend (particularly for an in-place upgrade) that you upgrade when site usage is low. For small single-server deployments, upgrade may complete in less than a day. For larger deployments, such as server farms with large amounts of data, the gradual upgrade option can be used to distribute the upgrade process over several outage windows. There is no way to determine the exact amount of time required to upgrade any particular site collection. Because of this, it is very important to communicate with other team members involved in the upgrade process as well as end users. The day or days that you choose for upgrading should be far enough in the future to enable the upgrade team time to complete all of the preliminary steps. When planning the timeline, be sure to schedule time to validate the upgraded sites and time to implement any changes or do any work to re-brand sites. It is important to communicate with site owners, designers, and developers at the following points during the upgrade process: Before the process begins, so that they know the general timeline and what their roles in the process will be. After the pre-upgrade scan tool has been run, so that they can address any issues identified by the tool. For more information about the pre-upgrade scan tool, see Run the pre-upgrade scan tool (Windows SharePoint Services). For example, issues such as customized site templates or custom Web Parts should be reported to the appropriate site owner, designer, or developer before scheduling the upgrade to give them time to investigate the issues and take preliminary steps. For example, a developer might decide that it is prudent to rebuild a Web Part before the upgrade occurs. And site owners might want to make note of any customizations that have been done to their sites, including site templates and changes to core Active Server Page Extension (ASPX) files. After their sites have been upgraded, so that they can review the sites and make any changes necessary. Site owners need to know how long the old versions of the sites will be maintained so that they can be sure to retrieve anything they need from the old site. Page 42 of 146 When and what to communicate with site users It is equally important to communicate with the users of the sites to tell them about the following issues: When their sites will be upgraded In the case of an in-place upgrade, they must also be informed that their sites will be unavailable during the upgrade. When to expect their upgraded sites to be ready This means that the upgrade team has not only upgraded but also verified the functionality of the upgraded sites. How the upgrade might impact them and what they should know about the new environment For example, the site might look different or function slightly differently. Or they may need to reapply customizations from the old site after upgrade. You can also point them to available content, such as What's New articles or training materials, to learn about the new version. Download this book This topic is included in the following downloadable book for easier reading and printing: Upgrading Windows SharePoint Services See the full list of available books at Downloadable books for Windows SharePoint Services. Page 43 of 146 Use a trial upgrade to find potential issues (Windows SharePoint Services) Topic Last Modified: 2015-03-09 Before you begin the upgrade process, you'll want to know approximately how long it will take, how many customizations will have to be done again or reapplied, and which sites may not upgrade as expected. The following method will help you determine what issues you may run into during the upgrade process, so you can address them before or after upgrade as appropriate. 1. Run the pre-upgrade scan tool to find any custom sites or unghosted pages (required). Note: You must run the pre-upgrade scan tool before starting the upgrade process. This tool steps through each site collection and generates a report about the state of each site. It also saves list definition information for each list. You can review the reports to find issues and address them before you start the upgrade process. This scan must be run before you can upgrade; the SharePoint Products and Technologies Configuration Wizard will not run if this scan has not been performed. For more information about this tool and steps for running the scan, see Run the pre-upgrade scan tool (Windows SharePoint Services). 2. Review common issues to see which issues may apply to your environment. This list gives you a quick look at some common issues you may run across, and how to address them either before or after performing the upgrade. 3. Perform a trial upgrade by using a backup or mirrored (read-only) site (recommended, but optional). This is the best method for discovering issues. You can preview the entire upgrade process and find any issues and address them before you start (or at least know what to expect). This method does require extra time and hardware; however, if you do invest in a trial run, you'll have a much easier time during the real upgrade process. 4. Test custom Web Parts. You can test your Web Parts based on Windows SharePoint Services 2.0 to see if they'll keep working when you upgrade. Review common issues When you run the pre-upgrade scan tool or a test upgrade pass, you may notice one or more of the following common issues in your sites. If you have several sites with these issues, it is recommended that you perform a gradual upgrade. With a gradual upgrade, you have both the old version and the Page 44 of 146 new version of any affected sites available, and you can revert to the old sites or make updates to the new sites before making the new versions live. If you must run upgrade in place, be sure to take a backup of your sites before running the upgrade. Issue Explanation and what to do I do not know what has been customized. The most time-consuming step in the upgrade process may be to identify existing customizations and then decide which customizations to upgrade, migrate, and discard; and then map those customizations to Office SharePoint Server 2007. Use WinDiff, a tool that is provided with most Microsoft operating systems, to compare the original (default) site definition files to current (custom) site definition files to identify customizations. For more information, see Areas, Bucketwebs, Upgrade and Redirects (http://go.microsoft.com/fwlink/?LinkId=139912). The local server and server farm administrators In the new release, local server and server farm cannot browse to the sites. administrators are not automatically granted access to site content. If you want these users to have access to all site content, you can use the Web application policy to grant these users access to all sites. For more information about policy, see "Policy for Web applications" in the Logical architecture components (Windows SharePoint Services) article. My branding customizations are lost during The methods to use for branding your site have upgrade. changed in the new version. For example, you can now use Master Pages to control the layout and structure of your pages. Reapply branding by using the new methods. My themes are lost during upgrade. Themes have been reworked and redesigned for the new version. Apply a new theme. Customizations done in a Web page editor Revert the pages to template to get the latest compatible with Windows SharePoint Services functionality, then reapply customizations in a such as Microsoft® Office FrontPage® 2003, are Web page editor compatible with Windows retained (my pages are still unghosted), but new SharePoint Services 3.0 such as Microsoft Office functionality does not appear in the site. SharePoint Designer 2007. Page 45 of 146 Issue Explanation and what to do Hard-coded URLs in Web Parts and pages that The URLs for certain pages may have changed pointed to specific places in my sites no longer during upgrade (for example, if you had some work. areas with the /C2/ or /C16/ paths, then those paths may have been updated to /sites/ instead). Navigate to the appropriate location, and then recreate the URLs to point to the new location. My sites are based on a heavily customized site Before upgrading your sites, create a new site definition. definition, and then create an upgrade definition file so the upgrade process can map your old site definition elements to the new site definition. I had extended form libraries and they no longer Support for forms has been changed from form work. libraries to document libraries. Redeploy and reapply the forms to new document libraries. We started the gradual upgrade process, and now Some InfoPath forms contain hard-coded links to a my forms do not work. data location (such as a specific SharePoint list, Web service, or XML file). Because the link is hardcoded, it cannot be fixed automatically to point to the temporary URL that is used for sites that have not yet been upgraded during gradual upgrade. To fix the forms, you can immediately upgrade the sites that contain forms with broken links (thus restoring the original URL). If you cannot upgrade the sites immediately (for example, if there are other issues with the site that you need to investigate before upgrading), you can republish the forms and point to the temporary URL domain. Note that, if you choose to republish the forms, you'll have to republish the forms again after you upgrade the sites to point to the original URL, so use this option sparingly. For more information about the temporary URLs used during gradual upgrade, see How the upgrade process works (Windows SharePoint Services). I had custom message text for Alerts and it is no The custom messages are preserved, but you must longer displayed. manually transfer the message file to the new path. I had custom event handlers configured for my You may need to reapply the event handlers, or environment. use new features to perform the tasks instead. Page 46 of 146 Issue Explanation and what to do Some controls that I rely on have been deprecated. Remove the references to the controls from your new site definition. For more information about deprecated controls and which controls or features to use instead, see the Windows SharePoint Services 3.0 Software Development Kit (SDK). My Web Parts were obfuscated in the old version, You may need to rebuild the Web Parts with and now they do not work in the new version. ASP.NET 2.0. My custom Web services relied on hard-coded You may need to rework the Web services to use URLs or functionality that has changed. the new URL schemes and new functionality. For more information, see the Windows SharePoint Services 3.0 Software Development Kit (SDK). Some files (with extensions .asmx, .rem, .resx, These file extensions have been added to the list .soap, or .ashx) are no longer visible or cannot be of blocked file extensions for the new version. If opened after upgrade. you need to allow users to upload or download files with these extensions, you can remove the entries for these extensions from the list. For more information about managing blocked file extensions, see the topic Manage blocked file types in the Windows SharePoint Services 3.0 Central Administration Help system. I don't see a Link to Outlook button on View pages You must revert the page to the template version anymore. to get the new user interface controls on the View pages, such as this control. I can't revert a custom page to template. If you added a completely custom page to your site (for example, if you replaced default.aspx with a completely different file rather than making changes to the existing default.aspx file), that page has no association with the site definition and so cannot revert to template. If you want your custom page to have the same look and feel as the other pages in your site, consider creating a new page based on the site definition and transferring your customizations to that new page. Perform a trial upgrade Page 47 of 146 If you have the resources available, it is recommended that you perform a trial upgrade to discover any issues before you perform the actual upgrade. You can perform this trial upgrade on either a backup or a mirrored version of your site. To perform a trial upgrade on a backup version of your environment: 1. Take a full backup of your server or server farm. 2. Restore the backup on separate hardware, and configure that environment so it is identical to your product environment (for example, install any custom Web Parts, custom binaries, site definitions, and so on). 3. Perform the pre-upgrade, upgrade, and post-upgrade steps for the upgrade path you will use in your live environment. 4. Review the results and look for issues that you can address before performing the upgrade in your live environment. To perform a trial upgrade on a mirrored (read-only) version of your environment: 1. In the mirrored environment, perform the pre-upgrade, upgrade, and post-upgrade steps for the upgrade path you will use in your live environment. 2. Review the results and look for issues that you can address before performing the upgrade in your live environment. Test custom Web Parts Because Windows SharePoint Services 2.0, Service Pack 2 (SP2), supports running ASP.NET 2.0 on the same Internet Information System (IIS) Web site (also known as virtual server or Web application in the new terminology), you can install and enable ASP.NET 2.0 on your virtual servers running Windows SharePoint Services 2.0 and verify that your Web Parts are going to work in the new environment. To test your Web Parts, do either of the following: Download and install ASP.NET 2.0 and .NET Framework 2.0 to a front-end Web server in your farm or to your stand-alone server. Then, in IIS, enable ASP.NET 2.0 for any IIS Web sites that are hosting SharePoint sites and review the Web Parts in your sites. In a development environment, download, install, and enable ASP.NET 2.0 and .NET Framework 2.0; copy your Web Parts over; and review them to see if they still work. Download this book This topic is included in the following downloadable book for easier reading and printing: Upgrading Windows SharePoint Services See the full list of available books at Downloadable books for Windows SharePoint Services. Page 48 of 146 Determine how to handle customizations (Windows SharePoint Services) Topic Last Modified: 2016-05-08 If you have extensively customized your previous-version sites (by using a Web page editor compatible with Microsoft Windows SharePoint Services 2.0, such as Microsoft Office FrontPage 2003), you need to determine how you want to handle your customized sites when you upgrade. Your approach will vary based on the extent of the customizations, the complexity of your site, and your goals for upgrading. You can choose to: 1. Keep the customizations While this approach allows you to keep the same look and feel, you won't be able to take advantage of the new capabilities available in the new version. If you really want to keep your pages looking just as they did, there are three ways to keep the customizations: Do an in-place upgrade. By default, an in-place upgrade preserves customizations and does not reset to the site definition. Some controls, such as the Site Actions menu, may not be available in your upgraded site. Do a gradual upgrade, and keep the site in the previous-version environment (do not upgrade the site). This maintains the site exactly as it is, with the previous-version functionality only. This is usually a short-term solution, as most organizations do not want to support both versions over the long term. Do a gradual upgrade and upgrade the site, but don't reset any pages to the site definition. This approach might result in an uneven look if you didn't customize every page. Customized pages retain the previous version's look and functionality, while uncustomized pages have the new version's look and functionality. Some controls, such as the Site Actions menu, may not be available in your customized pages. Note: By default, custom pages are kept as is after an upgrade (except for themes). 2. Replace the customizations If you are planning a complete site redesign, or if you are significantly changing the information architecture, then the upgrade is your chance to start over with a new look or a new organization. There are two ways to replace your customizations and start with a new site: Go ahead and upgrade (either in-place or gradual), and reset all pages to use the default pages from the site definition. Page 49 of 146 With this approach, you can start with the new look and functionality, and then decide whether or not to customize the site again. Site owners can reapply customizations when they review the upgraded sites. Note: If you have added a completely custom page to your site (for example, if you replaced Default.aspx with a completely different file rather than making changes to the existing Default.aspx file), that page has no association with the site definition and therefore it cannot be reset to the site definition. If you want your custom page to have the same look and feel as the other pages in your site, consider creating a new page based on the site definition and transferring your content to that new page. Start with a new site in the new environment. This approach works when you're dramatically redesigning your site and do not need to have either the structure or most of the content in the new site. Create a brand-new site, create a new site design, and transfer your content into the new site. This is not an upgrade path, but rather an opportunity to design your new site from start to finish. 3. Redo the customizations This approach allows you to take advantage of the new capabilities, modify your design slightly if desired, and move to a more manageable design. You can take advantage of the new Master Pages model to apply your design, rather than customize each individual page. There are three ways to redo the customizations: Do an in-place or gradual upgrade and do not reset the pages to the site definition version. After the upgrade, modify the appropriate master pages of the upgraded site to take on the previous version's look and feel, and then reset all customized pages to the site definition. This gives all formerly customized pages the same look as the un-upgraded site. You can incorporate the new controls, such as the Site Actions menu, into your new master page as part of this work. Do an in-place upgrade and do not reset the pages to the site definition. After the upgrade, open the site and copy the customizations, and then reset to the site definition and reapply your customizations to the master pages as appropriate. By default, an in-place upgrade preserves customizations and does not reset the pages to the site definition version. When you open the site by using a Web page editor that is compatible with Windows SharePoint Services 3.0, such as Office SharePoint Designer 2007, you can copy the customizations and then reset the original pages to get the new functionality. Then you can reapply any applicable customizations to the master pages. Following this process with an in-place upgrade is somewhat complicated, because you need to copy the customized pages before resetting them. Consider using the gradual upgrade method below instead. Note: When you perform an in-place upgrade, it does not preserve the previous version of the site. If you want to be able to have the previous version and the new version of the site side by side, so you can transfer customizations from the previous-version site to the new-version site, use a Page 50 of 146 gradual upgrade — or, if you are performing an in-place upgrade, be sure you have a mirrored server or server farm that is running the previous version. Do a gradual upgrade and, in the upgraded site, reset the customized pages to the site definition pages. Then transfer the customizations from your original site to the master pages in the upgraded site by using a Web page editor compatible with Windows SharePoint Services such as Office SharePoint Designer 2007. This option provides you with the most flexibility. Because you can refer to the original site, you can see exactly how you did the previous customizations. And because you reset to the site definition, you can see the new functionality and decide which customizations to reapply to the master pages and page layouts and which to ignore. Note: Again, not all custom pages have an equivalent page in the site definition, so resetting to the site definition will not work for truly custom pages. If you want your custom pages to have the same look and feel as the other pages in your site, consider creating a new page based on the site definition and transferring your content to that new page. Carefully monitor your use of customizations and Web Parts Deploy only those customizations that follow the best practices described in the following papers: Best Practices: Using Disposable Windows SharePoint Services Objects (http://go.microsoft.com/fwlink/?LinkId=105945&clcid=0x409). Development Tools and Techniques for Working with Code in Windows SharePoint Services 3.0 (Part 1 of 2) (http://go.microsoft.com/fwlink/?LinkID=101494&clcid=0x409). Best Practices: Common Coding Issues When Using the SharePoint Object Model (http://go.microsoft.com/fwlink/?LinkId=105946&clcid=0x409). SharePoint Products and Technologies customization policy (http://go.microsoft.com/fwlink/?LinkId=105947&clcid=0x409). Also, monitor Web Parts and page-rendering times. The Colleagues Web Part can be processing intensive. Do not use it on pages that render a lot of other information. Worksheet Record any customized site definitions or page templates you are using in the Custom templates and mapping files worksheet (http://go.microsoft.com/fwlink/?LinkId=798133&clcid=0x409). Page 51 of 146 Develop new custom site definitions and create upgrade definition files (Windows SharePoint Services) Topic Last Modified: 2008-02-11 In this article: Before you develop new custom site definitions Develop new custom site definitions About upgrade definition files Create upgrade definition files Record upgrade definition file information on a worksheet Before you develop new custom site definitions Before you upgrade sites based on custom site definitions, you must take the following steps to ensure that each list and page that is derived from your custom site definitions will continue working after upgrade. Note: If you are not yet ready to upgrade the sites based on a custom site definition (for example, if you obtained the site definition from a solution provider and a new version of that site definition is not yet available), you can use a gradual upgrade to upgrade other sites, and leave the sites based on the previous custom site definition running in the previous environment. Later, when you have a new custom site definition, you can create the upgrade definition file and upgrade only the sites that are based on the new custom site definition. 1. Obtain or develop new custom site definitions and custom elements If you want to retain the functionality of sites that are based on a custom site definition, you need a new custom site definition that includes all of the functionality you need, plus any of the new capabilities you want to use. If you obtained a custom site definition or custom elements from a solution provider, check to see if the provider has a new version. If your solution provider does not provide a new version, you might need to develop your own. 2. Create a site upgrade definition file You also need to create a file that maps the custom elements from your old custom site definition to the new custom site definition, so that each element in your site (for example, a custom page) can upgrade to the appropriate new element. Page 52 of 146 During the pre-upgrade process, you copy the new custom site definition and any upgrade definition files to the installation directory so that they are available when you upgrade the site collections. Develop new custom site definitions Use this process to create custom site definitions in a development environment. For more information, see the Windows SharePoint Services Software Development Kit (SDK) on MSDN. 1. Create custom site definitions by starting from a site definition provided with the new environment. Site definitions are stored in the following folder: %COMMONPROGRAMFILES%\Microsoft Shared\web server extensions\12\TEMPLATE\SiteTemplates\NAME Where NAME matches the site definition name (for example, ACTION). Create a folder for your new site definition, and name the new folder using all uppercase letters. The XML files used to register the site templates are stored in the following location: %COMMONPROGRAMFILES%\Microsoft Shared\web server extensions\12\TEMPLATE\LCID\XML\webtempname.xml Where name matches the site definition name, except that it is in lowercase letters, (for example, action), and where LCID is the locale identifier for the language of the template, (for example, 1033 for United States English). 2. Test your site definitions in the development environment by creating a new site based on the site definition. After you have created and tested your new site definitions, you can create the upgrade definition files that map your previous site definitions to the new site definitions. About upgrade definition files A site upgrade definition file describes how to map a previous custom site definition to a new site definition. The goal of a site upgrade definition file is to give developers a tool to transform their previous sites into new equivalents that take advantage of all the improvements the new environment has to offer. An upgrade definition file for a site definition has the following sections: WebTemplate Specifies upgrade information for the Web template as a whole. In this section, you need one WebTemplate tag per upgrade definition file. Lists Specifies upgrade information for each list or library in the template. In the Lists section, you need one List tag per list or library. Files Specifies upgrade information for the individual pages in the template. In the Files section, you need one File tag for each ghosted (uncustomized) page in the template. Page 53 of 146 AppliedSiteFeature Specifies upgrade information for any site collection-level or subsite-level features included in the template. In the AppliedSiteFeature and AppliedWebFeature sections, you need one Feature tag for each feature at that level in the template. AppliedWebFeature Specifies upgrade information for any subsite-level features included in the template. In the AppliedWebFeature section, you need one Feature tag for each feature at that level in the template. Create upgrade definition files Give the upgrade definition file a unique name that begins with the name of the site definition. For example, for a site definition named "STS1," name the upgrade definition file "STS1_upgrade.xml." Upgrade definition files must be installed in the following folder: %COMMONPROGRAMFILES%\Microsoft Shared\web server extensions\12\Config\Upgrade For more information about creating upgrade definition files, including a sample upgrade definition file, see the Upgrade Definition Files (http://go.microsoft.com/fwlink/?LinkId=109945&clcid=0x409) and Upgrade Definition Schema (http://go.microsoft.com/fwlink/?LinkId=109946&clcid=0x409) topics in the Windows SharePoint Services 3.0 SDK on MSDN. For more information about deploying upgrade definition files and new site definitions, see Deploy upgrade definition files and new site definitions (Windows SharePoint Services). For additional information about creating upgrade definition files, such as what to include in the files and the schema, see Upgrading Windows SharePoint Services (http://go.microsoft.com/fwlink/?LinkId=98404&clcid=0x409) in the Windows SharePoint Services 3.0 SDK on MSDN. Record upgrade definition file information on a worksheet Record the file names and paths for each upgrade definition file that you need to create on the Custom templates and mapping files worksheet (http://go.microsoft.com/fwlink/?LinkID=73751&clcid=0x409). Download this book This topic is included in the following downloadable book for easier reading and printing: Upgrading Windows SharePoint Services See the full list of available books at Downloadable books for Windows SharePoint Services. Page 54 of 146 II. Perform pre-upgrade steps (*WSS*) Topic Last Modified: 2007-03-09 Insert introduction here. Subhead Insert section body here. Subhead Insert section body here. Page 55 of 146 Chapter overview: Perform pre-upgrade steps (Windows SharePoint Services) Topic Last Modified: 2009-06-30 There are specific steps you must take before you start the upgrade process. If you don't perform these steps before you start the upgrade process, the upgrade process might fail. This chapter describes the pre-upgrade steps you must perform to have a successful upgrade experience, regardless of which upgrade path you are pursuing. In this chapter: Install Service Pack 2 for Windows SharePoint Services 2.0 Install all pre-requisites (Windows SharePoint Services) Communicate downtime to site owners and users (Windows SharePoint Services) Run and test a full backup in SQL Server (Windows SharePoint Services) Create new domain names (gradual upgrade only) (Windows SharePoint Services) Run the pre-upgrade scan tool (Windows SharePoint Services) Deploy upgrade definition files and new site definitions (Windows SharePoint Services) Upgrade custom Web Part packages (Windows SharePoint Services) Save blocked file type settings (Windows SharePoint Services) After you have completed the pre-upgrade steps, you can perform the in-place or gradual upgrade, or database migration. Download this book This topic is included in the following downloadable book for easier reading and printing: Upgrading Windows SharePoint Services See the full list of available books at Downloadable books for Windows SharePoint Services. Page 56 of 146 Install Service Pack 2 for Windows SharePoint Services 2.0 Topic Last Modified: 2007-12-13 If you have not already applied Service Pack 2 (SP2) to your environment, you must do so before upgrading. Note: It is advised that you perform a full backup of your Windows SharePoint Services environment prior to applying a service pack. To install Microsoft Windows SharePoint Services SP2, do one of the following: Use Microsoft Windows Update (http://go.microsoft.com/fwlink/?LinkID=15270&clcid=0x409) to update your Web server computer (recommended). Windows Update scans your computer and provides you with a tailored selection of updates that apply only to the items on your computer. Download Windows SharePoint Services SP2 from the Microsoft Download Center Web site (http://go.microsoft.com/fwlink/?LinkId=71862), and then run the service pack executable on a server computer that is running the original version of Windows SharePoint Services. Note: If you are running a server farm configuration, you must install the service pack to each front-end Web server computer. For more information, see the Microsoft Knowledge Base article KB 875358: You must update all the Web servers in a Web farm that is running Windows SharePoint Services (http://go.microsoft.com/fwlink/?LinkID=39585&clcid=0x409). For more information about installing SP 2 for Windows SharePoint Services, see Installing and Using Service Packs for Windows SharePoint Services 2.0. Download this book This topic is included in the following downloadable book for easier reading and printing: Upgrading Windows SharePoint Services See the full list of available books at Downloadable books for Windows SharePoint Services. Page 57 of 146 Install all pre-requisites (Windows SharePoint Services) Topic Last Modified: 2008-02-15 In this article: Install Microsoft .NET Framework 3.0 Enable Microsoft ASP.NET 2.0 Before you can upgrade, you must have the following pre-requisite software installed: The Web server and application server computers must be running Microsoft® Windows® Server 2003 (Standard, Enterprise, Datacenter, or Web Edition) with Service Pack 1 (SP1), and must have Microsoft .NET Framework 3.0 and Microsoft ASP.NET 2.0. Instructions for installing Microsoft .NET Framework 3.0 and enabling Microsoft ASP.NET 2.0 are provided later in this article. For more information about Microsoft .NET Framework, see the Microsoft .NET Framework Developer Center (http://msdn.microsoft.com/netframework/). For server farm installations, the back-end database server computer must be running Microsoft SQL Server™ 2005 or Microsoft SQL Server 2000 with Service Pack 3 (SP3) or later. Page 58 of 146 Install Microsoft .NET Framework 3.0 Go to the Microsoft Download Center Web site (http://go.microsoft.com/fwlink/?LinkID=72322&clcid=0x409). On the Microsoft .NET Framework 3.0 page, follow the instructions for downloading and installing Microsoft .NET Framework 3.0. There are separate downloads for x86-based computers and x64-based computers; be sure to download and install the appropriate version for your computer. The Microsoft .NET Framework version 3.0 download contains the Windows Workflow Foundation technology, which is required by Windows SharePoint Services 3.0 workflow features. Important: If you have a previous version of the Windows Workflow Foundation, such as Windows Workflow Foundation Beta 2.2 (build 3807.7), you must uninstall that version before installing this version of Microsoft .NET Framework 3.0. Note: You can also use the Microsoft .NET Framework version 3.5. You can download the .NET Framework version 3.5 from the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=110508). Enable Microsoft ASP.NET 2.0 1. Click Start, point to All Programs, point to Administrative Tools, and then click Internet Information Services (IIS) Manager. 2. In the IIS Manager tree, click the plus sign (+) next to the server name, and then click the Web Service Extensions folder. 3. In the details pane, click ASP.NET v2.0.50727, and then click Allow. Download this book This topic is included in the following downloadable book for easier reading and printing: Upgrading Windows SharePoint Services See the full list of available books at Downloadable books for Windows SharePoint Services. Page 59 of 146 Communicate downtime to site owners and users (Windows SharePoint Services) Topic Last Modified: 2007-12-13 Before you run the upgrade, you need to tell the owners and users of your sites that their sites are about to be upgraded. You should include the following information: Whether site owners and users will be able to use their sites during the upgrade process. All sites are unavailable during an in-place upgrade. How long you expect the upgrade process to take and when their sites will be ready to use again. Whether the site owners or users will have to redo any customizations after upgrade. (This is necessary so that they can record information about the customizations before you run the upgrade.) Download this book This topic is included in the following downloadable book for easier reading and printing: Upgrading Windows SharePoint Services See the full list of available books at Downloadable books for Windows SharePoint Services. Page 60 of 146 Run and test a full backup in SQL Server (Windows SharePoint Services) Topic Last Modified: 2015-03-09 In this article: Back up a database Test the backups To ensure that you can recover your existing environment in case something goes wrong during the upgrade process, you must back up all of the databases that are used by Windows SharePoint Services before you run the upgrade process. Windows SharePoint Services 2.0 uses two types of databases, as listed in the following table. Database type Database name Notes Configuration database ID_Config_db Required — one per farm. Content databases STS_database_server_name_ID Optional — there can be several of these if you have many team sites in your environment. Note: The database names above are examples of the default naming structure. The naming structure for your databases may vary. Perform a full backup operation with either the Stsadm command-line tool or SQL Server. If you are using SQL Server, use the simple recovery model, so that your transaction log is truncated. Back up a database Follow the appropriate steps to back up your databases in either SQL Server 2000 or SQL Server 2005. Back up a database in SQL Server 2000 1. On your database server, click Start, point to All Programs, point to Microsoft SQL Server, and then click Enterprise Manager. 2. In SQL Server Enterprise Manager, click the plus sign next to Microsoft SQL Servers. 3. Click the plus sign next to SQL Server Group. Page 61 of 146 4. Click the plus sign next to (local) (Windows NT). 5. Click the plus sign next to Databases. 6. Right-click the database you want to back up, point to All Tasks, and then click Backup Database. 7. In the SQL Server Backup dialog box, in the Name box, specify a name for the backup, and then in the Backup area, select Database - complete. 8. In the Destination area, either select an existing destination, or: a) Click Add. b) In the Select Backup Destination box, select File Name, and then next to the File Name box, click the browse button. c) In the Backup Device Location - (local) dialog box, in the File name box, type a file name, and then click OK. d) Click OK again to close the Select Backup Destination dialog box. 9. Click OK to start the backup process. 10. Click OK to acknowledge that the backup process has completed. Repeat these steps to back up the configuration database plus all of the other databases that are used by Windows SharePoint Services in your environment. Important: You should also back up any customizations (such as site definitions, Web Parts, and so on) and other files you would need in case you need to re-create your previous-version environment. Back up a database in SQL Server 2005 1. On your database server, click Start, point to All Programs, point to Microsoft SQL Server 2005, and then click SQL Server Management Studio. 2. In the Connect to Server box, fill in the connection information, and then click Connect. 3. After connecting to the appropriate instance of the Microsoft SQL Server Database Engine, in Object Explorer, click the server name to expand the server tree. 4. Expand Databases and select the database to back up. 5. Right-click the database, point to Tasks, and then click Back Up. The Back Up Database dialog box appears. 6. In the Source section, in the Database box, verify the database name. 7. In the Backup type box, select Full. 8. Under Backup component, click Database. 9. In the Name text box, either accept the default backup set name suggested or enter a different name for the backup set. 10. In the Destination section, choose the type of backup destination by clicking Disk or Tape, and then select a destination. To create a different destination, click Add. 11. Click OK to start the backup. Page 62 of 146 Repeat these steps to back up the configuration database plus all of the other databases that are used by Windows SharePoint Services in your environment. Important: You should also back up any customizations (such as site definitions, Web Parts, and so on) and other files you would need in case you need to re-create your previous-version environment. After you have backed up all of your databases, use the SQL Server DBCC shrinkfile command to free unused log space, making the logs as empty as possible. For more information, see Shrinking the Transaction Log (http://go.microsoft.com/fwlink/?LinkId=105233). Test the backups You need to be sure that these backups are valid so that you can recover if there is a hardware failure or data corruption during the upgrade process. To test your backups, set up a non-production, front-end Web server computer and a computer running SQL Server, restore the backups and install any customizations (such as site definitions, Web Parts, and so on), and then verify that the restored backup is functional. Download this book This topic is included in the following downloadable book for easier reading and printing: Upgrading Windows SharePoint Services See the full list of available books at Downloadable books for Windows SharePoint Services. Page 63 of 146 Create new domain names (gradual upgrade only) (Windows SharePoint Services) Topic Last Modified: 2009-02-05 If you are performing a gradual upgrade, you must have two separate domain names for your existing sites and your upgraded sites. The new, upgraded sites take over your existing domain names so that users can continue with their work on the upgraded sites without having to update their Favorites or bookmarks. The existing sites move to temporary domain names, where you can access them as needed. For example, if you have sites at http://company_intranet or http://portal_name, create a temporary domain name such as http://company_intranet_v2 or http://portal_name_v2 to host the previous version's sites, leaving the original URL for the new version. By default, the new and the temporary domain names point to the same IP address. However, if you use IP addresses instead of domain names to access content, the IP addresses for the existing and upgraded sites must be different. Note: You can also use a port number instead of a full domain name as the temporary URL. Ensure that the port is available. For more information about specifying the domain name or port number during upgrade, see Upgrade sites (Windows SharePoint Services), Plan security hardening for server roles within a server farm (Windows SharePoint Services), and Plan security hardening for extranet environments (Windows SharePoint Services). For more information about how URLs change during a gradual upgrade, see How the upgrade process works (Windows SharePoint Services). You must create the new domain names before you install the new version and upgrade any sites. For more information, see Creating DNS Domain Names and Computer Names (http://go.microsoft.com/fwlink/?LinkId=128856&clcid=0x409) in the Windows Server 2003 documentation on TechNet. Download this book This topic is included in the following downloadable book for easier reading and printing: Upgrading Windows SharePoint Services See the full list of available books at Downloadable books for Windows SharePoint Services. Page 64 of 146 Run the pre-upgrade scan tool (Windows SharePoint Services) Topic Last Modified: 2009-06-11 In this article: Issues that are reported by the pre-upgrade scan tool Install and run the pre-upgrade scan tool 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. 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: 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. For more information about issues or errors reported by the pre-upgrade scan tool, see the following blog entries on the Microsoft Web site: http://go.microsoft.com/fwlink/?LinkId=106424 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 Page 65 of 146 gradual upgrade, orphaned items will not be copied to the new site. We recommend that you clean up any orphaned objects before upgrading. Tip: Members of the Administrators group on the front-end 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). 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 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 frontend 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. Determine upgrade approach provides information to help you decide which type of upgrade to perform. 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. Page 66 of 146 Important: 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. Note: For more information about issues or errors reported by the pre-upgrade scan tool, see the following blog entries on the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=106424). Install and run the pre-upgrade scan tool 1. Download and install the pre-upgrade scan tool from the Microsoft Download center (http://go.microsoft.com/fwlink/?LinkId=92383). Note: You must be a member of the Administrators group on the local computer to run this tool. 2. On the command line, change to the folder that contains the file, and then run the following command to scan all servers in your server farm: prescan.exe /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. 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. 3. 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 preupgrade 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 also share the relevant pre-upgrade scan test results with other members of the upgrade team. For example, you can report issues such as Page 67 of 146 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. Download this book This topic is included in the following downloadable book for easier reading and printing: Upgrading Windows SharePoint Services See the full list of available books at Downloadable books for Windows SharePoint Services. See Also Other Resources Preupgradecheck: Stsadm operation (Windows SharePoint Services) Page 68 of 146 Deploy upgrade definition files and new site definitions (Windows SharePoint Services) Topic Last Modified: 2016-05-06 In this article: Before you deploy upgrade definition files and site definitions Deploy upgrade definition files and site definitions You can create upgrade definition files and custom site definitions in a separate development environment. Then, you can use the following process to deploy new upgrade definition files and custom site definitions to your server. Important: This step must be performed after installation, but before running the SharePoint Products and Technologies Configuration Wizard. Before you deploy upgrade definition files and site definitions Before you perform this procedure, you must create the upgrade definition files and custom site definitions. For more information, see Develop new custom site definitions and create upgrade definition files (Windows SharePoint Services) and the Windows SharePoint Services 3.0: Software Development Kit (http://go.microsoft.com/fwlink/?LinkID=798133&clcid=0x409). Deploy upgrade definition files and site definitions 1. Save the upgrade definition files to the %COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\12\CONFIG\UPGRADE folder. 2. Save the custom site definitions to the %COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\12\TEMPLATE\SiteTemplates\NAME folder, where NAME matches the site definition name (for example, ACTION). Name the new folder using all uppercase letters. 3. Save the Webtemp.xml files for your custom site definitions to the %COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\12\TEMPLATE\LCID\XML folder. Name the files WEBTEMPNAME.xml, where NAME matches the site definition name (for example, WEBTEMPACTION.xml). Page 69 of 146 4. You might need to reset Internet Information Services (IIS) to recognize the new site definitions. To reset IIS, run the following command on the command line: iisreset /noforce 5. If you have a server farm, repeat these steps for all servers in your farm. Page 70 of 146 Upgrade custom Web Part packages (Windows SharePoint Services) Topic Last Modified: 2007-12-13 Upgrade custom Web Part packages Most custom Web Parts will continue working after upgrade. However, you should test your Web Parts in ASP.NET 2.0 to verify that they will work in the new environment. In particular, you must rebuild or redeploy custom Web Parts if you: Used the ASP.NET 1.1 obfuscation tools. If you used these tools, you must rebuild your Web Parts by using ASP.NET 2.0. Are moving to a new server farm by using the database migration path for upgrade. If you choose this upgrade path, you must redeploy your Web Parts to the new farm. Have stored your custom Web Parts in the \BIN folder and are not upgrading in-place. Gradual upgrade does not upgrade items to the new \BIN folder, so you must redeploy your Web Parts. To upgrade your Web Parts, test them in ASP.NET 2.0, and then either rebuild or redeploy any Web Parts that meet the criteria above. Download this book This topic is included in the following downloadable book for easier reading and printing: Upgrading Windows SharePoint Services See the full list of available books at Downloadable books for Windows SharePoint Services. Page 71 of 146 Save blocked file type settings (Windows SharePoint Services) Topic Last Modified: 2009-02-13 If you change the blocked file type settings, these changes are not saved after you upgrade. You have to manually save the blocked file type settings and then reapply them after you upgrade. Use the following procedure to save the blocked file type settings before you upgrade. Save blocked file type settings before upgrade 1. In Windows SharePoint Services 2.0, on the Central Administration home page, under the Security Configuration heading, click Manage blocked file types. 2. Right-click in the area where the file name extensions are listed, and then click Select All. Rightclick again, and then click Copy. 3. Paste the copied information into a Notepad file. 4. Save the file and then proceed with the upgrade. For information about how to reapply blocked file type settings after an in-place upgrade, go to the Reapply Blocked File Type Settings section in Perform post-upgrade steps for an in-place upgrade (Windows SharePoint Services). For information about how to reapply blocked file type settings after a gradual upgrade, go to the Reapply Blocked File Type Settings section in Perform post-upgrade steps for a gradual upgrade (Windows SharePoint Services). Page 72 of 146 III. Perform an in-place upgrade (*WSS*) Topic Last Modified: 2007-03-09 Insert introduction here. Subhead Insert section body here. Subhead Insert section body here. Page 73 of 146 Chapter overview: Perform an in-place upgrade (Windows SharePoint Services) Topic Last Modified: 2007-12-13 The in-place upgrade approach is the simplest. After you perform the pre-upgrade steps, run Setup for the new version, install any necessary language packs, start the SharePoint Products and Technologies Configuration wizard, wait while the upgrade runs, and then verify the results. In this chapter: Install and configure Windows SharePoint Services for an in-place upgrade Install available language template packs (Windows SharePoint Services) After you have completed these steps, you can go on to the Perform post-upgrade steps (Windows SharePoint Services) chapter and perform the following steps: Review upgraded sites (Windows SharePoint Services) Troubleshoot and resume upgrade (Windows SharePoint Services) Perform post-upgrade steps for an in-place upgrade (Windows SharePoint Services) Download this book This topic is included in the following downloadable book for easier reading and printing: Upgrading Windows SharePoint Services See the full list of available books at Downloadable books for Windows SharePoint Services. Page 74 of 146 Install and configure Windows SharePoint Services for an in-place upgrade Topic Last Modified: 2009-01-21 When you run an in-place upgrade, all content and configuration data is upgraded in-place, at one time. When you start the in-place upgrade process, the Web server and Web sites remain offline until the upgrade has been installed. When you perform an in-place upgrade, you cannot pause or roll back to the previous version. Upgrade is a detailed and complicated operation. Even in relatively basic environments, there may be customizations that do not lend themselves to a smooth and simple upgrade. These customizations, and many other variables, are outside of the control of the upgrade process and may cause the in-place upgrade to fail. We recommend in-place upgrade only for a stand-alone server and even then, in limited situations. In general, this means that you should consider in-place upgrade for environments that meet both of the following conditions: Small installations Environments that have not been customized In practice, this means that you should only use in-place upgrade in environments where there is minimal impact when a server is down. Examples include development, test, or staging servers where you need a quick upgrade experience and can quickly roll back the entire server to an earlier configuration. For example, in a virtualized environment, if something goes wrong with the upgrade, you can discard the undo disks and, in minutes, be back to your original environment. Another option to avoid having to troubleshoot a failed upgrade is to restore your server from a backup. Note: If you have a more complex server farm, we recommend that you perform a gradual upgrade. For more information about performing a gradual upgrade, see Install and configure Windows SharePoint Services for a gradual upgrade. For more information about choosing an upgrade approach, see Determine upgrade approach. When upgrading a server farm, be sure to upgrade all of the servers in the server farm in the following order: 1. Run Setup to install the new version on all servers in the server farm. 2. Run the SharePoint Products and Technologies Configuration Wizard on the front-end Web server that contains SharePoint Central Administration. Page 75 of 146 3. Run the SharePoint Products and Technologies Configuration Wizard on all other front-end Web servers or search servers in the farm in any order. In this article: Before you begin Install Windows SharePoint Services version 3 Run the SharePoint Products and Technologies Configuration Wizard Install and configure Windows SharePoint Services using the command line Review the log files and resolve any issues Before you begin Before you begin installing Windows SharePoint Services 3.0, make sure that you have installed and configured all the pre-requisite software. For more information, see Install all pre-requisites (Windows SharePoint Services). Make sure that these are the minimum permissions for the account that you use to run Setup and the SharePoint Products and Technologies Configuration Wizard: The account is a member of the Administrators group on the Web server computer. The account is granted the fixed database role (db_owner) for all SharePoint Products and Technologies databases. In many IT environments, database administrators (DBAs) create and manage databases. Security policies and other policies in your organization might require that DBAs create the databases needed by Windows SharePoint Services 3.0. Note: For information about how to deploy Windows SharePoint Services 3.0 in an environment in which DBAs create and manage databases, see Deploy using DBA-created databases (Windows SharePoint Services) (http://go.microsoft.com/fwlink/?LinkID=86818&clcid=0x409). If you are running an in-place upgrade on a server farm, stop the World Wide Web Publishing Service (W3SVC) on all front-end Web servers to disconnect all the users from the server farm. In server farms with multiple front-end Web servers, if you allow users to connect after the files and databases have been updated on one Web server, and the other Web servers have not been updated, users will not be able to browse the Web sites. Install Windows SharePoint Services 3.0 1. Run Setup.exe. Tip: As an alternative to installing Windows SharePoint Services 3.0 and then separately deploying the available software updates, you can download a Windows SharePoint Page 76 of 146 Services 3.0 install file that includes the available software updates. You can find the Windows SharePoint Services 3.0 install file that includes the available software updates on the Microsoft Download Center (http://go.microsoft.com/fwlink/?LinkID=72322&clcid=0x409). 2. On the Read the Microsoft Software License Terms page, review the terms, select the I accept the terms of this agreement check box, and then click Continue. 3. On the Upgrade earlier versions page, click Yes, perform an automated in-place upgrade. 4. On the Server Type tab, select your server type: Choose Web Front End if you are running upgrade on a server farm. Choose Stand-alone if this is a stand-alone server (not part of a SharePoint farm), and you want to use Windows Internal Database for your database. Note: Your server environment may not detect all of these server types. 5. Click Install Now. Note: If you have a custom site definition or custom Web application installed on your server, you will see a Setup Warning box notifying you that there are third-party products installed that integrate with Windows SharePoint Services 2.0. If you are aware of these customizations or applications and are prepared to continue with the upgrade process (for example, if you have created upgrade definition files for any custom templates), click OK. If you want to cancel the upgrade process and investigate these products, click Cancel. For more information about upgrade definition files, see Develop new custom site definitions and create upgrade definition files (Windows SharePoint Services). 6. The Installation Progress page appears and Setup installs Windows SharePoint Services 3.0 and applies updates. 7. On the completion page, clear the Run the SharePoint Products and Technologies Configuration Wizard now check box, and then click Close. Before you run the SharePoint Products and Technologies Configuration Wizard, you should perform the following steps: Deploy software updates available for Windows SharePoint Services 3.0. For more information, see Deploy software updates for Windows SharePoint Services 3.0. Run the pre-upgrade scan tool to be sure that you have identified and addressed any issues. For more information, see Run the pre-upgrade scan tool (Windows SharePoint Services). Deploy any upgrade definition files. For more information, see Deploy upgrade definition files and new site definitions (Windows SharePoint Services). Install any language template packs for Windows SharePoint Services 3.0. Alternatively, you can install them after you complete the upgrade process, and then use the command line to upgrade any sites that depend on the language template packs. For more information, see Install available language template packs (Windows SharePoint Services). Page 77 of 146 Note: In server farm deployments, all your Web servers must have the same software update version applied. To accomplish, you can create an installation source that contains a copy of the released software product, along with the available software updates (also known as a slipstreamed installation source). When you run Setup from this updated installation source, the Web server will have the same software update version as the rest of the Web servers in your server farm. You can also use the installation source to add a new Web server to an existing server farm. When you run Setup from this updated installation source, the new Web server will have the same software update version as the rest of the Web servers in your server farm. For more information about creating an installation source, see Create an installation source that includes software updates (Windows SharePoint Services 3.0) Run the SharePoint Products and Technologies Configuration Wizard 1. Click Start, point to All Programs, point to Administrative Tools, and then click SharePoint Products and Technologies Configuration Wizard. 2. In the SharePoint Products and Technologies Configuration Wizard, on the Welcome to SharePoint Products and Technologies page, click Next. A message appears, notifying you that Internet Information Services (IIS), the SharePoint Administration Service, and the SharePoint Timer Service may need to be restarted or reset during configuration. 3. Click Yes to continue with the wizard. A message appears, notifying you that you should download and install new language template packs for the new version. 4. Click OK to confirm the message and continue with the wizard. Do not install the language template packs until you have completed running the configuration wizard. Note: If you chose Stand-alone as your server type, the configuration wizard skips the next few steps and starts the configuration process. Skip to step 8 in this procedure. 5. On the Configure SharePoint Central Administration Web Application page, if you want to use a specific port number for SharePoint Central Administration, select the Specify port number check box, and then type the port number to use. 6. In the Configure Security Settings section, select either Negotiate (Kerberos) or NTLM, depending on your environment, and then click Next. Page 78 of 146 Note: To enable Kerberos authentication, you must perform additional configuration. For more information about authentication methods, see Plan authentication methods (Windows SharePoint Services). 7. In the Completing the SharePoint Products and Technologies Configuration Wizard page, verify the settings, and then click Next. The configuration wizard runs and configures the configuration database and Central Administration Web application for Windows SharePoint Services 3.0. 8. 9. A message appears notifying you that if you have a server farm with multiple servers, you must run Setup on each server to install new binary files before continuing the configuration wizard. Depending on your server farm configuration, and where you are in the process of installing and configuring Windows SharePoint Services 3.0, you have three choices: If this is the only server in your farm, no other actions are necessary. Click OK to continue with the wizard. If you have other servers in your farm, and you have not yet run Setup and the configuration wizard on the other servers, leave this message open on this server, and then run Setup and the configuration wizard on the other servers in the farm. When all of the other servers are at this same stage, you can return to the front-end Web server and click OK to continue with the SharePoint Products and Technologies Configuration Wizard. If you have already run Setup and the configuration wizard on all servers in your server farm and they are all at this stage, on a front-end Web server, click OK to continue with the configuration wizard. The configuration wizard continues the upgrade process by setting up the configuration database and installing the Central Administration Web application. 10. On the Configuration Successful page, review the settings that have been configured, and then click Finish. The SharePoint Products and Technologies Configuration Wizard closes and the Upgrade Running page opens. You may be prompted to enter your user name and password before the Upgrade Running page will open. The upgrade process might take a while to complete. The Upgrade Running page refreshes every minute. 11. After the process has completed, click Continue. Page 79 of 146 The Central Administration home page opens. If you stopped the World Wide Web Publishing Service (W3SVC) on all front-end Web servers before the upgrade, make the Web servers available to users by manually starting the World Wide Web Publishing Service on the front-end Web servers. Install and configure Windows SharePoint Services 3.0 using the command line If you prefer, you can use the command line to install and configure Windows SharePoint Services 3.0 instead. For more information, see Setup.exe command-line reference (Windows SharePoint Services), Command-line reference for the SharePoint Products and Technologies Configuration Wizard (Windows SharePoint Services), Stsadm command-line tool (Windows SharePoint Services), and Install Windows SharePoint Services 3.0 by using the command line. Note: If you started the installation in silent mode, using the /q switch, the SharePoint Products and Technologies Configuration Wizard does not automatically start. To continue the upgrade, you need to force the upgrade by either manually starting the wizard or running the psconfig command with arguments to force an in-place version to version upgrade. Review the log files and resolve any issues If upgrade fails or reports issues, you can refer to the log files for more information. The Upgrade.log file is located at %COMMONPROGRAMFILES%\Microsoft Shared\web server extensions\12\LOGS. Caution: In some configurations, the SharePoint Timer Service (OWStimer) account—which, by default, is the same account used by the SharePoint Central Administration v3 application pool account— is configured with credentials that do not have permission to access the LOGS folder in %COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\12\. If this is the case, part of the Upgrade.log file is stored in the temporary storage folder of the account that is running the SharePoint Timer service. To avoid the possibility of deleting the upgrade log file when you restart the server computer, copy Upgrade.log to another location. For information about viewing the upgrade log file, see Verify upgrade (Windows SharePoint Services). For information about troubleshooting common issues, see Troubleshoot and resume upgrade (Windows SharePoint Services). Page 80 of 146 Install available language template packs (Windows SharePoint Services) Topic Last Modified: 2008-04-01 Before you can upgrade any sites based on a previous version's language template pack, you need to install the new version's language template pack. In this article: About installing language template packs and upgrading sites About changing languages Install language template packs Page 81 of 146 For more information about language template packs, see Deploy language packs (Windows SharePoint Services 3.0) in the Deployment Guide. About installing language template packs and upgrading sites If you want to install a language template pack for Windows SharePoint Services 3.0, do so after running Setup and before running the SharePoint Products and Technologies Configuration Wizard. This way, you can upgrade any sites based on a Windows SharePoint Services language template pack along with your other sites during the upgrade process (either in-place or gradual). You can also install a language template pack after you have run the SharePoint Products and Technologies Configuration Wizard, and after you have upgraded the sites in your environment that are not based on a language template pack. If you choose this path, you must then use the command line to upgrade the sites based on the newly installed language template pack. For more information about using the command line to upgrade sites based on a language template pack, see Upgrade sites (Windows SharePoint Services). About changing languages Generally, a cross-language upgrade is not supported; you must upgrade from and to the same language. For example, if you are running U.S. English in the previous version, you need to upgrade to U.S. English in the new version. If you want to change languages, you must first perform the upgrade and then change the language for the site. However, this process is complicated in some cases — such as when the previous version had a fully localized product for a particular language but the new version only has a language template pack, or when the new version has a language template pack for a new language that was not available in the previous version. Moving from a fully localized product to a language template pack Use the following procedure to upgrade from a language that was supported with a fully localized product in the previous version, but that is only supported by a language template pack in the new version: 1. Choose a language to install for the new version (for example, English), and select the appropriate upgrade option (in-place or gradual) during setup. This is the language that the SharePoint Central Administration Web site will use. 2. In the SharePoint Products and Technologies Configuration Wizard, when you are prompted to install language template packs, stop the wizard and install the appropriate language's language template pack. Page 82 of 146 If you had additional Windows SharePoint Services language template packs installed, install the Windows SharePoint Services 3.0 language template packs now by canceling the wizard and running the appropriate Setup programs to install the language template packs. Then start the wizard again. 3. Run the configuration wizard again to start the upgrade process. Changing languages to a new language template pack Use the following process to upgrade from one language in the previous version to a different language in the new version (for example, if the language you want was not available in the previous version, but is now available as a language template pack in the new version). 1. Upgrade to the new version in the same language that you used for the previous version. 2. After the upgrade is complete, install the new language template pack. 3. Create new sites based on the new language template pack. 4. Manually move your content to the new sites. Install language template packs After you install the new version, you can install the language template packs you need. Note: Before you begin, be sure you have configured supplemental support for the languages you want to install in your server operating system. You can install language support files by opening the Regional and Language Options control panel, and then on the Language tab, in the Supplemental language support area, selecting the check boxes for the language types you need to support. Note: You can install the language template pack for Windows SharePoint Services 3.0 after you deploy the software updates and the updated language packs for Windows SharePoint Services 3.0. This makes it possible for you to first install Windows SharePoint Services 3.0 on a Web server from a slipstreamed installation source and then install the language template pack for Windows SharePoint Services 3.0. A slipstreamed installation source is an installation source that contains a copy of the released version of the software, along with software updates and updated language packs. For more information about creating an installation source, see Create an installation source that includes software updates (Windows SharePoint Services 3.0). To install a language template pack 1. Download the language template pack for Windows SharePoint Services 3.0 from the Microsoft Download Center (http://go.microsoft.com/fwlink/?LinkId=82240). For x64 systems, use the following link: Microsoft Download Center (http://go.microsoft.com/fwlink/?LinkId=82241). Page 83 of 146 2. For the language template pack, run Setup.exe. 3. Follow the instructions in Setup to install the language template pack. 4. On the completion page, clear the Run the SharePoint Products and Technologies Configuration Wizard now check box, and then click Close. After installing all of the language templates packs you need, you can continue configuring your installation. For more information, see Install and configure Windows SharePoint Services for an in-place upgrade or Install and configure Windows SharePoint Services for a gradual upgrade. Page 84 of 146 IV. Perform a gradual upgrade (*WSS*) Topic Last Modified: 2007-03-09 Insert introduction here. Subhead Insert section body here. Subhead Insert section body here. Page 85 of 146 Chapter overview: Perform a gradual upgrade (Windows SharePoint Services) Topic Last Modified: 2007-12-13 A gradual upgrade enables you to run both the previous and new versions, so that you can move sites gradually to the new environment, and have both versions of the sites available for transferring customizations or comparison. In this chapter: Install and configure Windows SharePoint Services for a gradual upgrade Install available language template packs (Windows SharePoint Services) Upgrade sites (Windows SharePoint Services) After you have completed these steps, you can go on to the Perform post-upgrade steps (Windows SharePoint Services) chapter and perform the following steps: Review upgraded sites (Windows SharePoint Services) Revert to a previous version site (Windows SharePoint Services) Troubleshoot and resume upgrade (Windows SharePoint Services) Perform post-upgrade steps for a gradual upgrade (Windows SharePoint Services) Finalize upgrade (Windows SharePoint Services) Download this book This topic is included in the following downloadable book for easier reading and printing: Upgrading Windows SharePoint Services See the full list of available books at Downloadable books for Windows SharePoint Services. Page 86 of 146 Install and configure Windows SharePoint Services for a gradual upgrade Topic Last Modified: 2009-01-29 A gradual upgrade installs the new version side-by-side with the previous version. After you install and configure Windows SharePoint Services 3.0, you can then determine which site collections to upgrade and when to upgrade them. Note: You must use an in-place upgrade (or database migration) if you are using Windows SharePoint Services 2.0 in stand-alone mode with Microsoft SQL Server™ 2000 Desktop Engine (Windows) (WMSDE). For more information about performing an in-place upgrade, see Install and configure Windows SharePoint Services for an in-place upgrade. For more information about choosing an upgrade approach, see Determine upgrade approach. When upgrading a server farm, be sure to upgrade all of the servers in the server farm in the following order: 1. Run Setup to install the new version on all servers in the server farm. 2. Run the SharePoint Products and Technologies Configuration Wizard on the front-end Web server that contains the SharePoint Central Administration Web site. 3. Run the SharePoint Products and Technologies Configuration Wizard on all other front-end Web servers or search servers in the farm in any order. In this article: Before you begin Install Windows SharePoint Services 3.0 Install and configure Windows SharePoint Services 3.0 on other front-end Web servers in the farm Run the SharePoint Products and Technologies Configuration Wizard Install and configure Windows SharePoint Services 3.0 using the command line Review the log files and resolve any issues Page 87 of 146 Before you begin Before you begin installing Windows SharePoint Services 3.0, be sure you have installed all prerequisite software. For more information, see Install all pre-requisites (Windows SharePoint Services). Make sure that the minimum permissions for the account that you use to run Setup and the SharePoint Products and Technologies Configuration Wizard are: The account is a member of the Administrators group on the Web server computer. The account is granted the fixed database role db_owner to all SharePoint Products and Technologies databases. In many IT environments, database administrators (DBAs) create and manage databases. Security policies and other policies in your organization might require that DBAs create the databases needed by Windows SharePoint Services 3.0. Note: For information about how to deploy Windows SharePoint Services 3.0 in an environment in which DBAs create and manage databases, see Deploy using DBA-created databases (Windows SharePoint Services) (http://go.microsoft.com/fwlink/?LinkID=86818&clcid=0x409). Install Windows SharePoint Services 3.0 1. Run Setup.exe. Tip: As an alternative to installing Windows SharePoint Services 3.0 and then separately deploying the available software updates, you can download a Windows SharePoint Services 3.0 install file that includes the available software updates. You can find the Windows SharePoint Services 3.0 install file that includes the available software updates on the Microsoft Download Center. 2. On the Read the Microsoft Software License Terms page, review the terms, select the I accept the terms of this agreement check box, and then click Continue. 3. On the Upgrade earlier versions page, click Yes, perform a Gradual upgrade. 4. On the Server Type tab, select Web Front End. 5. Click Install Now. Note: If you have a custom site definition or custom Web application installed on your server, you will see a Setup Warning dialog box, notifying you that there are third-party products installed that integrate with Windows SharePoint Services 2.0. If you are aware of these customizations or applications and are prepared to continue with the upgrade process (for example, if you have created upgrade definition files for any custom templates), click OK. If you want to cancel the upgrade process and investigate these products, click Cancel. For Page 88 of 146 more information about upgrade definition files, see Develop new custom site definitions and create upgrade definition files (Windows SharePoint Services). 6. Setup runs and installs Windows SharePoint Services 3.0. 7. On the completion page, clear the Run the SharePoint Products and Technologies Configuration Wizard now check box, and then click Close. Before you run the SharePoint Products and Technologies Configuration Wizard, you should perform the following steps: Deploy software updates available for Windows SharePoint Services 3.0. For more information, see Deploy software updates for Windows SharePoint Services 3.0. Run the pre-upgrade scan tool to be sure that you have identified and addressed any issues. For more information, see Run the pre-upgrade scan tool (Windows SharePoint Services). Deploy any upgrade definition files. For more information, see Deploy upgrade definition files and new site definitions (Windows SharePoint Services). Install any language template packs for Windows SharePoint Services 3.0. Alternatively, you can install them after you complete the upgrade process, and then, from the command line, upgrade any sites that depend on the language template packs. For more information, see Install available language template packs (Windows SharePoint Services). Note: In server farm deployments, all your Web servers must have the same software update version applied. To accomplish this, you can create an installation source that contains a copy of the released software product, along with the available software updates (also known as a slipstreamed installation source). When you run Setup from this updated installation source, the Web server will have the same software update version as the rest of the Web servers in your server farm. You can also use the installation source to add a new Web server to an existing server farm. When you run Setup from this updated installation source, the new Web server will have the same software update version as the rest of the Web servers in your server farm. For more information about creating an installation source, see Create an installation source that includes software updates (Windows SharePoint Services 3.0) Install and configure Windows SharePoint Services 3.0 on other front-end Web servers in the farm If you have a server farm, follow the instructions to Install Windows SharePoint Services 3.0 on each front-end Web server in your server farm, and then Run the SharePoint Products and Technologies Configuration Wizard. Caution: Do not add any servers to your server farm after running Setup. Running the SharePoint Products and Technologies Configuration Wizard upgrades the configuration database. This Page 89 of 146 database contains the list of servers in the farm, and any servers added to the farm after the configuration wizard has been run will not be included in the database, and therefore will not appear in the Windows SharePoint Services 3.0 topology. If you need to add servers to your farm, do so either before starting the upgrade or after you have completed the upgrade process, following the steps in Add servers to an upgraded farm (Windows SharePoint Services). Run the SharePoint Products and Technologies Configuration Wizard 1. Click Start, point to All Programs, point to Administrative Tools, and then click SharePoint Products and Technologies Configuration Wizard. 2. In the SharePoint Products and Technologies Configuration Wizard, on the Welcome to SharePoint Products and Technologies page, click Next. 3. A message appears, notifying you that IIS, the SharePoint Administration Service, and the SharePoint Timer Service may need to be restarted or reset during configuration. Click Yes to continue with the wizard. 4. A message appears, notifying you that if you have existing language template packs, you should download and install the new version of the language packs before you proceed. Click OK to continue with the wizard. 5. On the Connect to a server farm page, select No, I want to create a new server farm, and then click Next. 6. On the Specify Configuration Database Settings page, in the Database server box, type the name of the server running Microsoft SQL Server 2000 or SQL Server 2005. 7. In the Database name box, leave the default (SharePoint_Config) or type a database name to use instead. 8. In the Specify Database Access Account section, type the user name and password to use to connect to SQL Server, and then click Next. Note: This account must have rights to create databases. If SQL Server is running on a server that is separate from your Web front-end server, then this account must also be a domain account. This user account must be a member of the following SQL Server security roles: Database Creator and Security Administrator. 9. On the Configure SharePoint Central Administration Web Application page, if you want to use a specific port number for SharePoint Central Administration, select the Specify port number check box, and then type the port number to use. 10. In the Configure Security Settings section, select either Negotiate (Kerberos) or NTLM, depending on your environment, and then click Next. Page 90 of 146 Note: To enable Kerberos authentication, you must perform additional configuration steps. For more information about authentication methods, see Plan authentication methods (Windows SharePoint Services). 11. On the Completing the SharePoint Products and Technologies Configuration Wizard page, verify the settings, and then click Next. The configuration wizard runs and configures the configuration database and the Central Administration application for Windows SharePoint Services 3.0. 12. A message appears notifying you that if you have a server farm with multiple servers, you must run Setup on each server to install new binary files before running the configuration wizard and starting the upgrade process. Depending on your server farm configuration, and where you are in the process of installing and configuring Windows SharePoint Services 3.0, you have three choices: If this is the only server in your farm, no other actions are necessary. Click OK to continue with the wizard. If you have other servers in your farm, and you have not yet run Setup and the configuration wizard on the other servers, leave this message open on this server, and then run Setup and the configuration wizard on the other servers in the farm. After you have run Setup and the configuration wizard on the other servers, you can return to the front-end Web server and click OK to continue with the SharePoint Products and Technologies Configuration Wizard. If you have run Setup and the configuration wizard on all servers in your server farm, and they are all at this stage, on a front-end Web server, click OK to continue with the configuration wizard. 13. On the Configuration Successful page, review the settings that have been configured, and then click Finish. The SharePoint Products and Technologies Configuration Wizard closes and Central Administration opens. You may be prompted to enter your user name and password before the Central Administration site will open. If you have not already done so, you can install any language template packs you need for the new version. For more information, see Install available language template packs (Windows SharePoint Services). After installing the language packs (if any), you are ready to start upgrading specific Web applications and site collections. Continue with the process by following the steps in the Upgrade sites (Windows SharePoint Services) topic. Install and configure Windows SharePoint Services 3.0 using the command line If you prefer, you can install and configure Windows SharePoint Services 3.0 from the command line instead. For more information, see Setup.exe command-line reference (Windows SharePoint Services), Command-line reference for the SharePoint Products and Technologies Configuration Page 91 of 146 Wizard (Windows SharePoint Services), Stsadm command-line tool (Windows SharePoint Services), and Install Windows SharePoint Services 3.0 by using the command line. Note: If you started the installation in silent mode, using the /q switch, the SharePoint Products and Technologies Configuration Wizard does not automatically start. To continue the upgrade, you need to force the upgrade by either manually starting the wizard or running the psconfig command with arguments to force a gradual upgrade. Review the log files and resolve any issues If the upgrade fails or reports issues, you can refer to the log files for more information. The Upgrade.log file is located in %COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\12\LOGS. Caution: In some configurations, the SharePoint Timer Service (OWStimer) account—which, by default, is the same account used by the SharePoint Central Administration v3 application pool account— is configured with credentials that do not have permission to access the LOGS folder in %COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\12\. If this is the case, part of the Upgrade.log file is stored in the temporary storage folder of the account that is running the SharePoint Timer service. To avoid the possibility of deleting the upgrade log file when you restart the server computer, copy Upgrade.log to another location. For information about troubleshooting common issues, see Troubleshoot and resume upgrade (Windows SharePoint Services). For information about viewing the upgrade log file, see Verify upgrade (Windows SharePoint Services). Page 92 of 146 Upgrade sites (Windows SharePoint Services) Topic Last Modified: 2015-03-09 In this article: Upgrade sites by using Central Administration pages Upgrade sites by using the command line Upgrade sites after installing a language template pack When you perform a gradual upgrade, you can determine which sites to upgrade and when. Before you can upgrade any sites to Windows SharePoint Services 3.0, you must run Setup and the SharePoint Products and Technologies Configuration wizard on all servers in your server farm. After you have completed that step and installed any language template packs you need, you can begin to upgrade sites. For more information about upgrading your servers, see Install and configure Windows SharePoint Services for a gradual upgrade. When you are ready to upgrade your sites, you can use either the upgrade pages in the SharePoint® Central Administration Web site or the upgrade operation on the command line. Use the command line if you want to run upgrade for large batches of sites at different times, or if you have installed a language template pack after upgrading other sites in your environment. Upgrade sites by using Central Administration pages There are two phases in the process for upgrading sites from the Central Administration pages. First, you create a new Web application to host the upgraded versions of the sites. Then, you upgrade one or more site collections. Important: You must upgrade the root site collection before you can upgrade any other site collections in the Web application. Create a new Web application to host upgraded sites 1. In Central Administration, on the Operations tab, under Upgrade and Migration, click Site content upgrade status. 2. On the Site Content Upgrade Status page, next to the URL you want to upgrade, click Begin upgrade. 3. On the Set Target Web Application page, in the Web Application to Upgrade section, verify that the Web application you want to upgrade appears. 4. In the New URL for Original Content section, in the Port box, type a port number, and then in the Host Header box, type the host header to use (if needed). Page 93 of 146 5. In the Application Pool for New Web Application section, select Create new application pool, then in the Application pool name box, type a name, and then select either Predefined or Configurable. If you selected Predefined, select the account to use. If you selected Configurable, type the account name to use, and then type the password for that account. Note: You cannot use the same application pool that you used for the previous version. You can use the same user account, but you must create a new application pool, or use an application pool that you already created for your upgraded sites. 6. In the Reset Internet Information Services section, select either Restart IIS Automatically or Restart IIS Manually. If you choose Restart IIS Manually, you will need to restart IIS after the Web application is created in the final step in this procedure. 7. In the Security Configuration section, under Authentication Provider, select either Negotiate (Kerberos) or NTLM depending on your environment. 8. In the Content Databases section, select either Automatic database name selection or Manually set database names. If you choose to manually set the database names, then on the Database Names page, you must supply names for the temporary content databases and the new version content databases. 9. Click OK. If you chose to manually set the database names, the Database Names page opens. Type the names to use for the temporary content databases and the new version content databases for this Web application, and then click Save. An Operation in Progress page appears while the new Web application is created. Note: If you chose to restart IIS manually, you must now run iisreset /noforce on each front-end Web server in your server farm. Upgrade site collections 1. On the Site Collection Upgrade page, select the check boxes next to the sites you want to upgrade, and then click Upgrade Sites. Important: You must upgrade the root site collection before you can upgrade any other site collections in the Web application. If you are upgrading multiple site collections at one time, the root site collection must be included in the first set of sites that you upgrade. 2. On the Sites Selected for Upgrade page, verify the number of site collections, the storage used, the originating database, and the target database, and then click Upgrade Sites. The Upgrade Running page opens, and upgrade runs for the selected site collections. This may take a few minutes or a few hours, depending on how many site collections you have selected and how Page 94 of 146 large the site collections are. The Status page refreshes automatically every minute to provide you with an updated status. If the upgrade fails or reports issues, you can refer to the log files for more information. The Upgrade.log file and the trace log file are located at %COMMONPROGRAMFILES%\Microsoft Shared\web server extensions\12\LOGS. The trace log is named in the following format: Machine_name-YYYYMMDD-HHMM.log, where YYMMDD is the date and HHMM is the time (for example, Server1-20061105-1241.log). 3. After the upgrade process has completed, click Home to return to the Central Administration home page. Upgrade sites by using the command line To upgrade sites by using the command line, you must follow the same two-step process: create a target Web application, and then upgrade the sites. To create the target Web applications, use the following command, including any options that apply to your environment (skip this step if you have already performed the steps under "Create a new Web application to host upgraded sites" above): stsadm -o upgradetargetwebapplication -url <URL to upgrade> -relocationurl <new URL for non-upgraded content> -apidname <new application pool name> [-apidtype <configurableid/NetworkService>] [-apidlogin <DOMAIN\name>] [-apidpwd <application pool password>] [-exclusivelyusentlm] For information about how to perform this procedure using the Stsadm command-line tool, see Upgradetargetwebapplication: Stsadm operation (Windows SharePoint Services). Then, after you have created the Web application, you can upgrade individual site collections by using the following command, including any options that apply to your environment: stsadm -o upgrade [-inplace | -sidebyside] [-url <url>] [-forceupgrade] [-quiet] [-farmuser <farm user> -farmpassword <farm password>] [-sitelistpath <sites xml file>] For example, to upgrade sites at a particular URL in a side-by-side (gradual) upgrade process, you would use the following command: stsadm -o upgrade -sidebyside -url <url> -sitelistpath <path to XML file> Note: When you use the command line to perform a gradual upgrade, you cannot upgrade sites from different content databases. If your Web application contains a large number of sites spread Page 95 of 146 across multiple content databases, break the list into smaller groups of sites contained within the same content database. For information about how to perform this procedure using the Stsadm command-line tool, see Upgrade: Stsadm operation (Windows SharePoint Services). To get a list of sites that need to be upgraded, you can use the enumsites operation to list all redirected sites on a Web application. Use the following syntax to generate the list: stsadm -o enumsites -url http://server_name -redirectedsites You can use the list of sites generated by this operation to generate your sitelist XML file for the upgrade operation. The following table describes the parameters used for the upgrade operation: Parameter Optional/Requir Description ed Inplace or Required, you Inplace specifies an in-place upgrade, where the version 2.0 sites are Sidebyside must specify one upgraded immediately, and the version 2.0 environment is not of these options available after the upgrade process is complete. Sidebyside specifies a gradual upgrade, where the version 2.0 sites are preserved in the version 2.0 environment. URL Optional ForceUpgrad Optional The version 2.0 URL to the site collection. Specifies whether or not to force the upgrade. e Quiet Optional Specifies that the upgrade process is run in quiet mode. FarmUser Optional Specifies the user account to use in performing the upgrade. FarmPasswor Optional (but d Specifies the password for the FarmUser account. required if using FarmUser) Reghost Optional Specifies whether to reghost pages (reset pages to site definition) during upgrade. Page 96 of 146 Parameter Optional/Requir Description ed SiteListPath Optional Allows you to specify an XML file with a list of specific site collections to upgrade. The format of the XML file is: <RedirectedSites Count="2"> <Site Url="http://server_name" TargetDatabase="DB1" /> <Site Url="http://server_name/sites/site1" TargetDatabase= "DB1" /> </RedirectedSites> The “Count” and “TargetDatabase” attributes are optional. Specify just the set of sites you want to upgrade from a single content database. Alternatively, use the command stsadm –o enumsites –url<V3url>redirectedsites to produce this same XML for site collections that require upgrade. For information about how to perform this procedure using the Stsadm command-line tool, see Enumsites: Stsadm operation (Windows SharePoint Services). Upgrade sites after installing a language template pack If you performed an in-place upgrade and then installed a language template pack, you must now upgrade any sites that depend on the language in that language template pack. To perform the upgrade, perform the upgrade operation on the command line by using any options that apply to your environment. Download this book This topic is included in the following downloadable book for easier reading and printing: Upgrading Windows SharePoint Services (http://go.microsoft.com/fwlink/?LinkID=85554) See the full list of available books at Downloadable books for Windows SharePoint Services. Page 97 of 146 V. Deploy a new server farm, then migrate content databases Topic Last Modified: 2007-03-09 Insert introduction here. Subhead Insert section body here. Subhead Insert section body here. Page 98 of 146 Chapter overview: Deploy a new farm, then migrate databases (Windows SharePoint Services) Topic Last Modified: 2007-12-13 If you are moving to new hardware, or redesigning and restructuring your deployment, you can choose to migrate your databases from the old version to the new version rather than directly upgrading them. When you perform a database migration, you perform an in-place upgrade on the databases, but you do not upgrade your server farm configuration data. Although this upgrade path has more manual steps than either an in-place or a gradual upgrade, it can be the best option if you have highly customized sites or custom Web services or applications. Important: Before you begin the process, be sure you have performed the planning and pre-upgrade steps. For more information, see Chapter overview: Plan and prepare for upgrade and Chapter overview: Perform pre-upgrade steps (Windows SharePoint Services). Perform a database migration by using the following steps: 1. Create the environment for the new version. See Prepare the new Windows SharePoint Services 3.0 environment. 2. Back up or copy the databases, and then migrate the data. If you have a server farm, see Migrate content databases. If you have a stand-alone server, see Migrate content databases from WMSDE to Windows Internal Database. After you have completed these steps, you can go on to the Perform post-upgrade steps (Windows SharePoint Services) chapter and perform the following steps: Review the sites to be sure they upgraded properly. See Review upgraded sites (Windows SharePoint Services) Troubleshoot and resume upgrade (Windows SharePoint Services) Perform post-upgrade steps for an in-place upgrade (Windows SharePoint Services). Because database migration is essentially an in-place upgrade for your content, you can use the same postupgrade steps. Page 99 of 146 Download this book This topic is included in the following downloadable book for easier reading and printing: Upgrading Windows SharePoint Services See the full list of available books at Downloadable books for Windows SharePoint Services. Page 100 of 146 Prepare the new Windows SharePoint Services 3.0 environment Topic Last Modified: 2009-01-29 Before you can migrate your content into a new environment, you must create that new environment. Depending on your current Windows SharePoint Services configuration, you need to perform different steps to create that environment. If you have a server farm, follow the steps in Deployment for Windows SharePoint Services 3.0 technology to deploy and configure your new server farm. If you have a stand-alone server running Microsoft® SQL Server™ 2000 Desktop Engine (Windows), follow the steps in Install Windows SharePoint Services 3.0 on a stand-alone computer to deploy and configure your server. Part of creating the new environment is recreating the Web applications, re-applying configuration settings, and copying other customizations over from the old environment. After you deploy Windows SharePoint Services 3.0, you must: 1. Create a Web application for each virtual server that was in the old environment. For more information, see Deployment for Windows SharePoint Services 3.0 technology. 2. Manually re-apply farm configuration settings, including: Outgoing e-mail server Any server farm–level security and permission settings Included paths (such as /sites or /mysites) Alternate access settings Quota templates For more information about configuring these settings, see Deployment for Windows SharePoint Services 3.0 technology. 3. Manually copy all customizations into your new farm. Be sure to install any of the following components that your sites may depend on to work properly, including: Language packs Custom site definitions Custom style sheets (cascading style sheets files) Custom Web Parts Custom Web services Any other components or files on which your sites may depend Page 101 of 146 Note: Ensure that you transfer settings from the Web.config file to your new farm. After you finish preparing the new environment, you can migrate the databases. If you have a server farm, follow the steps in Migrate content databases to migrate your databases from the previous version server farm to the new version server farm. If you have a stand-alone server running WMSDE, follow the steps in Migrate content databases from WMSDE to Windows Internal Database to migrate your database from the previous version stand-alone server to the new version stand-alone server. Download this book This topic is included in the following downloadable book for easier reading and printing: Upgrading Windows SharePoint Services See the full list of available books at Downloadable books for Windows SharePoint Services. Page 102 of 146 Migrate content databases Topic Last Modified: 2015-03-09 In this article: Before you begin Set the previous version databases to be read-only Back up the previous version databases using SQL Server Restore the backup copy to the new farm Add the databases to the Web applications Review the upgrade log files for any issues Repeat the restore and add database procedures for all content databases When you upgrade by way of a database migration, you essentially perform a backup and restore of your databases (that is, you back them up in the old farm, and then restore them in the new farm). When you restore a database and add it to the farm, the upgrade process runs and upgrades the entire database. The database migration process is similar to the in-place upgrade process; the difference is that the database migration process is performed manually and gradually. Before you begin, you must create your new server farm environment. For information about creating the new environment, see Prepare the new Windows SharePoint Services 3.0 environment. After you have set up the new environment, you can follow the steps below to detach and then reconnect the databases to perform the upgrade. Before you begin Before backing up and migrating your databases, you must perform the following steps to prepare for the upgrade. 1. Run the pre-upgrade scan tool on the content in your original environment. If you do not run the pre-upgrade scan tool on your databases before you back them up, you will not be able to upgrade the data on your new server farm. For more information, see Run the pre-upgrade scan tool (Windows SharePoint Services). 2. Create your new server farm environment. For information about creating the new environment, see Prepare the new Windows SharePoint Services 3.0 environment. 3. If you have custom site definitions or area definitions in your old environment, create new site definitions and upgrade definition files for these site definitions and deploy them to your new environment. For more information, see the following resources: Page 103 of 146 Develop new custom site definitions and create upgrade definition files (Windows SharePoint Services) Deploy upgrade definition files and new site definitions (Windows SharePoint Services) Set the previous version databases to be read-only Be sure you capture all of the data in your backup so that you are restoring and upgrading the current state of your environment. Therefore, set the previous version databases to read-only so that users cannot add or change information in the sites. With the databases set to read-only, users can continue to view content, but they are not able to add or change content. Important: Before you perform these procedures, be sure that you have run the pre-upgrade scan tool on the sites stored in the databases. If you do not run the pre-upgrade scan tool on the data before you back the databases up, you will not be able to upgrade the data on your new server farm. For more information, see Run the pre-upgrade scan tool (Windows SharePoint Services). Set a database to read-only in SQL Server 2000 1. In Microsoft SQL Server Enterprise Manager, right-click the name of the database that you want to set to read-only, and then click Properties. 2. In the Properties dialog box, click the Options tab. 3. Under Access, select the Read-only check box, and then click OK. Set a database to read-only in SQL Server 2005 1. In SQL Server Management Studio, right-click the name of the database that you want to set to read-only, and then click Properties. 2. In the Select a page section, click Options. 3. In the right pane, under Other options, in the State section, next to Database Read-Only, click the down arrow, and then select True. Back up the previous version databases by using SQL Server tools Follow the appropriate steps to back up your databases in either SQL Server 2000 or SQL Server 2005. Repeat these steps for each content database in your server farm. Do not perform these steps for the configuration database; you do not need the configuration database because you have created a new one in the new environment. Back up a database in SQL Server 2000 1. On your database server, click Start, point to All Programs, point to Microsoft SQL Server, and then click Enterprise Manager. Page 104 of 146 2. In SQL Server Enterprise Manager, click the plus sign next to Microsoft SQL Servers. 3. Click the plus sign next to SQL Server Group. 4. Click the plus sign next to (local) (Windows NT). 5. Click the plus sign next to Databases. 6. Right-click the database you want to back up, point to All Tasks, and then click Backup Database. 7. In the SQL Server Backup dialog box, in the Name box, specify a name for the backup, and then in the Backup area, select Database - complete. 8. In the Destination area, either select an existing destination, or: a) Click Add. b) In the Select Backup Destination box, select File Name, and then next to the File Name box, click the Browse button. c) In the Backup Device Location - (local) dialog box, in the File name box, type a file name, and then click OK. d) Click OK again to close the Select Backup Destination dialog box. 9. Click OK to start the backup process. 10. Click OK to acknowledge that the backup process has completed. Repeat these steps to back up all of the other content databases that are used by Windows SharePoint Services 3.0 in your environment. Back up a database in SQL Server 2005 1. On your database server, click Start, point to All Programs, point to Microsoft SQL Server 2005, and then click SQL Server Management Studio. 2. In the Connect to Server box, fill in the connection information, and then click Connect. 3. After connecting to the appropriate instance of the SQL Server 2005 Database Engine, in Object Explorer, expand the server tree by clicking the plus sign next to the server name. 4. Expand Databases, right-click the database you want to back up, point to Tasks, and then click Back Up. The Back Up Database dialog box appears. 5. In the Source section, in the Database box, verify the database name. 6. In the Backup type box, select Full. 7. Under Backup component, select Database. 8. In the Backup set section, in the Name text box, either accept the default backup set name that is suggested or type a different name for the backup set. 9. In the Destination section, specify the type of backup destination by selecting Disk or Tape, and then specify a destination. To create a different destination, click Add. 10. Click OK to start the backup process. Page 105 of 146 Repeat the preceding procedure to back up all of the other content databases that are used by Windows SharePoint Services 3.0 in your environment. Restore the backup copy to the new farm After you have configured the new environment, you can restore the backup copies of the databases. Start with one database, and then verify that the restoration has worked before you restore the other databases. You must create a new database to contain the restored data, and then you can restore the backup into that new database. When you create the new database, be sure to create a large transaction log initially. The upgrade process creates many transactions while it runs and if your log is small, it might not be able to grow quickly enough to handle the number of transactions. If the transaction log runs out of space, the upgrade process will fail and you will need to retry attaching the database and upgrading the data. The following sections provide steps for restoring the backups for both SQL Server 2000 and SQL Server 2005. Restore the backup copy in SQL Server 2000 First, you create a new database. Then, you restore the backup into that new database. Create a new database to contain the restored data in SQL Server 2000 1. Open Enterprise Manager and connect to the server to which the backup is to be restored. 2. Expand Microsoft SQL Servers, expand SQL Server Group, and then expand (local) Windows NT. 3. Right-click Databases, and then click New Database. 4. In the Name box, type the name of the database you want to restore. 5. On the Data files tab, in the File Name box for the Data file type, verify that the name is the one you want to use. 6. In the Initial Size (MB) box, adjust the size to approximately the size of the database you want to restore. 7. On the Transaction Log tab, in the File Name box for the Log file type, verify that the name is the one you want to use. 8. In the Initial Size (MB) box, adjust the size to approximately three or four times the size of the log file for the database you want to restore. Make the log file very large to avoid filling it up during the upgrade process. You can always shrink the transaction log again after you have completed the upgrade. 9. In the File properties section, be sure that the Automatically grow file check box is selected. 10. In the Maximum file size section, be sure that Unrestricted file growth is selected. You can change these settings after you perform the upgrade. It is important that the log file not run out of space during the upgrade process. 11. Click OK to create the database. Page 106 of 146 Restore a backup copy of a database as a new database in SQL Server 2000 1. Copy the database backup file to the target computer or share it on the network so that it is accessible from the server. 2. Open Enterprise Manager and connect to the server to which the backup is to be restored. 3. Expand Microsoft SQL Servers, expand SQL Server Group, and then expand (local) Windows NT. 4. Right-click the database you just created, click All Tasks, and then select Restore Database. The Restore Database dialog box appears. 5. In the Restore as database box, select the new database. This is the database to which the backup will be restored. 6. Select the From device option. 7. Click the Select Devices button. 8. In the Choose Restore Devices dialog box, select Disk. 9. Click the Add button. The Choose Restore Destination dialog box appears. 10. Enter the file name of the backup file that is to be restored. If the file exists on a network share, provide the UNC share name in the File name text box. Note: We recommend that you copy the backup to the server and use a local path to restore the database. 11. Click OK. The Choose Restore Device dialog box is now updated with the selected file. 12. Click OK to return to the Restore Database dialog box. The Devices list is now updated with the file selected in the previous step. 13. Click the Options tab, and then select the Force restore over existing database check box. This ensures that the restore operation overwrites the new database you just created. 14. Click OK in the Restore Database dialog box. This starts the restore process. Progress and confirmation dialog boxes are displayed as SQL Server performs and completes the restore of the database. 15. Click OK in the confirmation dialog box. For more information about restoring a backup to a new database, see SQL Server 2000 Backup and Restore (http://go.microsoft.com/fwlink/?LinkId=93461). Restore the backup copy in SQL Server 2005 First, you create a new database. Then, you restore the backup into that new database. Create a new database to contain the restored data in SQL Server 2005 1. After connecting to the appropriate instance of the SQL Server 2005 Database Engine, in Object Explorer, expand the server tree by clicking the plus sign next to the server name. 2. Right-click Databases, and then click New Database. Page 107 of 146 3. In the Database name box, type the name of the database you want to restore. 4. In the Owner box, specify an owner if desired. 5. In the Database files section, in the Logical Name box for the Data file type, verify that the logical name is the one you want to use. 6. In the Initial Size (MB) box, adjust the size to approximately the size of the database you want to restore. 7. In the Logical Name box for the Log file type, verify that the logical name is the one you want to use. 8. In the Initial Size (MB) box, adjust the size to approximately three or four times the size of the log file for the database you want to restore. Make the log file very large to avoid filling it up during the upgrade process. You can always shrink the transaction log again after you have completed the upgrade. 9. In the Autogrowth column for the log file, set it to By 10 percent, unrestricted growth. You can change this setting after you perform the upgrade. It is important that the log file not run out of space during the upgrade process. 10. Click OK to create the database. Restore a backup copy of a database in SQL Server 2005 Enterprise Edition 1. Right-click the database you just created, point to Tasks, point to Restore, and then click Database. The Restore Database dialog box appears. 2. In the Restore Database dialog box, on the General page, the name of the restoring database appears in the To database list box. 3. In the To a point in time text box, retain the default (Most recent possible). 4. To specify the source and location of the backup sets to restore, select From device, and then click the browse button to select the backup file. 5. In the Specify Backup dialog box, in the Backup media box, be sure that File is selected. 6. In the Backup location area, click Add. 7. In the Locate Backup File dialog box, select the file you want to restore, and then click OK. 8. In the Select the backup sets to restore grid, select the Restore check box next to the most recent full backup. 9. In the Restore Database dialog box, on the Options page, under Restore options, select the Overwrite the existing database check box. 10. Click OK to start the restore process. Add the databases to the Web applications When you add the content databases, be sure that the root site for the Web application is included in the first content database you add (in other words, the first site collection at the root of the virtual server in your old environment). After you have added the database that contains the root site, you can add the other content databases for the Web application in any order. You do not need to create any Page 108 of 146 site collections to store the content before you add the database; this process creates the site collections for you. Be sure that you do not add any new site collections until you have restored all of the content databases. You must use the Stsadm command-line tool to add a content database to a Web application. Note: You cannot add the same content database more than once to a farm, even on different Web applications. Each site collection in a content database has a globally unique identifier (GUID) associated with it, registered in the configuration database. Therefore, it is not possible to add the same site collection twice to the farm, even in separate Web applications. Although you can successfully attach the database in this situation, the site collection cannot be started. If you need a duplicate copy of a site collection in the same farm, first attach the database that contains the site collection to a separate farm, and then use the Stsadm.exe backup and restore operations to copy the site collection over to the other farm. The backup and restore process creates a new GUID for the site collection. Add a content database to a Web application by using the Stsadm command-line tool To add a content database to a Web application, you use the addcontentdb operation. Important: If you are running Windows SharePoint Services 3.0 in host-header mode, you must perform an additional step to set a host header property before you attach the content databases. This step is not needed if you are running Windows SharePoint Services 3.0 with Service Pack 1 applied. On the command line, run the following command: stsadm.exe -o setproperty -pn V2UsedHostHeaderMode -pv true After you add the content databases, you must then set the property to false so the next content database operation is for databases that contain site collections that use managed paths (such as \sites): stsadm.exe -o setproperty -pn V2UsedHostHeaderMode -pv false Run the following command: stsadm -o addcontentdb -url <URL> –databasename <database name> [-databaseserver <server name>] [-databaseuser <user name> [ -databasepassword <password>] [-sitewarning <site warning count>] [-sitemax <site max count>] The following table explains the parameters for the addcontentdb operation. Name Required/Optional Page 109 of 146 Description Name Required/Optional Description URL Required URL of the Web application to which the content database is being added. DatabaseName Required Database name. DatabaseServer Optional Database server name. The default server is used if a value not provided. DatabaseUser Optional Account used for SQL authentication. Must be used in conjunction with databasepassword. DatabasePassword Optional (however, required if The databasepassword parameter using DatabaseUser) should only be used where Windows authentication is not implemented Therefore, in a SQL authentication scenario, you need to pass the databaseuser and databasepassword parameters to authenticate against the database server. Under Windows authentication, you can omit these parameters because the credentials are passed using NTLM. SiteWarning Optional Integer number of site collections allowed in the content database prior to generating a warning event in the Windows event log. SiteMax Optional Specifies the maximum number of site collections allowed in the content database. For more information about this operation, see Addcontentdb: Stsadm operation (Windows SharePoint Services). Review the upgrade log files for any issues Page 110 of 146 After you have attached the database and the upgrade process has completed, you can review the upgrade log file to see if there were any issues during upgrade. The upgrade log file and the trace log file are located at %COMMONPROGRAMFILES%\Microsoft Shared\web server extensions\12\LOGS. The trace log is named in the following format: Computer_name-YYYYMMDD-HHMM.log, where YYYYMMDD is the date and HHMM is the time (for example, Server1-20061105-1241.log). Repeat the restore and add database procedures for all content databases If you have multiple content databases, after you have restored the first content database and verified the upgrade by reviewing the upgrade log file, you can continue by restoring and upgrading the next database. After you have successfully restored and upgraded all of the content databases, you can review the sites to be sure that they upgraded properly. For more information, see Review upgraded sites (Windows SharePoint Services). Next, follow the steps in Perform post-upgrade steps for an in-place upgrade (Windows SharePoint Services). Because database migration is essentially an in-place upgrade for your content, you can use the same post-upgrade steps. For more post-upgrade steps, see Chapter overview: Perform postupgrade steps (Windows SharePoint Services). Download this book This topic is included in the following downloadable book for easier reading and printing: Upgrading Windows SharePoint Services See the full list of available books at Downloadable books for Windows SharePoint Services. Page 111 of 146 Migrate content databases from WMSDE to Windows Internal Database Topic Last Modified: 2015-03-09 In this article: Detach the databases from your WMSDE instance Copy and attach the database files to SQL Server Add the databases to the Web applications Review the upgrade log files for any issues Repeat the restore and add database procedures for all content databases If you are using Windows SharePoint Services 2.0 in stand-alone mode with Microsoft SQL Server 2000 Desktop Engine (Windows) (WMSDE), it is still possible to upgrade by way of a database migration. First, you must create your new environment in stand-alone mode, complete with the Windows Internal Database. Windows Internal Database uses SQL Server technology as a relational data store for Windows roles and features only, such as Windows SharePoint Services, Active Directory Rights Management Services, UDDI Services, Windows Server Update Services, and Windows System Resources Manager.. For more information about creating the new environment, see Prepare the new Windows SharePoint Services 3.0 environment. After you have the new environment installed, you can follow the steps below to first detach and then copy and attach the databases SQL Server. Then you add the databases to the Web application that will host the content. When you add the databases to the Web application, the upgrade process runs and upgrades the content databases to the new version. Note: Before you detach your databases, be sure that you have run the pre-upgrade scan tool on the site content stored in the databases. For more information, see Run the pre-upgrade scan tool (Windows SharePoint Services). Detach the databases from your WMSDE instance Important: Take your environment offline to perform this process. With WMSDE databases, you do not have the option to mark the database read-only, as you do with SQL Server 2000 or Microsoft SQL Server 2005. If you do not take your environment offline, there is the risk that users will add Page 112 of 146 content or change settings in their sites; if this occurs, you will not have those changes in your backups and, therefore, in your new environment. 1. On the computer running Windows SharePoint Services, click Start, point to Run, type cmd, and then click OK. Note: Be sure you are logged on as a member of the Administrators group on the local server. 2. Type the following command and then press ENTER: Osql –S Servername\sharepoint -E This connects to the OSQL database management tool, with your SharePoint database instances specified. 3. Type the following command and then press ENTER: EXEC sp_detach_db “Content_Database_name” where Content_Database_name is the name of your database, such as MSSharePoint. 4. Type the following command and then press ENTER: Go 5. If you get an error message such as "Database is in use and cannot be detached," use the following commands on the command line to pause and restart the database engine: net pause mssql$sharepoint net continue mssql$sharepoint For more information, see How to change the location of the Windows SharePoint Services database files (http://go.microsoft.com/fwlink/?LinkId=75398&clcid=0x409). Repeat these steps for any additional content databases you may have. Do not perform these steps for the configuration database; you do not need the configuration database because you have created a new one in the new environment. After you have detached the databases, you can copy and then attach the databases to your new environment. To perform these steps, you need to install the SQL Server 2005 Command Line Query Utility; you can download this tool from the Feature Pack for Microsoft SQL Server 2005 - April 2006 (http://go.microsoft.com/fwlink/?LinkID=72684&clcid=0x409). Install both the Microsoft SQL Server Native Client (sqlncli.msi, a pre-requisite for installing the command-line query utility) and the SQL Server 2005 Command Line Query Utility (SQLServer2005_SQLCMD.msi). Copy and attach the database files to SQL Server 1. Copy the database files for your content database (with extensions .mdf and .ldf) to the following location in your new environment: Page 113 of 146 Drive:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data where Drive is the drive where Windows SharePoint Services is installed. 2. If you have not already done so, on the computer running Windows SharePoint Services 3.0, install the Microsoft SQL Server Native Client and the SQL Server 2005 Command Line Query Utility from the Feature Pack for Microsoft SQL Server 2005 - April 2006 (http://go.microsoft.com/fwlink/?LinkID=72684&clcid=0x409). 3. On the computer running Windows SharePoint Services 3.0, click Start, point to Run, type cmd, and then click OK. Note: Be sure you are logged on as a member of the Administrators group on the local server. 4. Type the following command and then press ENTER to attach the databases that you copied: sqlcmd -S \\.\pipe\mssql$microsoft##ssee\sql\query -E 5. Type the following command and then press ENTER: EXEC sp_attach_db @dbname = N'Content_Database_name', @filename1 = N'%WINDIR%\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data\<dbname>.mdf', @filename2 = N'%WINDIR%\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data \<dbname>_log.ldf’ 6. Type the following command and then press ENTER: Page 114 of 146 Go Add the databases to the Web applications When you add the content databases, be sure that the root site for the Web application is included in the first content database you add. After you have added the database that contains the root site, you can add the other content databases for the Web application in any order. Be sure that you do not add any new site collections until you have restored all of the content databases. You must use the command-line tool to add a content database to a Web application. Note: You cannot add the same content database more than once to a farm, even on different Web applications. Each site collection in a content database has a globally unique identifier (GUID) associated with it, registered in the configuration database. Therefore, it is not possible to add the same site collection twice to the farm, even in separate Web applications. Although you can successfully attach the database in this situation, the site collection cannot be started. If you need a duplicate copy of a site collection in the same farm, first attach the database that contains the site collection to a separate farm, and then use the Stsadm.exe backup and restore operations to copy the site collection over to the other farm. The backup and restore process creates a new GUID for the site collection. Add a content database to a Web application by using the command-line tool To add a content database to a Web application, use the addcontentdb operation. Important: If you are running Windows SharePoint Services 3.0 in host-header mode, you must perform an additional step to set a host header property before you attach the content databases. This step is not needed if you are running Windows SharePoint Services 3.0 with Service Pack 1 applied. On the command line, run the following command: stsadm.exe -o setproperty -pn V2UsedHostHeaderMode -pv true After you add the content databases, you must then set the property to false so the next content database operation is for databases that contain site collections that use managed paths (such as \sites): stsadm.exe -o setproperty -pn V2UsedHostHeaderMode -pv false To add a content database, on the command line, run the following command: Page 115 of 146 stsadm -o addcontentdb -url URL [-databaseserver servername] –databasename databasename [-DatabaseUser username -DatabasePassword password] [-SiteWarning number] [-SiteMaximum number] [-SearchServer servername] The following table explains the parameters for the addcontentdb operation. Name Required/Optional Description URL Required The URL for the Web application to which this database is being added. DatabaseServer Optional The database server where the new database will be stored. The short version of this parameter is DS. If omitted, this parameter defaults to the name of the server from which you are running the command. DatabaseName Required The name of the database you are creating. The short version of this parameter is DN. DatabaseUser Optional The user account for SQL Server database creation. If you use this parameter, you must also specify the DatabasePassword parameter. DatabasePassword SiteWarning Optional (however, required if The password for the specified using DatabaseUser) DatabaseUser account. Optional The integer number of site collections to allow in this content database prior to generating a warning event in the Windows Event log. SiteMaximum Optional The maximum number of site collections to allow in this content database. SearchServer Optional The Search server to use for indexing content in this content database. Page 116 of 146 Review the upgrade log files for any issues After you have attached the database and the upgrade process has completed, you can review the upgrade log file to see if there were any issues during upgrade. The upgrade log file and the trace log file are located at %ProgramFiles%\Common Files\Microsoft Shared\web server extensions\12\LOGS. The trace log is named in the following format: Machine_name-YYYYMMDD-HHMM.log, where YYYYMMDD is the date and HHMM is the time (for example, Server1-20061105-1241.log). Repeat the restore and add database procedures for all content databases Repeat these steps for any additional content databases you may have. After you have successfully restored and upgraded all of the content databases, you can review the sites to be sure they upgraded properly (for more information, see Review upgraded sites (Windows SharePoint Services)). Then follow the steps in the Perform post-upgrade steps for an in-place upgrade (Windows SharePoint Services) topic; because database migration is essentially an in-place upgrade as far as your content is concerned, you can use the same post-upgrade steps. Download this book This topic is included in the following downloadable book for easier reading and printing: Upgrading Windows SharePoint Services See the full list of available books at Downloadable books for Windows SharePoint Services. Page 117 of 146 VI. Perform post-upgrade steps (*WSS*) Topic Last Modified: 2007-03-09 Insert introduction here. Subhead Insert section body here. Subhead Insert section body here. Page 118 of 146 Chapter overview: Perform post-upgrade steps (Windows SharePoint Services) Topic Last Modified: 2008-03-24 After you have reviewed your upgraded sites and made any changes that you needed to, and after you have also determined that you are done running the upgrade process, then you can finish the upgrade, import or migrate any additional content you need to include, and remove the old version of the product. In this chapter: Verify upgrade (Windows SharePoint Services) Review upgraded sites (Windows SharePoint Services) Revert to a previous version site (Windows SharePoint Services) — for gradual upgrades only Troubleshoot and resume upgrade (Windows SharePoint Services) Perform post-upgrade steps for an in-place upgrade (Windows SharePoint Services) Perform post-upgrade steps for a gradual upgrade (Windows SharePoint Services) Finalize upgrade (Windows SharePoint Services) Migrate content or sites after upgrade (Windows SharePoint Services) Add servers to an upgraded farm (Windows SharePoint Services) Download this book This topic is included in the following downloadable book for easier reading and printing: Upgrading Windows SharePoint Services See the full list of available books at Downloadable books for Windows SharePoint Services. Page 119 of 146 Verify upgrade (Windows SharePoint Services) Topic Last Modified: 2010-03-26 In this article: View the upgrade log Force a software upgrade View the Servers in Farm page View the upgrade log After you have upgraded to Windows SharePoint Services 3.0 and installed the available software update, you should verify that the installation was successful by reviewing the upgrade log file (Upgrade.log), as described in the following procedure. To view the upgrade log file 1. In Windows Explorer, change to the following directory: %COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\12\LOGS 2. Use a text editor to open the Upgrade.log file. 3. Scroll to the date on which you installed the software update. 4. Search, or visually scan, for the following entries: Finished upgrading SPFarm Name=<Name of Configuration Database> In-place upgrade session finishes. Root object = SPFarm=<Name of Configuration Database>, recursive = True. 0 errors and 0 warnings encountered. If you find these entries, the installation was successful. 5. If you do not find the entries from the previous step, you can identify specific issues that may have contributed to the failure by searching, or visually scanning, through the Upgrade.log file for the following terms: fail error Page 120 of 146 After you identify and resolve the blocking issues, you can force a software upgrade to complete the configuration from the command line. After you have verified that the upgrade was successful by reviewing the upgrade log file, review the upgraded sites and notify site owners that their sites are ready for review. For more information about reviewing upgraded sites, see Review upgraded sites (Windows SharePoint Services). Important: In some configurations, the SharePoint Timer Service (OWStimer) account—which, by default, is the same account used by the SharePoint Central Administration v3 application pool account—is configured with credentials that do not have permission to access the LOGS folder in %COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\12\. If this is the case, part of the Upgrade.log is stored in the temporary storage folder of the account that is running the SharePoint Timer service. To avoid the possibility of deleting the upgrade log file when you restart the server computer, copy Upgrade.log to another location. To write all available logging information, including verbose output and detailed debugging information, to the log files for the software update installation, run the following command: msiexec /p <PatchPackage> /l*vx %temp%\patch.log Where PatchPackage is the path to the software update log file. You can find the log file in the temporary file location with the file name msi*.log. Tip: By default, every time you run an upgrade, the information about that upgrade is added to the same upgrade log file. If you are running upgrade multiple times, rename the log file after each upgrade, so that you can review only the information about the current upgrade. Force a software upgrade If the installation was unsuccessful, you can run the SharePoint Products and Technologies Configuration Wizard again, or you can use the following procedure to complete the configuration from the command line. Note: You can enable Windows Installer logging before you start the software upgrade installation again. To enable logging for Windows Installer, see Microsoft Knowledge Base article 99206: How to enable Windows Installer logging (http://go.microsoft.com/fwlink/?LinkID=99206). To force a software upgrade 1. Open a Command Prompt window and change to the following directory: Page 121 of 146 %COMMONPROGRAMFILES%\Microsoft shared\Web server extensions\12\Bin\ 2. Type the following command: psconfig –cmd upgrade –inplace v2v –wait –force View the Servers in Farm page In addition to viewing the upgrade log, you can verify that the update was successful by using the SharePoint Central Administration Web site to view the version number on the Servers in Farm page. For more information about verifying that each server in the farm has been updated to the new binary version, see Deploy software updates for Windows SharePoint Services 3.0. Page 122 of 146 Review upgraded sites (Windows SharePoint Services) Topic Last Modified: 2009-01-29 After upgrading a site collection by using the gradual upgrade option, keep the original sites online for a period of time so that the upgraded sites can be reviewed and verified against the original sites. During this time, IT administrators, site owners, designers, and developers can review the sites and have a chance to do the following: Note: Because the URLs of the old sites are changed during a gradual upgrade, be sure to include the URL when you notify site owners that their sites are ready for review. The Site Content Upgrade Status page lists the URLs for the previous and new version sites. Compare the old site to the new site and look for any discrepancies or errors. For example, check all hyperlinks. In particular, hard-coded URLs may not work. Copy missing components, if any, from the old site to the new site by using a SharePointcompatible Web page editor, such as Office SharePoint Designer. Update or re-deploy any Web Parts that no longer function correctly. If you have a problem with a Web Part, append "contents=1" at the end of the URL syntax (http://siteurl/?contents=1), and then press ENTER. This takes you to the Web Part Maintenance page where you can remove and repair the broken Web Part page. Note: If you check out a page to make changes, ensure that you check in the page again. Determine whether any pages need to be reset to the site definition version. If you have pages that have been customized, and do not show the new version's functionality, you should consider resetting the pages to the site definition to apply the new version's look and functionality, and then reapplying your customizations. You can perform this step from the Site Settings page in your site, and you can reset either individual pages or the entire site. Page 123 of 146 If pages do not render, you can check the Site Settings page by going directly to the URL syntax (http://siteurl/_layouts/settings.aspx). If the Site Settings page works and the upgrade has succeeded, then there might be issues with the master page or home page. If the Site Settings page does not work, go to the log file to see if you can get more information about the problem. The log files are located at %COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\12\LOGS. If necessary, revert to the version 2 site. For more information, see Revert to a previous version site (Windows SharePoint Services). Download this book This topic is included in the following downloadable book for easier reading and printing: Upgrading Windows SharePoint Services See the full list of available books at Downloadable books for Windows SharePoint Services. Page 124 of 146 Revert to a previous version site (Windows SharePoint Services) Topic Last Modified: 2007-12-13 If you want to discard the results of a gradual upgrade for a particular site and revert to the previous version site, you can do so by using the procedure below. Note that reverting to the previous version site deletes the upgraded site, so be sure to copy any elements you might need from the upgraded site (by using a Web Page editor that is compatible with Windows SharePoint Services 3.0 such as Microsoft Office SharePoint Designer 2007) before you perform this action. After you have made any necessary changes in the previous version site, you can try upgrading the site again. 1. In Central Administration, on the Operations tab, under Upgrade and Migration, click Site content upgrade status. 2. On the Site Content Upgrade Status page, next to the URL that contains the site you want to revert, click Continue upgrade. 3. On the Site Collection Upgrade page, on the Actions menu, click Revert site. 4. On the Revert to Non-Upgraded Site page, in the Select Upgrade Site Collection section, in the Site Collection box, click the down arrow and click Change Site Collection. 5. On the Select Site Collection page, click the URL for the site collection you want to revert, and then click OK. 6. On the Revert to Non-Upgraded Site page, then click Continue. Download this book This topic is included in the following downloadable book for easier reading and printing: Upgrading Windows SharePoint Services See the full list of available books at Downloadable books for Windows SharePoint Services. Page 125 of 146 Troubleshoot and resume upgrade (Windows SharePoint Services) Topic Last Modified: 2009-02-05 In this article: General information about troubleshooting and restarting upgrade Known issues for pre-upgrade scanning Known issues for in-place upgrade Known issues for gradual upgrade Known issues for database migration Known issues for customized sites General information about troubleshooting and restarting upgrade If upgrade stops, you can use the following methods to troubleshoot the issues: Look for the word "error" in the upgrade log files. The upgrade log files are located at %COMMONPROGRAMFILES%\Microsoft Shared\web server extensions\12\LOGS. For more information about viewing the upgrade log, see Verify upgrade (Windows SharePoint Services). Tip: Use the Search Files and Folders feature of Windows to find iterations of “error” quickly in these log files. Review the events in Event Viewer and look for any application errors. Review the readme file for known issues and workarounds. Errors are often issues that you can work around. If you are running Gradual Upgrade, check to see if the site collections you were running have appeared in the new version. If so, you can perform the workaround there, or revert the v3 site to v2, and try to upgrade the site again. For more information about reverting sites, see Revert to a previous version site (Windows SharePoint Services). In-place upgrade can be restarted using the command stsadm –o upgrade. Upgrade will skip those tasks that were already complete, and continue from where it left off. For more information about the upgrade operation, see Upgrade sites (Windows SharePoint Services). Page 126 of 146 Known issues for pre-upgrade scanning Upgrade is blocked if you use Localhost as your server name Using "localhost" as your server name can cause many issues in your environment and is not recommended. If you are using "localhost" as your server name, when you run the pre-upgrade scan tool, this issue is logged and the upgrade cannot proceed. You must rename the server computer and then run an operation in prescan before you can continue with the upgrade. Follow the steps below to rename your server and fix the issue for the pre-upgrade scan tool. 1. Back up the configuration database. 2. From the command line, change to the following path: %COMMONPROGRAMFILES%\Microsoft Shared\web server extensions\60\bin, and then run the following command to change the server name in the configuration database: Stsadm.exe -o setconfigdb -databaseserver <server name> -connect 3. From the command line, change to the following path: %COMMONPROGRAMFILES%\Microsoft Shared\web server extensions\12\bin, and then run the following command to clear the issue for the pre-upgrade scan tool: Prescan /fixlocalhost 4. On the command line, run the following command to re-run the pre-upgrade scan process: Prescan /all If it is successful, proceed with upgrade. If it still fails, then there is still a service using the localhost servername. At this point, upgrade is not blocked, but some services may not upgrade successfully. Page 127 of 146 Known issues for in-place upgrade You must use a domain account, not Network Service, for server farm upgrades For either in-place or gradual upgrade in a server farm environment, you should use the same credentials that you used in the version 2 environment in your version 3 environment. However, if you were using the Network Service account for your version 2 environment, you must instead use a domain account in version 3. Your version 2 environment can continue using Network Service, but when you install version 3 and create the new farm, you must supply a domain account instead. Be sure that you grant the domain account that you use the appropriate rights to the databases in SQL Server (must be a member of the database creators, process administrators, and database owners group for all version 2 databases). Some settings are not preserved on the Web application when you perform an in-place upgrade If you use Secure Sockets Layer (SSL) and perform an in-place upgrade, you must use the Alternate Access Mapping (AAM) feature to modify the URL within Windows SharePoint Services because some settings are not preserved on the Web application. Before you upgrade, if you have an AAM entry that uses HTTPS, such as the following: Incoming URL: https://<server name> Outgoing URL: https://<server name> After you perform an in-place upgrade of Windows SharePoint Services 3.0, this entry will be incorrectly set to: Incoming URL: https://<server name> Outgoing URL: http://<server name> To correct the URL, on the SharePoint Central Administration Web site, on the Operations page, click Alternate Access Mappings, and then click Edit Public URLs to set the URL back to: Incoming URL: https://<server name> Outgoing URL: https://<server name> For more information about alternate access mappings, see Plan alternate access mappings (Windows SharePoint Services). Upgrade finishes on the first front-end Web server but has failures Page 128 of 146 In a farm that uses multiple front-end Web servers, if the upgrade finishes on the first front-end Web server but has failures, we recommend that you solve the problem and rerun the upgrade before you move on to upgrade any additional front-end Web servers. If, for some reason, you want to disregard the failure (for example, because the failure has to do with a rarely used site collection), you can move on to upgrade the second front-end Web server by using the Psconfig command-line tool. Use the following command-line operation: Psconfig -cmd upgrade -inplace b2b -wait -force Note: You cannot use the SharePoint Product and Technologies Configuration Wizard to upgrade additional front-end Web servers if you use the Psconfig command-line tool. SPConfigurationDatabase2 sequence error in the upgrade log If you perform an in-place upgrade and it fails, check Upgrade.log, which is located in the COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\12\LOGS folder. If you receive the following error message: “[SPConfigurationDatabaseSequence2] [ERROR] [date]: The role 'WSS_Content_Application_Pools' already exists in the current database,” you can use any of the following workarounds to solve the problem: Run the following SQL queries on the configuration database. delete from dependencies delete from objects delete from classes delete from sitemap exec sp_droprole N'WSS_Content_Application_Pools' Note: If the drop role has any members when the action failed, the sp_droprole call returns the names of those members. You must then run the following command for each member. exec sp_droprolemember N'WSS_Content_Application_Pools', N'usernameReturnedFromSP_DropRole' Then you must run the following query again. exec sp_droprole N'WSS_Content_Application_Pools' Create a new V3 farm, and then attach the existing content database. This option will retain all the user data, but will lose configuration information that was stored in the V2 configuration database, such as Web Part packages and virtual server settings. If the original failure was addressed (for example, the failure was due to lost network connectivity or insufficient SQL Server computer disk space and then corrected), you can restore the V2 farm and then restart the upgrade. Page 129 of 146 Note: Remember to restart the upgrade after you have performed the workarounds. For in-place upgrades on stand-alone servers, run upgrade from the command-line if you get an error with a login failure or connection failure to the database If you are running an in-place upgrade on a stand-alone server running WMSDE, the upgrade process might time out and generate an error similar to the following: SPContentDatabaseSequence] [ERROR] [10/18/2006 12:42:44 PM]: Cannot open database "STS_DATABASE_NAME_1" requested by the login. The login failed. Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. [SPContentDatabaseSequence] [ERROR] [10/18/2006 12:42:44 PM]: at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) If you see this error, or an error about a database connection failure, you must use the command-line to complete the upgrade. 1. Open a command prompt window and change to the following directory: %COMMONPROGRAMFILES%\Microsoft Shared\web server extensions\12\bin 2. Run the following command to resume and complete upgrade: psconfig -cmd upgrade -inplace v2v -force -wait For more information about using the psconfig.exe command-line utility, see Command-line reference for the SharePoint Products and Technologies Configuration Wizard (Windows SharePoint Services). Known issues for gradual upgrade You must use a domain account, not Network Service, for server farm upgrades For either in-place or gradual upgrade in a server farm environment, you should use the same credentials that you used in the version 2 environment in your version 3 environment. However, if you were using the Network Service account for your version 2 environment, you must instead use a domain account in version 3. Your version 2 environment can continue using Network Service, but when you install version 3 and create the new farm, you must supply a domain account instead. Be sure that you Page 130 of 146 grant the domain account that you use the appropriate rights to the databases in SQL Server (must be a member of the database creators, process administrators, and database owners group for all version 2 databases). Additional steps are required to gradually upgrade an SSL-only servers The gradual upgrade process uses a paired set of IIS Web sites to host the original (un-upgraded) site and new (upgraded) site. By default, the new site that is created does not use SSL. If you need this Web site to use SSL, you must perform additional steps during the gradual upgrade process to set the IIS settings and port number to be correct for SSL. Perform the following steps after you have created the target Web application for your sites, but before you upgrade any sites. For more information about creating the target Web application, see Create a new Web application to host upgraded sites in Upgrade sites (Windows SharePoint Services)). Change the port numbers and SSL settings in Internet Information Services (IIS) Manager 1. In Internet Information Services (IIS) Manager, click the plus sign (+) next to the server name that contains the Web application you want to change. 2. Click the plus sign (+) next to Web sites. 3. Right-click Default Web Site, and then click Properties. 4. On the Web Site tab, in the SSL port box, type 444, and then click OK. 5. Right-click Default Web Site_Pair, and then click Properties. 6. On the Web Site tab, in the SSL port box, type 443, and then click Apply. 7. On the Directory Security tab, in the Secure communications section, click Server Certificate. Follow the steps in the wizard to assign a new certificate. 8. On the Directory Security tab, in the Secure communications section, click Edit. 9. In the Secure Communications dialog box, select the Require secure channel (SSL) check box, and then click OK. 10. Click OK to close the Default Web Site_Pair Properties box. Update alternate access mapping settings and reset IIS 1. Open a command prompt window and change to the following directory: %COMMONPROGRAMFILES%\Microsoft Shared\web server extensions\12\bin. 2. Run the following command to change the alternate access mapping for the original Default Web Site to point to port 444: Stsadm -o addzoneurl -url https://server_name:port -urlzone default zonemappedurl https://server_name:444 Where server_name:port is the location for the Default Web site. 3. Change to the following directory: %COMMONPROGRAMFILES%\Microsoft Shared\web server extensions\60\bin. Page 131 of 146 4. Run the following command to change the alternate access mapping for the redirected Web site: Stsadm -o addzoneurl -url http://server_name:port -urlzone default zonemappedurl https://server_name:443 Where server_name:port is the location for the new site that was created when you created the target Web application. 5. Run the following command to reset IIS: iisreset /noforce I finalized the upgrade, but some sites were not upgraded yet, what can I do? If you have finalized the upgrade process, you can no longer use the gradual upgrade method to upgrade any remaining sites. You can, however, use the database migration approach to upgrade the sites. For more information about using database migration to upgrade sites after having finalized a gradual upgrade, see article 926718 in the Microsoft Knowledge Base (http://support.microsoft.com/kb/926718). I have selected the “Do not upgrade” option in the Setup screen, but I have now changed my mind and want to upgrade If you have selected the Do not upgrade option during Setup and change your mind after you run the SharePoint Products and Technologies Configuration Wizard, you must run the SharePoint Products and Technologies Configuration Wizard again to change to a gradual upgrade. Use the SharePoint Products and Technologies Configuration Wizard to change from the “Do not upgrade” option to a gradual upgrade 1. Run the SharePoint Products and Technologies Configuration Wizard to disconnect from the farm. 2. Go to %COMMOMPROGRAMFILES%\Microsoft shared\Web Server Extensions\12.0\WSS\ and change the registry key to V2V_GRADUAL_UPGRADE for SetupType and SetupTypeBackup. 3. Rerun the SharePoint Products and Technologies Configuration Wizard to perform the upgrade. Known issues for database migration You cannot add the same content database more than once to a farm, even on different Web applications Each site collection in a content database (including each portal site) has a globally-unique identifier (GUID) associated with it, registered in the configuration database. So, adding the same site collection (or portal) twice to the farm, even in separate Web applications, is not possible. Although the database attach succeeds in this situation, the site collection cannot be started. If you need a duplicate copy of a Page 132 of 146 site collection (or portal) in the same farm, first attach the database that contains the site collection to a separate farm, and then use the Stsadm.exe backup and restore operations to copy the site collection over to the other farm. The backup and restore process creates a new GUID for the site collection. Known issues for customized sites An application error can result when disallowed customizations are made to Web.config files Certain customizations are not allowed in Web.config files for subfolders within a virtual server. For example, the AUTHENTICATION and SESSIONSTATE nodes are not allowed within the Web.config file at this level. Modifying the Web.config file in ways that are not recommended can result in unexpected upgrade results. Be sure to follow the recommended practices for customizations, including customizations to the Web.config file. For more information, see Best Practices for Ensuring Application Reusability and Upgrade in Windows SharePoint Services on the MSDN Web site (http://msdn.microsoft.com/library/default.asp?url=/library/enus/odc_SP2003_ta/html/WSSSharePointCodeReuse.asp). Download this book This topic is included in the following downloadable book for easier reading and printing: Upgrading Windows SharePoint Services See the full list of available books at Downloadable books for Windows SharePoint Services. Page 133 of 146 Perform post-upgrade steps for an in-place upgrade (Windows SharePoint Services) Topic Last Modified: 2009-04-27 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: Remove Windows SharePoint Services 2.0 language packs. Reapply blocked file type settings. Page 134 of 146 After you have completed these steps, you can go on to Perform post-upgrade steps (Windows SharePoint Services). Note: If you uninstall Windows SharePoint Services 3.0 after upgrading from a Windows SharePoint Services 2.0 installation that used the Internet Information Service (IIS) default Web site, the default Web site will be deleted and you can not rollback to a working installation. For more information see Revert to a previous version site (Windows SharePoint Services). Remove Windows SharePoint Services 2.0 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. Note: Language packs for different languages will be made available at different times; check back periodically if you need a language that is not yet available. 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 (Windows SharePoint Services). Use the following procedure to reapply the blocked file type settings after you upgrade. Reapply blocked file type settings 1. Open the Notepad file that contains the file name extensions that you saved before the upgrade. 2. On the Edit menu, click Select All, and then click Copy. 3. In Windows SharePoint Services 3.0, on the Central Administration page, in the Security Configuration section, click Blocked file types. 4. 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. Note: The application allows duplicate file name extensions to appear on the list, so you do not need to delete anything. 5. Click OK to save the file. Page 135 of 146 Download this book This topic is included in the following downloadable book for easier reading and printing: Upgrading Windows SharePoint Services See the full list of available books at Downloadable books for Windows SharePoint Services. Page 136 of 146 Perform post-upgrade steps for a gradual upgrade (Windows SharePoint Services) Topic Last Modified: 2009-02-13 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: Delete any upgraded and confirmed previous version sites Remove Windows SharePoint Services 2.0 language packs Perform this step only when all sites using these language packs have been upgraded to the new version and are using Windows SharePoint Services 3.0 language packs. Reapply blocked file type settings Page 137 of 146 If you have upgraded all sites and you no longer need the original environment, then after you complete the steps below you can go on to Finalize upgrade (Windows SharePoint Services). Delete any upgraded and confirmed 2.0 sites After you have upgraded the original sites and confirmed that the upgraded instances of the sites are ready to use, you can start to clean up the 2.0 sites. You can delete the original sites in batches, as they are upgraded, and then continue to clean up upgraded sites over time. When all sites have been upgraded and are no longer needed, delete any remaining original sites, and then continue on to remove the language packs and then Finalize upgrade (Windows SharePoint Services). If some sites cannot be upgraded successfully, continue to run both versions side-by-side until the sites are no longer needed, or until you can migrate the content into a new site. You can use autodelete to automatically delete upgraded sites. Remove Windows SharePoint Services 2.0 language packs You must install the Windows SharePoint Services 3.0 language packs before you can upgrade sites in the corresponding 2.0 languages. After you have upgraded the sites to use the new language packs, you can remove the old version of the language pack. Note: Language packs for different languages will be made available at different times; check back periodically if you need a language that is not yet available. 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 (Windows SharePoint Services). Use the following procedure to reapply the blocked file type settings after you upgrade. Reapply blocked file type settings 1. Open the Notepad file that contains the file name extensions that you saved before the upgrade. 2. On the Edit menu, click Select All, and then click Copy. 3. In Windows SharePoint Services 3.0, on the Central Administration page, in the Security Configuration section, click Blocked file types. 4. 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. Page 138 of 146 Note: The application allows duplicate file name extensions to appear on the list, so you do not need to delete anything. 5. Click OK to save the file. Download this book This topic is included in the following downloadable book for easier reading and printing: Upgrading Windows SharePoint Services See the full list of available books at Downloadable books for Windows SharePoint Services. Page 139 of 146 Finalize upgrade (Windows SharePoint Services) Topic Last Modified: 2007-12-13 For an in-place or gradual upgrade, after all sites have been upgraded you can finalize the upgrade. Finalizing upgrade removes the connection to the previous version and cleans up any temporary data. After you finalize upgrade, you cannot go back to the farm upgrade process. Note: This content applies only to in-place and gradual upgrade processes. There is no finalize upgrade step for database migrations. 1. In Central Administration, on the Operations tab, under Upgrade and Migration, click Finalize upgrade. 2. On the Finalize Upgrade page, read through the information; if you are ready to finalize, click Complete Upgrade. 3. Click OK to finalize upgrade. Download this book This topic is included in the following downloadable book for easier reading and printing: Upgrading Windows SharePoint Services See the full list of available books at Downloadable books for Windows SharePoint Services. Page 140 of 146 Migrate content or sites after upgrade (Windows SharePoint Services) Topic Last Modified: 2008-10-28 In this article: Migrate content by using import/export Migrate a site collection by using backup/restore After you have completed the upgrade process, you can redistribute content or sites as needed to fit your new environment. It is easiest to move content or sites before you open the sites to users again, so that they do not have to experience more than one outage window. If you want to redistribute sites among your content databases, you can use any of the following methods to perform this action: Import/Export Use this method to move a subsite into a different site collection, or to move an entire site collection to a different database or Web application. With import/export, you can choose whether or not to include security settings when you import. To migrate content by using this method, use the import and export operations with the Stsadm command-line tool. Note: You can import sites only into site collections that are using same language as the exported site. Backup/Restore Use this method to move an entire site collection to a different database or Web application. To migrate content by using this method, use the backup and restore operations with the Stsadm command-line tool. Content Migration application programming interfaces (APIs) Use this method to move smaller sets of data (down to the list or item level) between sites. For more information about using the Content Migration APIs, see Windows SharePoint Services 3.0 Software Development Kit (http://go.microsoft.com/fwlink/?LinkId=76000&clcid=0x409). Page 141 of 146 Migrate content by using import/export The import/export feature is based on the new Content Migration APIs. With import/export, you can migrate either subsites or entire site collections, and you can import a subsite into an existing site collection. Like the Smigrate.exe utility in the previous version, import/export requires that the site you import to already exists. Note that import/export does not include some site settings, such as Recycle Bin state and alerts. Note: You can import sites only into site collections that are using same language as the exported site. To use import/export to migrate a site or site collection, see Archive and retrieve content by using Stsadm import and export operations (Windows SharePoint Server 3.0). For more information about using import/export, see Stsadm command-line tool (Windows SharePoint Services). Migrate a site collection by using backup/restore If you want to migrate an entire site collection, you can do so by using the backup and restore operations with the Stsadm command-line tool. First, back up the site collection you want to move, then delete it from the current database and take the database offline. Then, restore the site collection to the new URL. Be sure that there is no site collection already at the new location, or the restore operation will fail. Note: If there is a site collection at the destination and you want to overwrite it, you can use the overwrite parameter with the restore operation. To use backup/restore to migrate a site collection, see Back up and restore site collections by using built-in tools (Windows SharePoint Services 3.0). Download this book This topic is included in the following downloadable book for easier reading and printing: Upgrading Windows SharePoint Services See the full list of available books at Downloadable books for Windows SharePoint Services. Page 142 of 146 Add servers to an upgraded farm (Windows SharePoint Services) Topic Last Modified: 2009-03-17 In this article: Add a front-end Web server to an upgraded server farm Add a back-end database server to an upgraded server farm When you add a front-end Web server to an upgraded farm, you need to install not only the files and components needed by Windows SharePoint Services 3.0, but also any files and components that were needed by Windows SharePoint Services. To accomplish this, you can sometimes manage — with the help of a good checklist — to install all of the files and components that you need to get your sites working correctly on a new front-end Web server. However, there are some cases in which installing such components will not work. For example, you may have Web Parts installed that were designed for Windows SharePoint Services but that cannot be installed on a server running Windows SharePoint Services 3.0 (because you are running a newer version of ASP.NET). However, if they are already installed when Windows SharePoint Services 3.0 is installed, the Web Parts may continue to work. Caution: Do not add servers to your farm during the upgrade process. Either add them before beginning the upgrade, or wait until the upgrade is complete to add servers. Specifically, if you add a server to the farm while the SharePoint Products and Technologies Configuration Wizard is being run on any server in the farm, the new server will not appear in the upgraded topology. This is because the configuration database — which contains the information about which servers are in a farm — is the first item upgraded by the configuration wizard, and any servers not included in the configuration wizard at that time will not be registered in the configuration after the upgrade. Because you need both the previous and the current versions' files and components, the easiest way to add a server to a farm is to take an image of one of the existing servers in your farm (by using any of the tools available for imaging hard disks) and restore it to the new server, then run the SharePoint Products and Technologies Configuration Wizard to add the new server to the farm. This way, you have a snapshot of the upgraded state of the server, complete with any of the files or components you need in order for the sites to render correctly. Important: Make sure that the image of the server that you use to add a server to a farm has the same software update version applied as all of your Web servers. In server farm deployments, all your Page 143 of 146 Web servers must have the same software update version applied. For more information, see Deploy software updates for Windows SharePoint Services 3.0. Add a front-end Web server to an upgraded server farm Perform these steps on a server that has been prepared with an image taken from another front-end Web server in your farm. You can add a front-end Web server by using the SharePoint Products and Technologies Configuration Wizard or the Psconfig command-line tool. Use the following procedure to use the SharePoint Products and Technologies Configuration Wizard to add a front-end Web server to your upgraded farm. Add a front-end Web server to an upgraded server farm by using the configuration wizard 1. Click Start, point to All Programs, point to Administrative Tools, and then click SharePoint Products and Technologies Configuration Wizard. 2. In the SharePoint Products and Technologies Configuration wizard, on the Welcome to SharePoint Products and Technologies page, click Next. A message appears, notifying you that Internet Information Services (IIS), the SharePoint Administration Service, and the SharePoint Timer Service may need to be restarted or reset during configuration. 3. Click Yes to continue with the wizard. 4. On the Connect to a server farm page, select Yes, I want to connect to an existing server farm, and then click Next. 5. On the Specify Configuration Database Settings page, in the Database server box, type the name of the database server used for the farm you are connecting to, and then click Retrieve Database Names. 6. In the Specify Database Access Account section, type the user name and password to use to connect to Microsoft SQL Server, and then click Next. Note: This account must have rights to create databases. If SQL Server is running on a server that is separate from your front-end Web server, then this account must also be a domain account. This user account must be a member of the following SQL Server security roles: Database Creator and Security Administrator. 7. On the Completing the SharePoint Products and Technologies Configuration wizard page, verify the settings, and then click Next. The configuration wizard runs. 8. On the Configuration Successful page, review the settings that have been configured, and then click Finish. Page 144 of 146 Use the following procedure to use the Psconfig command-line tool to add a front-end Web server to your upgraded farm. Add a front-end Web server to an upgraded server farm by using the command line 1. Open a command prompt window and change to the following directory: %COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\12\bin 2. Run the following command: psconfig –cmd configdb –connect –server <database_server> -database <database_name> Note that the database_name above should be the name of the configuration database for the upgraded farm you want to connect to. For more information about adding a front-end Web server to your server farm, see Deploy Windows SharePoint Services 3.0 in a server farm environment. Add a back-end database server to an upgraded server farm For a database server, you do not need to use an image from another server in your server farm. You can simply install SQL Server and then join the server to the farm. For more information about adding a database server to your server farm, see Deploy Windows SharePoint Services 3.0 in a server farm environment. Page 145 of 146 Page 146 of 146
