Lessons Learned Project Server 2003 Sean Pales Bennett Adelson

Agenda Introduction Introduction Designing a Scalable Architecture Designing a Scalable Architecture Common Project Server Mistakes Common Project Server Mistakes Q & A Q & A

Who Are We? Bennett Adelson Enterprise Project Management is a division of Bennett Adelson  What does this mean?  Microsoft’s go to partner for EPM in Ohio  Core focus and competency is EPM  Proven record of successful Project Server implementations  Highest quality developers and implementation specialist

Who Am I? Director of Bennett Adelson Enterprise Project Management Director of Bennett Adelson Enterprise Project Management Microsoft Project user for over 5 years Microsoft Project user for over 5 years Frequent contributor to Microsoft Newsgroups Frequent contributor to Microsoft Newsgroups Former telecom analyst for New York based investment bank Former telecom analyst for New York based investment bank

Designing a Scalable Architecture

Top 5 Scalability Killers 1. Inadequate network infrastructure 2. Inadequate database hardware 3. No Pilot 4. Undefined project management practices 5. Unrestricted access to data

Logical Architecture Project Server IIS, ASP Pages Project Data Service XML Web Service View Processing Svc NT Service Session Mgmt Svc NT Service Scheduled Action Svc NT Service Trace Service NT Service Sharepoint “Front-End” IIS WSS DBPS Core DBPS Views DB PS Projects DB

Logical Architecture Project Server IIS, ASP Pages Project Data Service XML Web Service Sharepoint “Front-End” IIS WSS DBPS Core DBPS Views DB PS Projects DB

Web Server Options Single Server Single Server Dual Servers Dual Servers Single Cluster Single Cluster Dual Clusters Dual Clusters

Single Server Simplest setup Simplest setup Scale limited to size of hardware Scale limited to size of hardware Project Server IIS, ASP Pages Project Data Service XML Web Service Sharepoint “Front-End” IIS

Dual Server Separate WSS and Project Server Separate WSS and Project Server Allows ‘right sizing’ of each server based on use Allows ‘right sizing’ of each server based on use Use when significant WSS usage is expected outside of project server Use when significant WSS usage is expected outside of project server Project Server IIS, ASP Pages Project Data Service XML Web Service Sharepoint “Front-End” IIS

Project ServerPDSWSS Project ServerPDSWSS Single Cluster Efficient use of less expensive hardware Efficient use of less expensive hardware Flexibility of maintenance and adding capacity Flexibility of maintenance and adding capacity Use when balance of WSS to PS usage unknown Use when balance of WSS to PS usage unknown Project ServerPDSWSS

Dual Cluster Max flexibility in adding capacity as required Max flexibility in adding capacity as required Separate admin and maintenance orgs Separate admin and maintenance orgs Max capacity strategy Max capacity strategy Project ServerPDS Project ServerPDS Project ServerPDS WSS

Views Processing Options On Web Server On Web Server Separate Server Separate Server Multiple Separate Servers Multiple Separate Servers On Database Server On Database Server

Project Server IIS, ASP Pages Project Data Service XML Web Service Sharepoint “Front-End” IIS Views on Web Servers Default option Default option Only supported when using a single PS web server Only supported when using a single PS web server View Processing Svc NT Service

PSPDSWSS Views on Separate Server Required for clustered PS web servers Required for clustered PS web servers Increased publishing capacity Increased publishing capacity Single processor speed is critical Single processor speed is critical View Processing Svc NT Service

PSPDSWSS Views on Multiple Server New capability in SP1 New capability in SP1 Not ‘clustered’, additional separate servers Not ‘clustered’, additional separate servers Single processor speed is critical Single processor speed is critical View Svc

Views on Database Server Eliminates network overhead during publish Eliminates network overhead during publish Increased publishing speed Increased publishing speed Single processor speed is critical Single processor speed is critical View Processing Svc NT Service PS Views DB

Database Partition Options Single Database Single Database Two Databases Two Databases Three Databases Three Databases

Single Database All three logical table sets on one machine All three logical table sets on one machine Default install option Default install option WSS DB PS Core DB PS Views DB PS Projects DB

Two Databases Separate server for views data Separate server for views data Supported through PS Installer Supported through PS Installer WSS DB PS Core DB PS Views DB PS Projects DB

Three Databases Separate server for views data Separate server for views data Separate server for project data Separate server for project data Requires use of command line tools Requires use of command line tools WSS DB PS Core DB PS Views DB PS Projects DB

Multi-Site Configurations Multiple Project Server web sites on single hardware platform Multiple Project Server web sites on single hardware platform Separate database (not server) per Project Server site Separate database (not server) per Project Server site Additional flexibility for views processing and database layout Additional flexibility for views processing and database layout

