1 / 38

Lessons Learned Project Server 2003 Sean Pales Bennett Adelson

Lessons Learned Project Server 2003 Sean Pales Bennett Adelson. Agenda. Introduction Designing a Scalable Architecture Common Project Server Mistakes Q & A. Who Are We? . Bennett Adelson Enterprise Project Management is a division of Bennett Adelson What does this mean?

adele-madden
Download Presentation

Lessons Learned Project Server 2003 Sean Pales Bennett Adelson

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Lessons Learned Project Server 2003 Sean PalesBennett Adelson

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

  3. 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

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

  5. Designing a Scalable Architecture

  6. Top 5 Scalability Killers • Inadequate network infrastructure • Inadequate database hardware • No Pilot • Undefined project management practices • Unrestricted access to data

  7. Web Server Options • Single Server • Dual Servers • Single Cluster • Dual Clusters

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

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

  10. Single Cluster • Efficient use of less expensive hardware • Flexibility of maintenance and adding capacity • Use when balance of WSS to PS usage unknown WSS Project Server PDS WSS Project Server PDS WSS Project Server PDS

  11. Dual Cluster • Max flexibility in adding capacity as required • Separate admin and maintenance orgs • Max capacity strategy WSS Project Server PDS WSS Project Server PDS WSS Project Server PDS

  12. Views Processing Options • On Web Server • Separate Server • Multiple Separate Servers • On Database Server

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

  14. Views on Separate Server • Required for clustered PS web servers • Increased publishing capacity • Single processor speed is critical WSS PS PDS View Processing Svc NT Service

  15. Views on Multiple Server • New capability in SP1 • Not ‘clustered’, additional separate servers • Single processor speed is critical View Svc WSS PS PDS View Svc

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

  17. Database Partition Options • Single Database • Two Databases • Three Databases

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

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

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

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

  22. Multi-Site Front End • Single or Dual web server clusters for all sites • Number servers based on total number of concurrent users supported WSS Project Server PDS WSS Project Server PDS WSS Project Server PDS

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

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

  25. 10 Common Project Server Mistakes

  26. Mistake #10 • 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 • Resolution: • Submit smaller quantity of text • Use WSS, InfoPath or “other”

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

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

  29. Mistake #7 • 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 • Solution: • Run STSWiz.exe before running PSMIGRAT.exe

  30. Mistake #6 • 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 • Resolution: • Change your company’s processes • Hotfix (not included in SP1)

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

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

  33. Mistake #3 • 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 • Resolution: • Refrain from using special characters in the ERP and/or EROCs

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

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

  36. How to contact us • Bennett Adelson • www.BennettAdelson.com • Sean Pales • 1-877-328-7122 ext. 103 • 1-440-684-5000 ext. 103 • Spales@bennettadelson.com

  37. Thank you for attending

  38. ? Q & A

More Related