MCT USE ONLY. STUDENT USE PROHIBITED Planning for Upgrading to SharePoint 2010 15-33 Gathering Information about the Current Environment Key Points There are several tools that you can use to gather information about the current environment so that you can plan the upgrade better. These have been enhanced because Office SharePoint Server 2007 has the potential to include a large array of customizations. These tools are primarily designed to help you discover the composition of your Office SharePoint Server 2007 deployment. Many of these tools ship with Office SharePoint Server 2007 SP2. Pre-Upgrade Checker Tool You run this utility with the stsadm command. You can run the command against the entire farm or against individual servers in the farm. The utility reads SharePoint database information but makes no changes to your environment. You can therefore run and rerun the utility as many times as you want to review changes that you make. The command generates an XML log, a text log, and an HTML report. It provides two different types of information: MCT USE ONLY. STUDENT USE PROHIBITED 15-34 Designing a Microsoft® SharePoint® 2010 Infrastructure • Information report: • Farm servers • Databases • Alternative address mapping configuration • Site definitions • Features • Web Parts • Event receivers • Installed language packs • Issue report • Missing site definitions • Missing features • Missing assemblies • Data orphans • Modified content databases The Pre-Upgrade Checker provides reference links to Knowledge Base articles that will support you in using the tool. You do not have to run the Pre-Upgrade Checker tool before you upgrade, as was the case with PreScan for Office SharePoint Server 2007. However, you are strongly advised to do so. Gathering Information about Sites There are several tools for gathering information about sites. Although it may seem surprising to some, most farm administrators are not aware of all of the sites that exist in their Office SharePoint Server 2007 farms. The stsadm –o EnumAllWebs command provides a list of all of the sites that exist in a farm. SPDiag V2 ships with the SharePoint Administration Toolkit. This can help you to identify customizations and custom settings in the current environment. SPDiag V2 is designed to collect and review data from SharePoint Web servers, application servers, and computers running Microsoft SQL Server®, which it stores in a SQL Server database for analysis. SPDiag V2 can collect performance data from: • Internet Information Services (IIS) logs. • Unified Logging Service logs. MCT USE ONLY. STUDENT USE PROHIBITED Planning for Upgrading to SharePoint 2010 15-35 • Performance counters. • Windows Management Instrumentation (WMI). You can display data in the Trends pane of the SPDiag interface and use filters to reveal trends, bottlenecks, and other performance issues. You can also view the individual components and the logical structure of the farm in the Snapshot pane. Gathering Information about Customizations If your organization has deployed customized InfoPath form solutions, you should plan to run the stsadm -o ExportIPFSAdminObjects command. In these cases, a globally unique identifier (GUID) is inserted into the configuration database for which you may not have installation source code. The command gathers the deployment information, which you can then export for application if you perform a database attach upgrade. Gathering Information about Content Databases For content databases, you should plan to use the new Test-SPContentDatabase command. This tool tests the combination of a content database and the Web application. Again, this does not modify a database. You can run this on Office SharePoint Server 2007 and SharePoint 2010 prerelease versions. The report that this tool generates provides information about: • Current or potential issues. • Data orphans. • Missing site definitions. • Missing features. • Missing assemblies. The report also shows table sizing metrics. There are also several Windows PowerShell™ commands that your administrators can use during the upgrade process. Although these are not necessarily important to your planning, you should ensure that the upgrade team is aware of the function and use of the following commands: • Upgrade-SPContentDatabase • Upgrade-SPEnterpriseSearchServiceApplication • Upgrade-SPSingleSignOnDatabase MCT USE ONLY. STUDENT USE PROHIBITED 15-36 Designing a Microsoft® SharePoint® 2010 Infrastructure Cleaning Up the Current Environment Key Points You should always plan a system cleanup prior to an upgrade. Often, people regard the upgrade itself as the system cleanup; it is a chance to start again and leave behind issues from the previous version. If you fail to clean up your environment prior to upgrade, you may find that the problems from the past quickly become the problems of the present. You can minimize time and issues by removing components and content that you do not use. Always perform a full backup before you delete content or customizations that you believe are no longer used. As part of your upgrade, you should perform the following actions: • Delete unused sites and Web applications. This reduces the time for the upgrade and may remove potential customization problems. • Remove unnecessary document versions. This reduces the volume of data and will reduce upgrade time. MCT USE ONLY. STUDENT USE PROHIBITED Planning for Upgrading to SharePoint 2010 15-37 • Clean up templates, features, and Web Parts. This removes customizations that your organization no longer uses and will minimize the number of customization issues. This is particularly important if you plan to perform an in-place upgrade. • Repair data issues. You should identify problems such as undeletable sites or lists. There are additional tools in Office SharePoint Server 2007 SP2 and cumulative updates that administrators can use for problems such as these. The tools include the following commands: • stsadm -o DatabaseRepair [-deletecorruption] • stsadm -o ForceDeleteList • stsadm -o VariationsFixupTool MCT USE ONLY. STUDENT USE PROHIBITED 15-38 Designing a Microsoft® SharePoint® 2010 Infrastructure Planning the Upgrade Schedule Key Points Your upgrade is a long-term project. Most people only regard the upgrade as starting when you begin the first data backup; this is realistically the conclusion of your upgrade planning. You should spend far more time in planning and discussion than you spend in performing an upgrade. You must treat your upgrade as you do any large project. Assemble your team, which should include someone with project management experience. You should have an initial schedule, which defines the top-level activities and the key dates on which you must complete them to deliver the upgrade at the agreed time. You can keep this schedule information in an Excel 2010 workbook, but most upgrade projects are better organized in a Gantt chart. This is because all upgrades involve a team of business and technical staff and a number of interrelated steps. It is important to be able to track dependencies in this sort of project. MCT USE ONLY. STUDENT USE PROHIBITED Planning for Upgrading to SharePoint 2010 15-39 Establishing Upgrade Milestones Each milestone is associated with a series of dependent or independent activities, each of which you must complete before you can achieve the milestone. For anything less than the most trivial upgrade—a test environment—you should create a project plan that associates all milestones with activities and all activities with a named person who is responsible for them. You must also specify a completion date for each activity. If you follow this practice, you will find it possible to manage and preempt issues. Planning for Risk Management You should always plan for problems. This means that you provide additional time to ensure that you can deliver against your plan, even if problems occur; experience shows that you can never have too much time allocated to an upgrade project. It is notoriously difficult to give an exact timescale for an upgrade project. However, if you find that you are running ahead of schedule, you have an opportunity to reschedule the upgrade for an earlier date. The list of activities is too extensive to post here, and they are often specific to a company. The best way to test your plan is to perform a dry run in a meeting of the project team with an independent project manager acting as assessor or mentor. This independent view can ensure that you do not miss anything critical, such as ordering 64-bit equipment in time for the upgrade date. MCT USE ONLY. STUDENT USE PROHIBITED 15-40 Designing a Microsoft® SharePoint® 2010 Infrastructure Documenting the Upgrade Plan Key Points You must document your upgrade plan in detail. A good way to document the upgrade plan is by using a worksheet. A worksheet can help you marshal the key upgrade information for an existing farm and establish the high-level steps that are necessary to complete your upgrade projects. The columns in the worksheet should include: • Farm. The name, or identifier, of the farm that you plan to upgrade. • Site name. The name of the site to which you will upgrade. • Parent site. The name of the parent site or Web application. • Site URL. The URL for the site, based on the parent site prefix. • Purpose. A description of the purpose of the site. • Template. The template that was used to create the site. This is useful for identifying templates that may have been deprecated by Microsoft. • Version. The current version of Microsoft Office. MCT USE ONLY. STUDENT USE PROHIBITED Planning for Upgrading to SharePoint 2010 15-41 • Content database name. The name of the current content database. • Customizations. A list of the customizations on the site, such as Web Parts, master pages, and site templates. This does not specify the particular Web Part or master page, which you should detail in a separate document. • Operating system version. The Windows operating system server version and service pack level. • SQL Server version. The SQL Server version and service pack level. • Upgrade approach. The preferred upgrade option—database attach, in-place, or hybrid. • Upgrade steps. The high-level steps for completing the upgrade. Note that this document assumes that elements such as requirements gathering have already been completed. There should be a more detailed plan that breaks each of these steps into procedures. • Target Web application. The URL for the target Web application. The goal of the upgrade planning worksheet is to gather all of the core data in a single place. For highly complex or large upgrades, you should create additional documentation that details planning steps for specific issues. Additional Reading For more information about planning worksheets, see http://go.microsoft.com/fwlink/?LinkID=200926&clcid=0x409 and http://go.microsoft.com/fwlink/?LinkID=201265&clcid=0x409. MCT USE ONLY. STUDENT USE PROHIBITED 15-42 Designing a Microsoft® SharePoint® 2010 Infrastructure Lesson 3 Upgrade Considerations An upgrade plan provides the high-level steps for a project and possibly some detailed elements. There are several technical and business elements that also have an effect on the plan, such as minimizing production downtime. You should always create your upgrade plan and then review your plan with reference to these considerations. Your plan must also reflect consideration for how the upgrade will affect users. SharePoint 2010 ships with several IT and user options that will affect how you perform and then manage the entire upgrade experience for IT staff and information workers. You must always remember that the reason for upgrading is to enhance the productivity of the business, not just to have the latest version. Objectives After completing this lesson, you will be able to: • List the hardware requirements for the upgrade. • List the software requirements for the upgrade. . PROHIBITED 15 -34 Designing a Microsoft SharePoint 20 10 Infrastructure • Information report: • Farm servers • Databases • Alternative address mapping configuration • Site definitions • Features. and the Web application. Again, this does not modify a database. You can run this on Office SharePoint Server 20 07 and SharePoint 20 10 prerelease versions. The report that this tool generates. upgrade. Gathering Information about Content Databases For content databases, you should plan to use the new Test-SPContentDatabase command. This tool tests the combination of a content database