Multi-Site Front End Single or Dual web server clusters for all sites Single or Dual web server clusters for all sites Number servers based on total number of concurrent users supported Number servers based on total number of concurrent users supported Project ServerPDSWSS Project ServerPDSWSS Project ServerPDSWSS

Views Processing Options Multiple sites per views server Multiple sites per views server Multiple views servers per site Multiple views servers per site Site 2 Site 3 Site 1 View Svc

Database Options Multiple servers, partition by site Multiple servers, partition by site Multiple servers, partition by usage Multiple servers, partition by usage Multiple servers, partition by function Multiple servers, partition by function Site 3 Site 1 Site 4 Site 2 Site 1 Core Site 1 Views Site 2 Core Site 2 Views

10 Common Project Server Mistakes

Mistake #10 Problem: PWA Users receive a “size limit error” when submitting Status reports Problem: PWA Users receive a “size limit error” when submitting Status reports Mistake: There are limits on the volume of text users can submit through status reports’ ActiveX control Mistake: There are limits on the volume of text users can submit through status reports’ ActiveX control Resolution: Resolution:  Submit smaller quantity of text  Use WSS, InfoPath or “other”

Mistake #9 Problem: Portfolio Analyzer reports are not interactive Problem: Portfolio Analyzer reports are not interactive Mistake: A licensed Office 2003 product has not been installed Mistake: A licensed Office 2003 product has not been installed Resolution: Resolution:  Install an Office 2003 product (isnt this PWA?)  Unregister and Reregister the PWA DLL

Mistake #8 Problem: After installing WSS, the Project Server site or pages with grid controls won’t load Problem: After installing WSS, the Project Server site or pages with grid controls won’t load Mistake: WSS installed after Project Server Mistake: WSS installed after Project Server Resolution: Resolution:  Install WSS first  Modify the Exclude list

Mistake #7 Problem: You’ve upgraded from STS ’02 to WSS ’03 and issues have not migrated Problem: You’ve upgraded from STS ’02 to WSS ’03 and issues have not migrated Mistake: Failed to run STSWiz.exe after running OWS1002.exe Mistake: Failed to run STSWiz.exe after running OWS1002.exe Solution: Solution:  Run STSWiz.exe before running PSMIGRAT.exe

Mistake #6 Problem: Project Professional users receive Spooler Error 0x80040E14 when publishing Problem: Project Professional users receive Spooler Error 0x80040E14 when publishing Mistake: PWA users self-assign themselves to tasks and Project Managers assign that user to the same task Mistake: PWA users self-assign themselves to tasks and Project Managers assign that user to the same task Resolution: Resolution:  Change your company’s processes  Hotfix (not included in SP1)

Mistake #5 Problem: Users receive login error when trying to download new assignments Problem: Users receive login error when trying to download new assignments Mistake: IE Security allows for ONLY “Automatic logon only in the intranet zone” Mistake: IE Security allows for ONLY “Automatic logon only in the intranet zone” Resolution: Resolution:  Set IE Security to “Automatic logon with current user name and password”

Mistake #4 Problem: Timesheet doesn’t reflect changes to Tracking settings Problem: Timesheet doesn’t reflect changes to Tracking settings Mistake: Project Professional users have failed to Re-Publish assignments Mistake: Project Professional users have failed to Re-Publish assignments Resolution: Resolution:  Republish All Project Plans

Mistake #3 Problem: OLAP Cube fails to build! Problem: OLAP Cube fails to build! Mistake: This could be a number of things, but one of the main reasons is the existence of special characters in the ERP and/or EROCs Mistake: This could be a number of things, but one of the main reasons is the existence of special characters in the ERP and/or EROCs Resolution: Resolution:  Refrain from using special characters in the ERP and/or EROCs

Mistake #2 Problem: Project Server fails after installing a hotfix or service pack! Problem: Project Server fails after installing a hotfix or service pack! Mistake: Not reading the instructions Mistake: Not reading the instructions Resolution: Resolution:  Install in Test Environment  Make backups  Read ALL of the instructions

Mistake #1 Problem: Performance Issues! Problem: Performance Issues! Mistake: Poor Planning Mistake: Poor Planning Resolution: Resolution:  Talk to Experts!  Plan, Plan, Plan… Plan  Proof of Concept  Explore Configuration Planning Guide  Test Pilot  Small Rollouts

How to contact us Bennett Adelson Bennett Adelson   Sean Pales  ext. 103  ext. 103 

Thank you for attending

Q & A ?