upgrading to sharepoint 2010

C D H

C D H Upgrading to SharePoint 2010

March 2011

C D H Quick Facts

About Us• 21st Year• Grand Rapids &

Royal Oak• 30 Staff

Approach• Vendor Agnostic• Non-reseller• Professional

Services Only

Partnerships• Microsoft Gold

• Central Region Client Experience Award Winner

• VMware Enterprise• Cisco Premier• Novell Platinum• Citrix Silver

C D H

Infrastructure

Access & Identity Management

Expertise

Project Management

Collaboration

C D H Talks TechC D H

C D H Your Presenter

Mark BeckerMCSE, MCTS [email protected]

C D H Collaboration Team

Susan Cotts Doug Brower* Tim Allison

Mark Jordan

Eric Inch

David TappanMark BeckerEric McKee

C D H Why Upgrade to 2010?

C D H Why Upgrade to 2010?

• Benefits:– http://www.jeffgiangiulio.com/2010/04/why-

upgrade-to-sharepoint-2010.html

• SharePoint 2010 Editions– http://thecommunicator.co.cc/2010/05/03/share

point-2010-feature-comparison-sharepoint-foundation-2010-vs-sharepoint-2010-standardenterprise/

C D H Key to Success

Proper Preparation Prevents Poor Performance

He who fails to plan, plans to fail

C D H Components for Success

• Planning− Identify organizational goals (success criteria, budget, timeline, downtime),

identify stakeholders, create project team, build project plan for the remaining stages of the project.

• Discovery− Document existing environment, researching upgrade materials (known issues,

upgrade methods), identify solutions (in house and 3rd party) research solution compatibility to 2010.

• Testing 1-2− Build a quick test environment (virtual), perform test migration(s) using real data,

identify issues and mitigate (UI, incompatible or missing solutions). Build production or test farm and migrate again (identify infrastructure issues), validate new solutions, new UI and performance with real users.

• Execute− Solution is tested, production farm is built, obtain approval to proceed, issue

communications and perform final migration.• Stabilize

− Final user tests, the migration is formally accepted by the stakeholders. Includes final development efforts, release coordination and communication, end user training, production deployment, final solution documentation, and project closure tasks, including formal sign-off on all project deliverables.

DiscoveryTesting

1-2Execute StabilizePlanning

C D H Planning: Organizational Goals

• What is Success? - Budget, timeline, downtime, helpdesk tickets (training issues and problem resolution)

• Stakeholders? – Critical to your success (defining success factors, giving you access to key testers, key to adoption of the new technology)

• Project Team – *Project manager, stakeholders, *SharePoint specialist(s), *Developer(s), IT infrastructure staff, *Training specialist(s), End user testers

* Can be outsourced

C D H Planning: The Plan

Discovery• Install pre-requisites

• Identify solutions and mitigation

• Review PreUpgradeCheck

• Determine requirements for new farm

Test 1• Build test farm• Perform migration using real data

• Identify major upgrade issues

• Test with project team

• Build issues list for team

• Determine fixes and document

New Farm• Build new test and production farm

• Fully configure all features to final specifications

Test 2• Determine best migration process

• Perform migration test on new farm

• Establish migration window

• Test with real users

• Determine training requirements and initiate training

Final Migration• Client updates• Complete training• Communicate outages

• Backup and verify• Migrate databases• Implement solutions

• End user test• Fix issues• Backup new farm• Release to production

Stabilize• Provide ad-hoc support

• Solution development

• Complete “As Built” documentation

• Clean up old server farm

C D H Planning: Migration Methods

• Selecting a Migration Method– In-Place– *Database attach– *Hybrid 1 (Database attach w/read-only databases)– Hybrid 2 (In-Place w/detached content databases)– AAM Hybrid (both farms up w/detach database)*Most common


Chuck Norris can upgrade SharePoint In-Place. (and it will actually work)


• In-Place (Not recommended)– Upgrade performed directly on production servers– Servers must meet pre-requisites

• Windows Server 2008 SP1 or higher• SQL Server 2005 SP3 CU3

– Pros• Customizations are kept• Farm-wide settings preserved• Bizarre User Profile migration is avoided

