MCT USE ONLY. STUDENT USE PROHIBITED Planning for Upgrading to SharePoint 2010 15-13 Data Migration Data migration is the third upgrade strategy that is available when you move from old to new Office SharePoint environments. This is very similar in process and goals to the database attach option. The process of data migration involves the creation of a new SharePoint 2010 farm environment and the movement (or migration) and addition of the existing site databases to the new installation. When you add databases to the new installation, the upgrade process automatically upgrades them. Data migration is considered to be the same as an in-place upgrade; however, the changes are made on a copy of the content rather than the content. Office SharePoint Portal Server 2003 For Office SharePoint Portal Server 2003 updates, you must first upgrade the farm to Office SharePoint Server 2007 SP2. The options are the same as for Windows SharePoint Services 2.0 upgrades. For Office SharePoint Portal Server 2003, you must create upgrade definition files for translating the page templates into new page layouts. This is because page layouts replace page templates in the new site architecture, and you must specify which page layout to use for each page type. During the pre-upgrade process, you deploy 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. Windows SharePoint Services 3.0 When you plan to upgrade Windows SharePoint Services 3.0 to Microsoft SharePoint Foundation 2010 or SharePoint 2010, you should first install the latest service pack and cumulative updates on the farm servers. The service pack provides the Pre-Upgrade Checker tool, which you can use to scan your farm to identify possible issues. You should resolve any issues that the Pre-Upgrade Checker report identifies before you proceed to an in-place or database attach upgrade to the required version of SharePoint 2010. With the farm servers at the appropriate software levels, you can choose to complete an in-place or database attach upgrade. Again, the most common choice is to perform a database attach upgrade, unless you have a small and discrete farm. You should make a new backup of content databases before you start any upgrade, because the schema will have changed during the upgrade process. To continue, you must build a SharePoint 2010 farm with the appropriate Web applications and configuration to match your site requirements. You can then attach the content database and complete the upgrade. Deploy any customizations, such as custom master pages, to the site when you have completed the upgrade process. MCT USE ONLY. STUDENT USE PROHIBITED 15-14 Designing a Microsoft® SharePoint® 2010 Infrastructure Office SharePoint Server 2007 If you are upgrading an Office SharePoint Server 2007 or Office SharePoint Server 2007 SP1 farm, you should first upgrade to the latest service pack and then run the Pre-Upgrade Checker tool. This process is then the same as the upgrade path for Windows SharePoint Services 3.0. Additional Reading For more information about how to plan and prepare for upgrade to Office SharePoint Server 2007 and the tools that are available to support you, see http://go.microsoft.com/fwlink/?LinkID=200924&clcid=0x409. MCT USE ONLY. STUDENT USE PROHIBITED Planning for Upgrading to SharePoint 2010 15-15 Upgrade Considerations Key Points There are a number of solution-specific options that you should review when you plan an upgrade. Business Data Catalog Upgrades If you have Office SharePoint Server 2007 applications that run the Business Data Catalog (BDC), you must make specific plans for upgrade or migration. The service application models are different for BDC and Microsoft Business Connectivity Services (BCS), so there will be a number of changes. You can perform an in-place upgrade, or you can choose the database attach option, which involves greater configuration effort. Note: The acronym BDC is used in this section to describe the Office SharePoint Server 2007 Business Data Catalog Service. The acronym BCS is used to describe SharePoint 2010 Business Connectivity Services and all associated services, including the Business Data Connectivity Service. MCT USE ONLY. STUDENT USE PROHIBITED 15-16 Designing a Microsoft® SharePoint® 2010 Infrastructure When you perform an in-place upgrade of a farm that uses BDC, you automatically create a BCS instance. This will have associated service databases for BCS and the Application Registry Service, which directly replaces the BDC from Office SharePoint Server 2007 and supports the backward compatibility of solutions that are based on BDC. The Application Registry Service supports Office SharePoint Server 2007 applications that include: • Custom Web Parts • Custom code • Searching A copy of each application definition in BDC is added to the Application Registry Service, and an upgraded version is added in BCS. If you perform a database attach upgrade, you must plan to upgrade BDC individually, by first exporting the application definitions from the Office SharePoint Server 2007 BDC. After you complete the upgrade, you must update the solution to use BCS and import the updated BDC models into the Business Data Connectivity Service. Search It is important to understand that the Search Service is not upgraded when you use the database attach upgrade option. If your organization uses Office SharePoint Search, you must identify any customizations and prepare to redeploy them. These customizations may include: • Custom protocol handlers. • Custom iFilters. • Modifications to managed properties. • Custom word-breakers. • Custom thesauruses. • Customized noise-word files. • Custom security trimmers. You should also recrawl content databases when you upgrade. Depending on your content volumes and the dependence of your business on search, you must plan for appropriate time to completely reindex your environment. MCT USE ONLY. STUDENT USE PROHIBITED Planning for Upgrading to SharePoint 2010 15-17 Excel Services For the database attach upgrade approach, you must reconfigure Excel Services in your new farm. InfoPath Forms If you plan to use a database attach option, you must plan to reinstall any Microsoft InfoPath® forms that are currently used in your environment. Irrespective of the upgrade approach, you should review and test all forms. You should check specifically for forms that use fully qualified URLs and any forms that are packaged with custom assemblies. The command stsadm -o exportipfsadminobjects exports administrator-approved form templates and data connection files that are stored in the Office SharePoint Server 2007 or Microsoft Office Forms Server 2007 configuration database. Language Packs SharePoint 2010 ships in a number of localized SKUs. During the installation process, installers will be prompted to choose which language they want to use. The decision that they make here will influence the language that Central Administration uses. In addition, various language templates will be made available to enable an environment to support languages other than the language in which the initial installation was performed. You must be fully aware of the language requirements for your environment, particularly in a global deployment. Feature Upgrades Office SharePoint Server 2007 included a move toward the use of features in the product. SharePoint 2010 includes a feature upgrade capability. There is a version section in the XML of each Feature.xml file, where you can declare the version number of the feature. You can use this to specify whether the upgrade should use a newer version of a feature. If no version is declared in the file, the features are maintained and used in their current form. Additional Reading For more information about how to export application definitions, see http://go.microsoft.com/fwlink/?LinkId=189010. For more information about how to manage BDC models in SharePoint 2010, see http://go.microsoft.com/fwlink/?LinkID=200925&clcid=0x409. MCT USE ONLY. STUDENT USE PROHIBITED 15-18 Designing a Microsoft® SharePoint® 2010 Infrastructure For more information about Excel Services administration, see http://go.microsoft.com/fwlink/?LinkID=201263&clcid=0x409. For more information about upgrading forms templates, see http://go.microsoft.com/fwlink/?LinkID=201264&clcid=0x409. MCT USE ONLY. STUDENT USE PROHIBITED Planning for Upgrading to SharePoint 2010 15-19 Considerations for Migration from Other Platforms Key Points There are two key types of migration from non-SharePoint platforms to SharePoint 2010: • Application migration • Content migration Application migration involves the movement of application logic into a SharePoint 2010 environment. Content migration is concerned with the movement of data rather than business logic. It is far easier to migrate data than logic, because you can assume that most applications reflect business logic that the application itself is able to reproduce. You should review any request for an application migration to check whether it would be easier to re-create the application based on current requirements than to migrate the requirements that must, by definition, have been established in the past. MCT USE ONLY. STUDENT USE PROHIBITED 15-20 Designing a Microsoft® SharePoint® 2010 Infrastructure These two options can be extreme. For example, you may have raw documents that you just need to move to a document library, or you may have complex business logic that will take a great deal of effort to migrate. For users, it may seem obvious to migrate because they already have an application that they know. However, you will almost always find that an application migration leads to some loss of function, even if new functionality is available. You should also establish whether an application is an off-the-shelf solution or a heavily customized solution. File Shares You should concentrate your planning effort on the delivery of functionality to users. The data is easy to move; file shares contain files and documents, which generally have no interdependencies or links to external sources. An obvious exception may be worksheets in Microsoft Office Excel that may have embedded links to external data sources. You can ask users to identify such additional complexities to ensure that you can plan for data access or file modification. Data Types You must understand the type of data that you are going to migrate. You may find that file shares are more appropriate for a particular file type, such as virtual images or very large files that will gain little from content management features such as check-in, check-out, or versioning. SharePoint 2010 can hold these files through the remote binary large object (BLOB) storage functionality. However, you must establish whether this provides a business benefit. Security and Structure More complex considerations for file shares are the depth of hierarchy and the current application of access control lists (ACLs). Office SharePoint provides access through URLs. If your file share has very long folder and file names or very deep folder hierarchies, you may not be able to manage these because the URLs may become too long. If a file share has complex ACLs and inheritance, you will find that a direct security mapping is not a trivial task. You can leave this as a self-service option, so users migrate files to SharePoint sites as they require them. Be aware that the creation date of a file will change when you migrate to SharePoint 2010. If file creation or modification dates are important for regulatory compliance, you can create a new SharePoint document library for new content and treat the existing content as an historical archive. Remember to plan for any search issues that are associated with document interrogation. MCT USE ONLY. STUDENT USE PROHIBITED Planning for Upgrading to SharePoint 2010 15-21 Microsoft Exchange Public Folders For Microsoft Exchange public folders, there are out-of-the-box forms for migration of entities such as contact lists directly into SharePoint 2010. As with shared folders, it is unusual for you to find links between documents. ACL management is more complex, because Microsoft Exchange has a different ACL model. It gives rights based on e-mail addresses rather than Active Directory® directory service service tokens. You may have to manually map between these two, which can be a considerable effort. Public Folder Analysis One of the main difficulties can be the analysis of your public folders; these may not be well documented, especially if the environment has been in service for a long time. You may find that the effort involved in public folder analysis is difficult to justify in terms of time and resources. On a more technical level, you must plan for the types of documents that you commonly find in a public folder. For example, it is common to embed images, such as print screens, in e-mails. However, this is not easy to represent in HTML because a print screen is a Component Object Model (COM) component object. Compound documents—files that contain files—may also require a lot of planning. You can save these as .msg files, but users must have the Microsoft Office Outlook® client to view these. Web Content Management Content If you have a request to migrate from an existing Web content management system, you must plan the move based on the complexity of this environment. For example, it is easy to move Web pages and image libraries directly into SharePoint 2010, but you must ensure that there are no environment-specific or application- specific components that the users assume will migrate, such as page layouts. You can re-create these, but it will take effort, so your plan should include analysis of such requirements. Solution components such as navigation, Web Parts, and applets can cause difficulties. You should plan for a developer or development team to review these to estimate any time that you may need to budget for re-creation of components. MCT USE ONLY. STUDENT USE PROHIBITED 15-22 Designing a Microsoft® SharePoint® 2010 Infrastructure Third-Party Platforms Far more complex—and probably out of the scope of an upgrade plan—is migration from another application platform to SharePoint 2010. For example, if you have a request to migrate from Lotus Domino, you should treat this as a separate project. Migration of content, such as forms-based data, is relatively simple. However, you may find that you have well-established or business-critical systems that may be included in a data migration project. You should not permit this to become part of the general upgrade plan. Instead, you should establish a new project with new budget, schedules, and success criteria, because a complex application migration may extend your overall migration effort and impact overall productivity. If you must migrate from an external platform, you should check for available tools to assist you in complex projects. . software levels, you can choose to complete an in-place or database attach upgrade. Again, the most common choice is to perform a database attach upgrade, unless you have a small and discrete farm databases to the new installation. When you add databases to the new installation, the upgrade process automatically upgrades them. Data migration is considered to be the same as an in-place. similar in process and goals to the database attach option. The process of data migration involves the creation of a new SharePoint 20 10 farm environment and the movement (or migration) and addition