project server 2010 migration - mpug€¦ · 3. install sharepoint 2010 and project server 2010 to...

Microsoft Project Basics 3/5/2013

1

Project Server 2010

Migration

Presented by Chad Olson, Director of Technical Services

Agenda

Reasons to Migrate

Types of Migrations

• Best Practices

• Lessons Learned

Post Migration Considerations

Backwards Compatibility Mode (BCM)

Overview of Project Server 2013 Migration Process

Common Misperceptions

Planning

Q&A


2

Objectives & Takeaways

Objectives:

• Education on the migration process

• Share lessons learned & best practices

Key Takeaways:

• Avoid common pitfalls during a migration

• Better prepare yourself for future Project Server deployments

About Me

Chad Olson, MCTS MCSE MCP

• Director of Technical Services at Sensei Project Solutions

• Been involved with Project Server platform since 2001

• Focus Primarily on Technical Services

• Installation

• Design

• Architecture

• Configuration

• Migration

• Integration

• Reporting

• 50+ Microsoft Project/Project Server Deployments

• ~20 migrations

http://www.senseiprojectsolutions.com/


3

Sensei Project Solutions

Microsoft Partner with deep expertise in PPM solutions

100+ Microsoft Project/Project Server deployments

1,000+ Project Managers/Team Members trained

Certified on entire technology stack + Project Management:

• PMP/PMI-SP, MCP, MCT, MCTS, MCSE

How do we help our clients?

Deployment Services

• Microsoft PPM solution

• On-going support services

Training

• Role-based, Process-focused

• Coaching and Mentoring

Solutions

• ‘Jumpstart’ solutions (‘project in a box’)

• Report Packs


4

Reasons to Migrate

New Features

Product Support

Compatibility with other software or add-ons

Performance

Better Hardware

New Architecture

Maintenance

Deployment

Licensing

Types of Migrations/Upgrades

High Level

2003 -> 2007 -> 2010

• Migrate from Project Server 2003 to 2010

• Virtual Migration Environment (VME)

• Uses Project Migration Tool (Project Pro 2007 component)

2007 -> 2010

• In-Place Upgrade

• Database Attach Migration

• Project and SharePoint Content Databases

• Database Attach Core Migration

• Project Databases Only


5

Migration Type

Project Server 2003 to Project Server 2010

Project Server 2003 Migration

Need to migrate into Project Server 2007 first

• Virtual Migration Environment (VME) – A Hyper-V image with Project Server 2007 installed. Contains migration tool and scripts. Provided by Microsoft for download

• Can install a new Project Server 2007 on premise if desired

Migration Tool

• Included on the Project Professional 2007 media as an optional installation component (P12MigrationTool.exe).

• Can be ran on a desktop or on the server

• Includes a configuration .ini file to determine which projects to include or exclude

• Command line: P12MigrationTool.exe –c path:\filename.ini

• Saves and publishes each project to the queue one-by-one

http://www.microsoft.com/en-us/download/details.aspx?id=19311


6


Migration Process Overview from 2003 -> 2007 • Project Data Only


Full Migration with WSS 2.0 (SharePoint workspaces)

• Steps: 1.Install PS2007, 2.Run Prescan tool, 3.Attach a copy of WSS 2.0 content dbs to PS 2007 farm, 4.Migrate & Publish projects


7


Pre-Migration Scripts

• Determine any issues with existing 2003 data

• Included in the VME

• Included in the Project Server 2007 Migration Guide

• Can also be used to filter projects to migrate or exclude


Run the Pre-Migration Scripts and analyze the results

Run the migration tool with the –verify switch first

Fix any issues in the 2003 environment first

Read the Migration Guide

Document your migration settings and review with the team for consensus

Educate admins on what doesn’t migrate

• Status reports, To-Do lists, view filters, project versions, status update rules, saved links, etc.

http://technet.microsoft.com/en-us/library/cc197696(v=office.12)


8


Virtual Migration Environment (VME) • Only Hyper-V with Windows Server 2008 R2

• Minimum of 4GB virtual memory, pref. 8 GB