– Cons• Most risky – no fallback• Most downtime – all content databases upgraded serially• Power outage or disk space issue during upgrade could leave upgrade in an

unsupported state


• Database Attach (Most common)– Performed on a new SharePoint 2010 farm– Customizations and all configurations are re-deployed to this farm– Pros

• SAFE! Fallback is assured since production servers are not modified• Can upgrade multiple content databases in parallel for less downtime (provided you

have the SQL resources)• Can use this method to consolidate multiple farms into one• Can upgrade hardware as well as software• Opportunity to clean out the old server with a “fresh” install

– Cons• More effort because new farm has to be built, server and farm settings recreated• Customizations not upgraded• Copying databases over the network takes time and additional space


• Hybrid 1 (common)– Same as the database attach method but source databases are set to

read-only rather than taken offline– Production farm is usable for read-only access by users– Pros

• Minimal downtime for users for read-only access• SAFE! Fallback is assured since production servers are not modified• Can upgrade multiple content databases in parallel for less downtime (provided you

have the SQL resources)• Can use this method to consolidate multiple farms into one• Can upgrade hardware as well as software• Opportunity to clean out the old server with a “fresh” install

– Cons• More effort because new farm has to be built, server and farm settings recreated• Customizations not upgraded• Copying databases over the network takes time and additional space


• Hybrid 2 (Better than In-Place)– Upgrade performed directly on production servers , but content

databases are detached – After in-place upgrade of services and configuration databases the

content databases are attached and upgraded (in parallel if necessary)– Servers must meet pre-requisites

• Windows Server 2008 SP1 or higher• SQL Server 2005 SP3 CU3

– Pros• Customizations are kept• Farm-wide settings preserved• Bizarre User Profile migration is avoided• Save time over In-Place method by upgrading multiple content databases in parallel

– Cons• Still risky. No fallback for server. Content databases are safe, but a build of a SharePoint

2010 farm would be necessary to move forward• Still more downtime than the database attach

C D H Discovery

“The more you know, the more you realize you know nothing.”

– Socrates

C D H Discovery

• Review Upgrade Sites and Articles:– 5 Ways to Ruin Your SharePoint 2010 Upgrade

http://www.cmswire.com/cms/enterprise-cms/5-ways-to-ruin-your-sharepoint-2010-upgrade-008392.php

– SharePoint 2010 Upgrade Key Resourceshttp://blogs.msdn.com/b/joelo/archive/2010/01/31/sharepoint-2010-upgrade-key-resources.aspx

– Microsoft Upgrade Resource Center | SharePoint 2010IT Pro: http://technet.microsoft.com/en-us/sharepoint/ee517214.aspxDeveloper: http://msdn.microsoft.com/en-us/sharepoint/ee514557.aspx

– Joel Oleson’s PreUpgradeCheck Drilldownhttp://www.sharepointjoel.com/Lists/Posts/Post.aspx?List=0cd1a63d%2D183c%2D4fc2%2D8320%2Dba5369008acb&ID=238

– Anders Rask SharePoint 2010 Upgrade Whitepaperhttp://sites.wizdim.com/andersrask/files/2010/05/WhitePaper-Upgrading-SharePoint-2007-to-SharePoint-2010.pdf

– IE 6 Countdownhttp://www.ie6countdown.com/

C D H Discovery: 2007 Farm

• Upgrade Existing SharePoint Farm to SP2 + CU October

• Run STSADM –o preupgradecheck– Reports farm and server data

• Servers, databases, AAM, site definitions, features, language packs• Can serve as your server farm documentation

– Identifies current or potential issues• Data orphans, missing features, database schema issues

• Research and resolve issues . Rerun preupgradecheck

• EXAMPLE PreUpgradeCheck Report– http://www.sharepointjoel.com/Lists/Posts/Post.aspx?List=0cd1a63d%2

D183c%2D4fc2%2D8320%2Dba5369008acb&ID=238

C D H Discovery: Customizations

• Identify Customizations:– Look in C:\Program Files\Common Files\Microsoft Shared\Web Server

Extensions\12\Layouts, Templates\Features– GAC (Global Assembly Cache), CSS, Master Pages, timer jobs– Gary Lapointe’s “gl –enumunghostedfiles” (preupgradecheck miss)– Add/Remove Programs


