installation requirement will coexist on the same farm with will not work with project server 2013...
TRANSCRIPT
Nadin MeraliProgram ManagerMicrosoft
Get over the hurdles - Upgrade and Migration to Microsoft Project Server 2013
PC315
Related Sessions
PC318 - Project Server 2013 Deployment Best Practices from the field
PC319 - The Great Database Consolidation, Project Server 2010 to 2013 Migration in 8 Easy Steps
AgendaCompatibility MatrixProject Online vs Project Server 2013Migrating to Project OnlineMigrating to Project Server 2013
Installation Requirement
Will coexist on the same farm with
Will NOT work with
Project Server 2013
SharePoint Server 2013 Enterprise
SharePoint Server 2013 Enterprise
SharePoint Foundation 2010
Project Server 2010
SharePoint Server 2010 Enterprise
SharePoint Server 2010 Enterprise
Office SharePoint Server 2007
Compatibility MatrixProject Server and SharePoint Server
Compatibility MatrixProject Desktop and Project Server
Project Server 2007
Project Server 2010 Project Server 2013 & Project Online
Project Professional 2013, Project Pro for
Office 365Not Supported Not Supported Full connectivity
Project Professional 2010 Not Supported Full connectivity Not Supported
Project Professional 2007 Full connectivity
Connectivity to Server in BCM*
(Project Professional 2007 SP2 required)
Not Supported
ServicesSelf hostingon-premise
Storage
Servers
Networking
O/S
Middleware
Virtualization
Data
Applications
Runtime
You m
anag
eInfrastructure
(as a Service)
Storage
Servers
Networking
O/S
Middleware
Virtualization
Data
Applications
Runtime
Manag
ed
by v
end
or
You
manag
e You m
anag
e
Software(as a Service)
Manag
ed
by v
end
orStorage
Servers
Networking
O/S
Middleware
Virtualization
Applications
Runtime
Data
Project Server Cloud Continuum
Control
Co
st-e
fficie
ncyProject Server (On-
premise)
Project Server
Value Prop:Full h/w control – size/scaleRoll-your-own HA/DR/scale
Value Prop:100% of API surface areaEasy migration of existing appsRoll-your-own HA/DR/scale
Project Server (IaaS)
Hosted Project Server
Value Prop:Auto HA, Fault-ToleranceFriction-free scaleSelf-provisioning, management at scale
Project Online
Office 365 (SaaS)
Project Server 2013 ArchitectureW
FEA
pp
SQ
L
Project Professional
2013
3rd party on-premises
applications
SharePoint AppsPowerShellBrowser
ASPX Pages Web Services WCF Endpoints
CSOM OData
ForwarderBusiness ObjectsBusiness ObjectsBusiness Objects
WCF Endpoints
Business ObjectsBusiness ObjectsBusiness ObjectsEventin
gQueue PCS Workflow
content configS
hare
Poin
tarchive
dbopublishdraft
Pro
ject
Event Receiver
AzureWorkflow
cubes
Migrating to Project OnlineUsing Project Professional 2013Will bring in the project, tasks, task assignmentsWill NOT bring in timesheets, admin settings, portfolio’s
Using FluentPro’s Cloud Migrator ProAllows migration from Project Server 2010 (link)
Use Project Online for new initiativesStart new projects online, continue existing problems on premiseCreate report to pull data from old/new sites
Migrating to Project Server 2013No “In Place” upgrade path.No direct path from 2003 or 2007 to 20132003 and 2007 will need to follow their respective upgrade paths to reach 2010Virtual Migration Environment (2003 to 2007)Link to VME
Project Server 2010SharePoint Farm
Site Collection
Excel Services
SearchProject
Services
Site Collection
Draft
Archived
Published
Reporting
Project Server 2013SharePoint Farm
Site Collection
Excel Services
SearchProject
Services
Site Collection
Project Project
Migrating Project databasesProject Server 2010 Project Server 2013
Migrate
Content
Publish
Reporting Archive
Draft DraftPublish
DraftPublish
Reporting
DraftPublish
ReportingArchive
Draft (draft.*) Publish (pub.*) Reporting (dbo.*) Archive (ver.*)
Migrating Project databases
Draft
Archived
Published
Reporting
Project Server 2010 Project Server 2013
Content
Draft
Archived
Published
Reporting
Contoso.com
Contoso.com/sites/ServicePWA
Contoso.com/sites/ConsultingPWA
MigrateContent
Contoso.com
Project
Project
Contoso.com/sites/ServicePWA
Contoso.com/sites/ConsultingPWA
Migration Plan
Convert Project DB
Upgrade and Mount Project DB
Mount and Upgrade Project Web Instance
Enable PWA FeaturePost Migration
Test
•
Plan Upgrade
Setup New Project 2013 Farm
Upgrade to Project Server 2010
Preparing Project Server 2010
Plan UpgradeLearn
• Upgrade methods• New capabilities• Downtime mitigation
Prepare• Document environment• Manage customizations• Plan upgrade strategy• Make items upgradable
Test• Build test farms• Use real data• Evaluate techniques• Find issues early
Implement• Build/upgrade farms• Deploy customizations• Minimize downtime• Monitor progress
Validate• Troubleshooting• Upgrade event failures• UI/UX issues• Data issues
PC318 - Project Server 2013 Deployment Best Practices from the field
Migration Plan
Convert Project DB
Upgrade and Mount Project DB
Mount and Upgrade Project Web Instance
Enable PWA FeaturePost Migration
Test
•
Plan Upgrade
• Plan for • Clients• Upgrading
customizations
• Multiple test cycles
Setup New Project 2013 Farm
Upgrade to Project Server 2010
Preparing Project Server 2010
Small Farm
Availability
Perf
orm
an
ce
Migrating to Project Server 2013Requirements and Installation
Each server role on its own server
Medium Farm
Multiple servers for most server roles Large Farm
Multiple servers for each server role, may include multiple farms for specific purposes.
Multiple environments: • Development• Proof Of Concept• Pilot• Test/Staging• Production
Bare Metal vs VM
Migrating to Project Server 2013Requirements and Installation
Lync 2010 (Optional)
Project Professional Windows 7 or 8
TechNet
IE8 or latest version of Firefox, Chrome or Safari
Exchange Server 2013 (Optional)
Microsoft SQL Server 2008 R2 SP1
SharePoint Server 2013 Enterprise
Windows Server 2008 R2 SP12012 R2 requires SharePoint SP1
Hardware and software requirements for Project Server 2013
Installation prerequisites for Project Server 2013Requirements and InstallationInstallation Prerequisites are the same as SharePoint 2013Required Service ApplicationsProject Service ApplicationExcel Services (Used for Reporting)PerformancePoint Service (Used for Reporting)Secure Store Service (Used for Reporting)State Service (Used for Charting)
Migration Plan
Convert Project DB
Upgrade and Mount Project DB
Mount and Upgrade Project Web Instance
Enable PWA FeaturePost Migration
Test
•
Plan Upgrade
• Plan for • Clients• Upgrading
customizations
• Multiple test cycles
Setup New Project 2013 Farm
• Review Hardware requirements
• Plan new farm topology
• SharePoint 2013 + Project Server 2013 running
Upgrade to Project Server 2010
Preparing Project Server 2010
Upgrade to Project Server 2010
No direct path from 2003 or 2007 to 2013
Create migration Farms to migrate data
Will require more downtime
Migrating to Project Server 2013Pre-Project Server 2010
Project Server 2003
Temporary/VM
Project Server 2007
(VME)
Temporary/VM
Project Server 2010
Project Server 2013
Migration Plan
Convert Project DB
Upgrade and Mount Project DB
Mount and Upgrade Project Web Instance
Enable PWA FeaturePost Migration
Test
•
Plan Upgrade
• Plan for • Clients• Upgrading
customizations
• Multiple test cycles
Setup New Project 2013 Farm
• Review Hardware requirements
• Plan new farm topology
• SharePoint 2013 + Project Server 2013 running
Upgrade to Project Server 2010
• Follow established upgrade path from previous versions of Project
Preparing Project Server 2010
Preparing Project Server 2010Disable Prevent Active Directory synchronization for this userNot supported in Project Server 2013.Use XXXXX_Published Select RES_NAME, WRES_ACCOUNT, WRES_EMAIL From MSP_RESOURCES Where RES_PREVENT_ADSYNC = 1
Check for and repair all database consistency errors.
Preparing Project Server 2010What will be migrated over?ProjectTasksTask AssignmentsProject SitesProject Site DocumentTimesheets etc
CustomizationDB Customizations will not be migrated over.New Tables/Columns that have need addedWebParts may work and will need to be testedCustom Workflow/Activities dlls will need to be installed post-migrationContact the vendor to see if the customization is supported in 2013 or if they have an updated version
Preparing Project Server 2010Disable Backward Compatibility Mode (BCM)BCM mode not supported, switch to native modeUse intermediate farm to upgrade
ProductionProject
Server 2010 (BCM)
Temporary/VM
Project Server 2010
New Production
Project Server 2013
Migration Plan
Convert Project DB
Upgrade and Mount Project DB
Mount and Upgrade Project Web Instance
Enable PWA FeaturePost Migration
Test
•
Plan Upgrade
• Plan for • Clients• Upgrading
customizations
• Multiple test cycles
Setup New Project 2013 Farm
• Review Hardware requirements
• Plan new farm topology
• SharePoint 2013 + Project Server 2013 running
Upgrade to Project Server 2010
• Follow established upgrade path from previous versions of Project
Preparing Project Server 2010
• Enable User AD sync
• Check DB Consistency and ownership
• Disable BCM
Backup and RestoreSharePoint Site Collection LockContent DBEach sets of Project DBs
Draft
Archived
Published
Reporting
Draft
Archived
Published
Reporting
Contenthttp://contoso.com/
http://contoso.com/sites/ServicePWA
http://contoso.com/sites/ConsultingPWA
All Projects DB’s whose site collection exists in the Content DB
stsadm -o setsitelock -url http://contoso.com -lock noaccess
stsadm -o setsitelock -url http://contoso.com
Backup and RestorePublish Database CleanupThe WRES_Account field should be NULL and not an empty string
Use XXXXX_Published Select RES_Name, RES_TYPE, RES_ID from MSP_RESOURCES where WRES_ACCOUNT =''
Update MSP_RESOURCES set WRES_ACCOUNT = null where WRES_ACCOUNT ='‘
Migration Plan
Convert Project DB
Upgrade and Mount Project DB
Mount and Upgrade Project Web Instance
Enable PWA FeaturePost Migration
Test
•
Plan Upgrade
• Plan for • Clients• Upgrading
customizations
• Multiple test cycles
Setup New Project 2013 Farm
• Review Hardware requirements
• Plan new farm topology
• SharePoint 2013 + Project Server 2013 running
Upgrade to Project Server 2010
• Follow established upgrade path from previous versions of Project
Preparing Project Server 2010
• Enable User AD sync
• Check DB Consistency and ownership
• Disable BCM
SharePoint Mount and Upgrade SitesCreate Web ApplicationUse temporary Content DB name
Test-SPContentDatabaseCheck results to look for
any upgrade blockerDeploy any relevant missing featuresMissing Site Definition
Mount-SPContentDataBaseMounts the content DB
//Test Content DBTest-SPContentDataBase –Name PWA_WSS_CONTENT_80 –WebApplicatio http://contoso.com
//Mount Content DBMount-SPContentDataBase–Name PWA_WSS_CONTENT_80 –WebApplicatio http://contoso.com -ServerInstance localhost
SharePoint Mount and Upgrade SitesSP-SiteAdd your account as a secondary owner of the PWA site collections
Migrate UsersWindows Classic authentication mode to claims based authentication
Test-SPSiteHealth Check1. Site Collection Administration2. Site Collection Health Checks.3. Run Checks
Upgrade-SPSite
//Set site ownership for each PWA siteSet–SPSite -Identity http://contoso.com/sites/servicePWA -SecondaryOwnerAlias “contoso\FarmAdmin”// Migrate users(Get-SPWebApplication http://contoso.com).migrateUsers($true)
//Test each PWA SiteTest–SPSite –Identity http://contoso.com/sites/servicePWA //health check navigate tohttp://contoso.com/sites/servicePWA/_layouts/15/settings.aspx
//Upgrade each PWA SitesUpgrade–SPSite –Identity http://contoso.com/sites/servicePWA –versionupgrade
Migration Plan
Convert Project DB
Upgrade and Mount Project DB
Mount and Upgrade Project Web Instance
Enable PWA FeaturePost Migration
Test
•
Plan Upgrade
• Plan for • Clients• Upgrading
customizations
• Multiple test cycles
Setup New Project 2013 Farm
• Review Hardware requirements
• Plan new farm topology
• SharePoint 2013 + Project Server 2013 running
Upgrade to Project Server 2010
• Follow established upgrade path from previous versions of Project
Preparing Project Server 2010
• Enable User AD sync
• Check DB Consistency and ownership
• Disable BCM
Convert Project DBConvertTo-SPProjectDatabase4 2010 Project DBs into 1 x 2013 Project DBDestructive Operation
//Convert 4x 2010 Project DB’s into a 2013 Project DB
ConvertTo-SPProjectDatabase -WebApplication http://contoso.com-Dbserver localhost-ArchiveDbname PWA_Service_Archive -DraftDbname PWA_Service_Draft -PublishedDbname PWA_Service_Published -ReportingDbname PWA_Service_Reporting -ProjectServiceDbname PWA_Service
Draft
Archived
Published
Reporting Project
Draft
Archived
Published
Reporting
Migration Plan
Convert Project DB
• Convert 4 Project DB’s into 1 new Project DB
Upgrade and Mount Project DB
Mount and Upgrade Project Web Instance
Enable PWA FeaturePost Migration
Test
•
Plan Upgrade
• Plan for • Clients• Upgrading
customizations
• Multiple test cycles
Setup New Project 2013 Farm
• Review Hardware requirements
• Plan new farm topology
• SharePoint 2013 + Project Server 2013 running
Upgrade to Project Server 2010
• Follow established upgrade path from previous versions of Project
Preparing Project Server 2010
• Enable User AD sync
• Check DB Consistency and ownership
• Disable BCM
Upgrade and Mount Project DBMount-SPProjectDatabaseMounts the newly created Project DB to the Web Application
Test-SPProjectDatabaseCheck for errors that could cause it to fail
Upgrade-SPProjectDatabaseUpgrades the database to the 2013 format
//Mount Project DB to Web ApplicationMount-SPProjectDatabase –Name PWA_Service –WebApplication http://contoso.com/ –DatabaseServer localhost
//Test each PWA SiteTest-SPProjectDatabase –Name PWA_Service–DatabaseServer localhost
//Update Project DatabaseUpgrade-SPProjectDatabase –Name PWA_Service –WebApplication http://contoso.com/ –DatabaseServer localhost
Migration Plan
Convert Project DB
• Convert 4 Project DB’s into 1 new Project DB
Upgrade and Mount Project DB
• Mount Project Database
• Test Project Database
• Upgrade Project Database
Mount and Upgrade Project Web Instance
Enable PWA FeaturePost Migration
Test
•
Plan Upgrade
• Plan for • Clients• Upgrading
customizations
• Multiple test cycles
Setup New Project 2013 Farm
• Review Hardware requirements
• Plan new farm topology
• SharePoint 2013 + Project Server 2013 running
Upgrade to Project Server 2010
• Follow established upgrade path from previous versions of Project
Preparing Project Server 2010
• Enable User AD sync
• Check DB Consistency and ownership
• Disable BCM
Upgrade and Mount Web App InstanceMount-SPProjectWebInstanceMounts Project DB to the Project Web App Instance
Test-SPProjectWebInstanceCheck for errors likeBI Center existsUnprocessed Queue Jobs/Queue StatusProject Workspaces
Upgrade-SPProjectWebInstance
//Mount Project DB to Project Web App InstanceMount-SPProjectWebInstance –DatabaseName PWA_Service –SiteCollection http://contoso.com/sites/servicePWA –DatabaseServer localhost
//Test each Project Web App instanceTest-SPProjectWebInstance –Identity http://contoso.com/sites/servicePWA
//Upgrades the Project Web App InstanceUpgrade-SPProjectWebInstance –Identity http://contoso.com/sites/servicePWA
Migration Plan
Convert Project DB
• Convert 4 Project DB’s into 1 new Project DB
Upgrade and Mount Project DB
• Mount Project Database
• Test Project Database
• Upgrade Project Database
Mount and Upgrade Project Web Instance
• Mount Project Web Instance
• Test Project Web Instance
• Upgrade Project Web Instance
Enable PWA FeaturePost Migration
Test
•
Plan Upgrade
• Plan for • Clients• Upgrading
customizations
• Multiple test cycles
Setup New Project 2013 Farm
• Review Hardware requirements
• Plan new farm topology
• SharePoint 2013 + Project Server 2013 running
Upgrade to Project Server 2010
• Follow established upgrade path from previous versions of Project
Preparing Project Server 2010
• Enable User AD sync
• Check DB Consistency and ownership
• Disable BCM
Enable PWA FeatureEnable-SPFeature Enabled the PWA feature on the site collection
//Enable PWA featureEnable-SPFeature –Identity pwasite -URL http://contoso.com/sites/servicePWA
Migration Plan
Convert Project DB
• Convert 4 Project DB’s into 1 new Project DB
Upgrade and Mount Project DB
• Mount Project Database
• Test Project Database
• Upgrade Project Database
Mount and Upgrade Project Web Instance
• Mount Project Web Instance
• Test Project Web Instance
• Upgrade Project Web Instance
Enable PWA Feature
• Turn on feature for Project Site collection
Post Migration
Test
•
Plan Upgrade
• Plan for • Clients• Upgrading
customizations
• Multiple test cycles
Setup New Project 2013 Farm
• Review Hardware requirements
• Plan new farm topology
• SharePoint 2013 + Project Server 2013 running
Upgrade to Project Server 2010
• Follow established upgrade path from previous versions of Project
Preparing Project Server 2010
• Enable User AD sync
• Check DB Consistency and ownership
• Disable BCM
CustomizationsConfigure/Upgrade customizationsCustom Workflow/Activities dlls need to be reinstalled.
Add custom columns/tables reporting
Enable Issues and Risks linksBulk update of all project sitesChange the site path information for your upgrade project sites since they have been movedCan be done via SharePoint Central Admin
Publish all Projects with associated project sitesIssues and Risk links get updated when the project is publishedHave PM publish projects that were previously publishedAdministrator should NOT go and automatically publish all projects
Add Enterprise Project TypesUpgraded PWA site will only have Basic Project TypeManually AddEnterprise ProjectSharePoint Tasks ListPost-upgrade tasks
Migration Plan
Convert Project DB
• Convert 4 Project DB’s into 1 new Project DB
Upgrade and Mount Project DB
• Mount Project Database
• Test Project Database
• Upgrade Project Database
Mount and Upgrade Project Web Instance
• Mount Project Web Instance
• Test Project Web Instance
• Upgrade Project Web Instance
Enable PWA Feature
• Turn on feature for Project Site collection
Post Migration
• Add Enterprise Project Types
• Bulk Site Update
• Publish Projects
• Install/Review Customizations
Test
•
Plan Upgrade
• Plan for • Clients• Upgrading
customizations
• Multiple test cycles
Setup New Project 2013 Farm
• Review Hardware requirements
• Plan new farm topology
• SharePoint 2013 + Project Server 2013 running
Upgrade to Project Server 2010
• Follow established upgrade path from previous versions of Project
Preparing Project Server 2010
• Enable User AD sync
• Check DB Consistency and ownership
• Disable BCM
Migration Plan
Convert Project DB
• Convert 4 Project DB’s into 1 new Project DB
Upgrade and Mount Project DB
• Mount Project Database
• Test Project Database
• Upgrade Project Database
Mount and Upgrade Project Web Instance
• Mount Project Web Instance
• Test Project Web Instance
• Upgrade Project Web Instance
Enable PWA Feature
• Turn on feature for Project Site collection
Post Migration
• Add Enterprise Project Types
• Bulk Site Update
• Publish all Project
Test
• Test• Test• Test• And then
test more
Plan Upgrade
• Plan for • Clients• Upgrading
customizations
• Multiple test cycles
Setup New Project 2013 Farm
• Review Hardware requirements
• Plan new farm topology
• SharePoint 2013 + Project Server 2013 running
Upgrade to Project Server 2010
• Follow established upgrade path from previous versions of Project
Preparing Project Server 2010
• Enable User AD sync
• Check DB Consistency and ownership
• Disable BCM
Plan UpgradeLearn
• Upgrade methods• New capabilities• Downtime mitigation
Prepare• Document environment• Manage customizations• Plan upgrade strategy• Make items upgradable
Test• Build test farms• Use real data• Evaluate techniques• Find issues early
Implement• Build/upgrade farms• Deploy customizations• Minimize downtime• Monitor progress
Validate• Troubleshooting• Upgrade event failures• UI/UX issues• Data issues
PC318 - Project Server 2013 Deployment Best Practices from the field
MyPC fill out evaluations & win prizes!
Fill out session evaluations by logging into MyPC on your laptop or mobile device.
Evaluation prizes daily! Claim your prize at the Registration Desk on Level 1.
www.msprojectconference.com
After the event, over 100 hours of resources; including all of the PPT decks and session videos will be available.
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. 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 provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.