• Minimum of 4 virtual processors (cores)

• Dedicated drives for .vhd files (Determine needed space for database files)

Reserved Enterprise Fields in Project Server 2007 • Project Type, Project Manager, Proposal, State, etc.

Externally Edited Projects • Need to save in Project Professional 2003 before migrating

Outstanding Status Updates (Task Updates) • Default setting is to not migrate projects with outstanding status updates

Project Versions • Determine best method to rename projects with _Published. Look at the

Rename Tool.

Timing • Migration Tool takes a long time to save projects

• ~1 hour per 135 projects

Migration Type

Project Server 2007 to Project Server 2010 – In-Place Upgrade

http://archive.msdn.microsoft.com/PS2007Rename


9

In-Place Upgrade

Process Overview

1. Install SharePoint Server 2010 (Ent.) on all servers in the farm

2. Install Project Server 2010 on all servers in the farm

3. Run the SharePoint Config. Wizard on server containing CA

4. Run the SharePoint Config. Wizard on remaining servers

In-Place Upgrade

All servers need to be 64-bit hardware and 64-bit software (OS, SQL, etc.)

Installer will not set up required SharePoint 2010 service applications for you. Do this manually before the upgrade.

Get backups of your environment before upgrading

Check Upgrade.log files for information or errors

Make sure your accounts have SQL permissions to the databases

Must reconfigure the Analysis Services configuration after upgrade


10

Migration Type

Project Server 2007 to Project Server 2010 – Database Attach Migration

Database Attach Migration

Process Overview

1. If needed; separate project workspaces to a dedicated SharePoint Content database

2. Backup and Restore SQL databases to new environment

3. Install SharePoint 2010 and Project Server 2010 to the new farm (using different hardware)

4. Create a web application in SharePoint 2010 for the new PWA

5. Add SharePoint 2007 content database to this web app using stsadm.exe (this will upgrade it to 2010)

6. Provision a PWA site and point to the restored Project Server 2007 databases (this will upgrade them to 2010)

7. Run the Bulk Update Project Sites link to update the URLs


11


Most common of all migrations

• “Database Attach Migration”

Why?

• Most organizations didn’t have existing 64-bit software/hardware

• Want to move to faster and more robust hardware

• A chance to change architecture (WFE, App, Database tiers)

• A common trend to change from physical to virtual hardware


Transaction logs can grow really large during a Database Attach migration

Need to run a switch for new SharePoint UI for migrated project workspaces

Quick Launch Bar customizations get messed up after migration. Reset to default layout before migration.

Make sure SharePoint 2010 environment is healthy before the upgrade (check Health Analyzer, ULS logs, event logs, etc.)

Ensure latest Service Pack and/or Cumulative Updates are installed prior to the migration

Ensure SQL Server is configured with Best Practices

If using a customized template for project sites, verify this works after migration. Might need to recreate it manually.


12

Migration Type

Project Server 2007 to Project Server 2010 – Database Attach Core Migration

Database Attach Core Migration

Process Overview

1. Backup and Restore the 4 Project Server databases to new SQL environment

2. Install SharePoint 2010 and Project Server 2010 to the new farm (using different hardware)

3. Create a web application in SharePoint 2010 for the new PWA

4. Provision a PWA site and point to the restored Project Server 2007 databases (this will upgrade them to 2010)

5. Create new project sites, if desired, for each migrated project


13

Database Attach Core Migration

If projects did have a project workspace association and you want to use a new one, you’ll need to clear it out using a SQL update command

Verify you don’t need any other SharePoint data from PWA such as documents or a help site. If so, move that manually.

Common approach for companies that weren’t utilizing project workspaces before and want to start new with SharePoint 2010 project sites.

Test

Before Migrating or Upgrading


14

Post Migration Considerations

Backwards Compatibility Mode: Turned on after a migration/upgrade. Determine when you can deploy Project Pro 2010 to users and when you can train them on the new interface.

All migrated projects get assigned to “Basic Project Plan” or whatever Enterprise Project Type (EPT) is the default. Need to manually assign those after the migration if desired.