• Research and Document customization issues– FAB 40 (STP and WSP)

http://blogs.technet.com/b/tothesharepoint/archive/2010/08/18/sharepoint-2010-products-upgrade-and-the-fabulous-40-application-templates.aspxhttp://www.techsolutions.net/Blog/tabid/65/EntryId/17/Fab-40-Templates-for-MOSS-2010.aspx

– 3rd party upgrades (Bamboo, KWizcom, Nintex, etc.)– Custom developed solutions and UI

• Develop a plan for dealing with customizations– Identify budget for 3rd party upgrades– Determine budget and time for custom developed solutions and UI– Prepare budgetary proposal and timeline for stakeholders


• Common User Experience (UX) issues– Custom Master Pages and Layouts will not upgrade

• New HTML markup (tables are gone in Master Page – cross browser support)

• New ribbon control, new controls added and other controls removed• Options:

– Convert existing Master Page (not recommended because it won’t support cross browser)

– Don’t do a visual upgrade!– Recreate Master page from scratch using standards compliant valid

markup – you will have to write new CSS

– Themes do not upgrade• New theme engine in 2010. v3 can still use the existing theme• Options:

– Use GUI to create your own theme or use PowerPoint and save as thmx file and upload

C D H Delivery: Before Visual Upgrade

C D H Discovery: After Visual Upgrade

C D H Discovery: Hardware

• Hardware Assessment– Review current utilization – Disk / RAM / CPU– Determine hardware capacity for new farm, including planned

expansion– Determine physical vs. virtualization strategy– Prepare budgetary proposal for stakeholder approval

• Minimum Hardware Requirements– Front End & App Tier

• 64-bit, four cores (2 core on virtual)• 8 GB (4GB for developer)• 80 GB system drive

– SQL Tier• 64-bit, four cores (2 core on virtual)• 8 GB – 16 GB (more is required during migration)• 80 GB system drive

C D H Discovery: Software

• Software Assessment:– Determine SQL Sever strategy for SharePoint 2010– Assess client workstation upgrade requirements– Prepare software budgetary proposal for stakeholders

• Software Requirement:– Windows Server 2008 R2 (ideal) or Windows Server 2008

w/SP2– SQL Server 2008 R2 (ideal), SQL Server 2008 SP1 CU2 or 64-

bit SQL Server 2005 SP3 CU3– No IE 6!

C D H Testing

“As a rule, software systems do not work well until they have been used, and have

failed repeatedly, in real applications.”– Dave Parnas

C D H Testing 1

• Create new least privilege accounts for the 2010 farm– spAdmin (for SP install), spFarm (Good account for database access

and user profile), spContent (Search crawl), spAppPool (application pools), spSQLsvc (SQL Server account), spSVC (SharePoint Service), spUPS (User Profile Service Sync)

• Build Farm– Production SQL Server (can be used be used for both farms)– Test SharePoint 2010 farm

• Quick install. Very little planning required• Used to enable a quick migration test

– Production and Test (QA) Farms• Architected and built using best practices, full configuration and capacity• Ideally both farms are identical and built together to ensure like configuration

C D H Testing 1

• Migration Test– Obtain backup of the production content databases:

• Content databases (main content and My Sites)• User Profile database• SSO (if used)

– Restore databases to SQL Server• Very SharePoint sites can break down the migration by content databases to conserve

test space required

• Perform Content DB Test against 2010 farm– Give the spAdmin account rights on the SQL Server and to the

restored databases– Create Web Application for your URL – delete the content database it

creates– Run PowerShell command:

• Add-SPShellAdmin -UserName DOMAIN\spAdmin• Test-SPContentDatabase -name Content_DB -webapplication https://YourURL -

serverinstance SQLsvr | ConvertTo-CSV | Out-file f:\migrationtest\migration.csv

C D H Testing 1

• Review CSV for Issues– Identify issues and correct in 2010 farm

• Install missing solutions, site definitions, etc.

– Re-run Content DB Test• Verify issues are resolved• In some cases you can proceed with the attach database test without cleaning up all the

issues

• Attach databases– Run PowerShell command:

