Project Server 2013 Deployment Best Practices from the field
Anaheim, CA | February 2-5, 2014 PC318 Project Server 2013 Deployment Best Practices Raphael the Ax, Akbar Guffar, Artem from field Khlobystin Premier Field Engineering Microsoft Basic Requirements Software Requirements
SQL Server SQL Server 2012 SQL Server 2008 R2 with SP1 Database Engine Management tools Connectivity comp SQL Server Agent SQL Server 2014 not yet supported Analysis Services Reporting Services Software Requirements Application & WebFrontend Server
Windows Server 2012, Standard Edition Enterprise Edition Datacenter Edition Windows Server 2008 R2 SP1 (64Bit), Standard Edition Enterprise Edition Datacenter Edition R2 not supported SP1 will add support Server Core install not supported
SharePoint Server 2013 Enterprise Edition Project Server 2013 Application Server role Web Server role PowerShell SP prerequisite installer Software Requirements Additional Features Task Sync: Exchange Server 2013
AD Sync: Windows Server 2003 AD (min.) Outlook 2003 - 2013 Internet Explorer 8 as minimum, 10-11 recommended Firefox, Safari & Chrome supported Reporting: Excel 2010 2013 Odata: Excel 2013 Visual Reports: Excel 2007 2013 Visio 2007 - 2013
Workflow Editing: SharePoint Designer 2013 Visio 2013 Visual Studio 2012 Requires Workflow Manager Client 1.0 execution engine Minimum Hardware Requirements Single-Server deployment CPU: 64-Bit, fourcore, 2.5Ghz RAM: 24GB Not recommended for production use
Recommended Hardware Three-tiered Infrastructure CPU: 64-Bit, fourcore, 2.5Ghz RAM: 16GB CPU: 64-Bit, fourcore, 2.5Ghz RAM: 16GB CPU: 64-Bit, fourcore eight-core, 2.5Ghz RAM: 32GB 64GB Scale-out each tier based on dataset requirements Recommended infrastructure Ideal world for Project Server Located in same datacenter
Load Balancer Crawler WFE1 WFE2 Search Project Server Project Server DB1 DB2
ShareP oint SA Architecture Project Server 2010 Architecture Project Server 2013 Architecture Project Professional 2013 WFE Browser 3rd party onpremises applications
PowerShell ASPX Pages Web Services WCF Endpoints Business Business Objects BusinessObjects Objects CSOM SharePoint Apps
OData Forwarder Queue draft publish dbo archive Calc cubes Business Business Objects
content Workflo w config Azure Workflow Project Server 2013 Architecture WFE Web Frontend ASPX Pages Web Services Business Business
Objects BusinessObjects Objects WCF Endpoints CSOM OData Forwarder Reduced page load times/ WAN optimizations through PSI forwarder Direct Business Objects database queries for non-queue nonPCS jobs Claims authentication cookie tracked at the DCache Service level
SOAP-based ASMX interface for PSI still available but deprecated Project Server 2013 Architecture Application Server App WCF Endpoints Eventin g Queue Calc Business Business Objects
BusinessObjects Objects Workflo w Azure Workflow Project Calculation Service (server-side & client-side share same scheduling engine) Queue service optimization, reduced number of database requests Active Directory Synchronization Improvements Project Server 2013 Architecture draft publish
dbo archive cubes SharePoint Project SQL Database Server content config Only one single Project database (dbo. for Reporting schema) Optimized security validation
Data transfer improvements (i.e. using Table Value Parameters) SQL maintenance jobs General Deployment Scenarios Separate Project Server Farm Yes Integrate Integrate; 20.00% Include Project Sites into global/ large SharePoint infrastructure Leverage global SharePoint farm hardware No Separate Departmental considerations
Avoid additional license costs (depending on SharePoint infrastructure) Different patch/ update cycles maintenance procedures Optimize operations based on specific requirements Separate; 80.00% Interoperability Backward Compatibility No! You cannot connect to Project Server 2013 with Project Professional 2010 SQL Server Best Practices
Why focus on SQL? ProjectWebA pp More than 90% of SharePoint and Project Data is stored in the databases All Project and Portfolio Management (PPM) data Time tracking and Timesheet data Aggregated SharePoint project site data When planning SQL Performance
Security High Availability Manage and Monitor Security Authentication Authorization Connection encryption Data encryption Firewall Antivirus Performance Dedicated instance
Benchmark the I/O subsystem More disks or faster disks SQL Edition Tempdb: File placement Number of data files Timer job to determine and repair fragmentation ProjectWebApp: Data and log file
placement Manage autogrowth Statistics are updated using built in SQL functionality hitting the threshold Schema changes not supported Monitor! High Availability SQL 2012 AlwaysOn AG
Concurrency Split of roles Geographic distribution Issues, Risks and Deliverables Custom Calendars Usage patterns: Workload conditions Average time between page requests Average session time Payload of Pages
Line of Business Integration Virtualization Capacity Planning Typical datasets in Project Server 2013 Small dataset: 20 projects 62.5 tasks per project 50 resources 3 calendars 2600 timesheets per year Medium dataset: 100 projects
250 tasks per project 1000 resources 26 calendars 52000 timesheets per year 5 EPTs Large dataset: 5000 projects 10000 resources 100 calendars 780000 timesheets per year 50 EPTs 30 workflows
100 departments Dataset requirements Small to large WFE/APP: 4 cores, 2.5 GHz per core; 16 GB of RAM; 80 GB of hard disk Virtualization Things to keep in mind Virtualization does not provide parity with physical machines Virtualizing SQL Server requires additional consideration Plan your Project Server deployment, build your virtualization plan around it Top Performance Bottlenecks AD Sync Database
Locks Database Server Disk I/O WFE CPU Utilization Server Memory Utilization Database Server CPU Utilization
Distributing data files Limit the number of projects and fields shown in a given view Limit the number of custom fields you utilize, especially at the task level and containing formulas Add additional WFE servers to the farm Scale up the WFE servers by adding higherspeed processors APP Server CPU utilization
Monitor at which tier memory usage is a bottleneck and investigate why Optimize workload (run jobs at nonworking hours when possible), optimize SQL
Purchase and install additional memory for that tier (scale up) Purchase additional servers to handle the load (scale out) Capacity Top Recommendations Technical and operational Implement best practices across all technologies Regularly monitor settings and performance
counters Invest in appropriate SQL Server: Ideally hardware Separate drive for data files and logs Separate drive for TempDB RAID 5, ideally RAID10 Use separate servers for every
role Scale-up and scale-out (check the ratio) Use high speed disks (10K, 15K) Keep an eye on network connection (100 mbps, 1 Gb/s, latency of 1 ms) Optimize: Security settings Views and custom fields Page payload
Queue Workload processes Workflows Custom solutions Teach users: Baselining Working with master projects Creating cross project links Using local custom fields Capacity Highlights
Determine the dataset to match current workload and expectations Implement recommended hardware/ virtual topologies Monitor your farm and optimize according to Best Practices Deployment Options Prepare for deployment Arrangements Ensure you have necessary accounts:
Setup user Farm admin Application pool account (optional) PWA admin Workflow Proxy Report related groups Configure SSAS: Allow network access Add SSAS admin Deployment Options GUI vs PowerShell Use CA to provision WEB & service applications and PWA
Use PowerShell for same purposes PowerShell Option Pros & Cons Time saving Perfect for repeated installs where you want to guarantee consistency and minimize data entry glitches
Remote deployments, parallel binary installations Value in having consistently-named but automatically-created databases PowerShell advanced skills required Not possible to reconfigure during the run
GUI Option Pros & Cons User friendly Time consuming Requires ~200 level knowledge Complicated repeated Possible to revert or reconfigure at any step
GUIDs in databases names installations Deployment Top Recommendations Technical stuff Plan for deployment: Determine dataset Client requirements Exchange Integration
Browser Support (IE6 and 7 are not supported) Authentication Hybrid solutions not possible Review hardware and software requirements and follow accordingly Implement best practices across all technologies Create appropriate
guidelines and keep them up to date: Architecture and Design Installation and Patching Change Tracking Disaster Recovery Deployment Highlights Plan your deployment thoroughly Prepare for deployment Choose the right
installation method! Couple ready scripts: AutoSPInstaller Install Project Server 201 3 with Powershell by Jim Cox Upgrade Upgrade considerations No In-place Upgrade Only DB Attach Consolidation of Databases from 4 to 1
No direct upgrade path from Office Project Server 2007 to Project Server 2013 Upgrade to 2010 then upgrade to 2013 Upgrade Your Project Client Users Upgrade Cycle Plan & Prepare Document Settings Evaluate customizations Plan upgrade
strategy Test Build test environments Use real data Find issues Implement Build/upgrade farms Monitor progress Validate Troubleshooting Upgrade event Failures Data issues
Post Upgrade tasks Enable Issues and Risks links Add the Project Server 2013 Enterprise Project Types Verify forms authentication (if used) upgrade successfully Verify custom code Verify workflows
Verify Reports Verify your upgraded databases Common Problems PWA Site not upgraded Common Problems View failed to load After the Upgrade Connect to PWA via Web and Project Create a new
enterprise project Check Permissions and links still work Check Project Workspaces Check custom fields and Formulas Check Reports Monitor Be proactive not reactive ! Implement monitoring plan
Analyze logs on a regular basis Developer Dashboard Project Log Level Manager ULS logging for specific entity AddSPProjectLogLevelMana ger RemoveSPProjectLogLevelMa nager Add new entity to monitor Remove specific entity from monitoring
SetSPProjectLogLevelMan ager Update settings for monitored entity SetSPProjectLogLevelMana gerRefresh Update configuration cache Software Updates Preparation Testing sign Off Back up your environment Single deployment Packages
Installation Verification SharePoint Server 2013 and Project Server 2013 CU Updates Verify the database version Language packs Repeat steps for each server in your farm Run SharePoint Config wizard Review the ULS logs
Disaster recovery Don't wait till it is too late! Integrate; 20.00% Separate; 80.00% Related Sessions PC206 - First Impressions supporting Project Server 2013 and Project Online PC209 - Troubleshooting Tips for Project and Project Server PC310 - Project Worst Practice - Learning from other people mistakes PC315 - Microsoft Project Server 2013 Supercharged PC319 - Get your hands dirty with Microsoft Project Server 2013 architecture
PC328 - Get over the hurdles - Upgrade and Migration to Microsoft Project Server 2013 PC400 - The Great Database Consolidation, Project Server 2010 to 2013 Migration in 8 Easy Steps Q&A Raphael Ax - [email protected] Akbar Guffar - [email protected] Artem Khlobystin - [email protected] MyPC fill out evaluation s Fill out session evaluations by logging win into &
MyPC on your laptop or mobile device. prizes! 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 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.
English Language Arts & LiteracySummer Academies. Dates & Venues. June 3 & 4, 2014 Kennesaw State University. June 11 & 12, 2014 Coastal Georgia Center ... Walpole/McKenna: Comprehensive Reading Solutions. Assessment Team. Summer Academy Presenter Proposal Form.
The Holland codes help us determine what your personality type is, which can also be a clue as to which type of jobs best suit you. There are six Holland codes. Most people have a dominant one and a secondary...
Be intelligent : Define the purpose and scope of each Gateway Define the roles and responsibilities of each Gateway Define the possible outcomes of each Gateway Prepare for each Gateway, Learn from each Gateway Governance tools - Gateways Sponsor Outcomes...
(Because the initial population is small compared to the carrying capacity, you can take k to be an estimate of the initial relative growth rate.) The model for a growth function for a limited population is given by the Gompertz...
They are wise and will make decisions for the good of the people Philosophy Regarding People: mistrusts the masses (people), incapable of ruling themselves. Aristotle DATES: 384-322 BCE TEACHER: Student of Plato FROM: Athens Wrote the book "Politics" Studied governments...
Theory X suggests that employees dislike work, avoid responsibility, have little ambition, and are motivated by threat and fear. Theory Y argues that people like work, seek responsibility, and are motivated by empowerment. If a manager believes theory X or...
IP Address가 192.168.254.1에서 192.168.254.253 사이의 한 값으로 설정되고 Subnet Mask가 255.255.255.0, Default Gateway가 192.168.254.254이어야 한다. [c:\]ipconfig Windows IP Configuration Ethernet adapter 로컬 영역 연결: Connection-specific DNS Suffix .
Ready to download the document? Go ahead and hit continue!