When to create project sites if no sites were migrated.

Recreate Data Analysis views in Excel Services

Have a Test environment to test the migration into and also to add new functionality. Then use Playbooks or Solution Starter tools to move settings into Production after the final migration.

Do you need Forms Authentication configured?

Redirect users to new environment

Backwards Compatibility Mode (BCM)

Allows Project Professional 2007 with SP2 or higher to connect

Turned on by default after a migration/upgrade (only way to turn it on)

Once you uncheck it and go into native mode you cannot revert back (greyed out).

Will need to save the Enterprise Global in Project 2010 after going native

Features if BCM is ON:

• All department fields are shown in Project Pro 2007

• Manually scheduled tasks are not available

• No inactive tasks

• Font strikethrough not available

• New project from SharePoint List disabled in PWA

http://technet.microsoft.com/en-us/library/gg128952.aspx

http://archive.msdn.microsoft.com/P2010SolutionStarter


15

Project Server 2013 – Upgrade Process

A. Plan & Prepare

Items to Note

• No “In-place Upgrade” method. Must do “Database Attach”

• Review Hardware & Software requirements first

• Plan for clients: There is no Backwards Compatibility Mode.

• No upgrade path from Project Server 2007. Must be on 2010.

Gather Info and Plan for Customizations

• Note items such as quotas, managed paths, AAM, authentication modes, customizations, email settings, etc.

Deploy new Project Server 2013 farm

• Database server needs to be SQL Server 2008 R2 or 2012.

• Install SharePoint Server 2013 and prerequisites.

• Install Project Server 2013

• Configure the farm (service apps, web application, etc.)


Prepare Windows PowerShell Environment

• Use PowerShell to execute many procedures for the migration

Verify databases are in Native Mode

• Project Server 2010 databases must be Native (no BCM)

Check data for known issues

• Run SQL scripts to check for data issues

B. Copy Databases

Backup and Restore the SharePoint content databases that contains PWA and Project Sites

Backup and Restore the 4 Project Server 2010 databases


16


C. Upgrade Data

Attach and upgrade databases using PowerShell cmdlets

Attach and upgrade SharePoint content database(s) first

Project Server Upgrade Phase

• Project Server 2013 now uses a single database

• Use PowerShell cmdlets to consolidate databases

• Attach Project Services database to web application

• Upgrade database

• Connect PWA instance

• Upgrade the PWA instance

• Enable PWA features

Upgrade Process diagram can be found here. Note: Based on Project Server 2013 Preview and subject to change.

Misperceptions: Performance

64-bits perception… twice as fast as 32-bits?



17

Misperceptions: Data Quality

Problems in 2003, 2007, let’s move to 2010 !!

Planning

Plan as much as you can

Determine Roles and Responsibilities

Mass majority of the effort is in the planning process

Determine if to have a dedicated test environment or test instance using the production environment

Have backups!

Educate users on new functionality

Practice migrations

• Capture timings

• Document any issues

• Re-test

Develop a Migration Plan or Checklist


18

Resources

Project Server 2007 Migration Guide

Virtual Migration Environment (VME)

TechNet: Project Server 2010

TechNet: Project Server 2010 Migration Resource Center

TechNet: Project Server 2010 Demand Management

TechNet: Project Server 2010 Update Center

TechNet: Upgrade to Project Server 2013 Preview

Portfolio Server 2007 Migration Guide

Follow the Conversation

Join us on Social Media!

@SenseiPPM

Sensei Project Solutions

SenseiProjectSolutions

http://www.senseiprojectsolutions.com

http://technet.microsoft.com/en-us/library/cc303388(v=office.12)


http://technet.microsoft.com/en-us/projectserver

http://technet.microsoft.com/en-us/projectserver/ff899331.aspx

http://technet.microsoft.com/en-us/projectserver/gg176680.aspx

http://technet.microsoft.com/en-us/library/gg502590(v=office.15)


http://www.senseiprojectsolutions.com/


19

Questions?

[email protected]

project server 2010 migration - mpug€¦ · 3. install sharepoint 2010 and project server 2010 to...

Documents