• Mount-SPContentDatabase -Name Content_DB -DatabaseServer SQLSPS -WebApplication https://yourURL

– Time the process– Monitor the SQL Server (you may need to add memory)– Upon completion, review logs …14\LOGS – look for “Upgrade session

finished successfully!”

C D H Testing 1

• Perform a Visual Upgrade:$sitecollection = Get-SPSite https://YourURL foreach($SPWeb in SiteCollection.AllWebs){$SPWeb.UIversion=4;$SPWeb.update();}

C D H Testing 1

• Review Sites for Issues– Web parts

• Missing, broken, render issues

– Style and Appearance• Images display correctly• CSS showing appropriately• Themes showing appropriately• js working (check for script errors)

– Permissions• Do appropriate people and groups still have correct permission level• Audienced web parts will require the audiences to be rebuilt to test• Targeted web parts work differently. You will have to tweak permissions

– Customized (unghosted) pages• Are customizations still in place

– Setup Search to crawl and test

C D H Testing 1

• User Profile Migration (many ways – few that work)– Create Web Application for My Sites

• If migrating My Sites, delete content db and attach migrated database

– User Profile Service Application Creation(make sure Managed Metadata Service Application is created first)• Temporarily add spFarm to local Administrators group and logon as spFarm• Create User Profile Service Application• Start the User Profile Service and manage the Application (Be patient. You may need a

reboot and always logon as spFarm!)• Start the User Profile Synchronization Service (be REAL patient – takes about 15 minutes)

– Create a User Profile Synchronization Connection• Typically this is AD. Consult TechNet article for AD rights http://technet.microsoft.com/en-

us/library/ee721049.aspx#accounts• Create connection, timer job and perform full sync. (be patient!)

– Configure Search to crawl the User Profile• Assign Administrator permissions in the User Profile Service Application to the spContent

account• Add the User Profile Content Source: sps3s://YourURL

C D H Testing 1

• User Profile Migration (cont.)– Verify the User Profile is working

• Synchronizing• Search can crawl it and displays users• You can manage the service without errors

– Stop the User Profile Synchronization Service– Delete the User Profile Service Application!– Create the User Profile Service Application

• Instead of creating a new profile database, specify the restored MOSS 2007 database (make sure you granted rights to spFarm to that database)

• Complete the process as before – this will upgrade the database to SharePoint 2010

– Start the User Profile Synchronization Service

• Verify User Profile Migration– Crawl the profile again and verify unique data was migrated

• Verify My Sites using same verification steps for Sites

C D H Testing 1

• SSO migration– Follow SSO migration steps documented in Anders Rask’s

whitepaper

• Tracking Migration Issues– Build a Tracking Site (preferred)

(Note: a site needs to have it’s own Web Application on the new 2010 farm)

– Give access to all testers– Conduct training sessions for end user testing– Configure alerts on the site

C D H Testing 1

• Tracking Migration Issues List

C D H Testing 2

• Install solutions and customizations onto new Test Farm

• Perform 2nd migration– Obtain migration timing metrics

• Project team performs initial tests• Open site to broader audience for User

Acceptance Testing (UAT)– Thorough test plan tests performance and all use cases

• Finalize Go-Live Plan– Detailed upgrade recipe: instructions to mitigate every

known issue• Conduct End User training

C D H Execute

• Obtain stakeholder approval to proceed with final migration

• Issue communications• Perform backups• Perform final migration

C D H Stabilize

• Post migration testing to confirm proper migration– Execute UAT Test Plan

• Finalize solution, customization and UI fixes• Upgrade is formally accepted by stakeholders• Complete end user training• Document “As Built” server configuration• Close a successful SharePoint 2010 Upgrade

project!

C D H

C D H SharePoint in Action

C D H Ferrari

C D H Energizer

C D H Winchester Ammunition

C D H Swatch

C D H TV Guide

C D H Kroger

C D H

Royal Oak306 S. Washington Ave.Suite 212Royal Oak, MI 48067p: (248) 546-1800

Thank You

Grand Rapids15 Ionia SWSuite 270Grand Rapids, MI 49503p: (616) 776-1600

(c) C/D/H 2007. All rights reservedwww.cdh.com

upgrading to sharepoint 2010

Technology