Real world problems upgrading to Project Server 2013

I recently helped a customer upgrade from Project Server 2010 to Project Server 2013. In the course of preparing, testing, and then running the actual upgrade, we ran into 7 problems that affected the upgrade. I want to share these so you can include them in your upgrade planning. These problems can be planned for…

2

"From the Trenches" white papers about enterprise project management

Whether you're new to project management or a seasoned professional, it can be helpful to have resources, such as white papers, from experts in the field. Project community experts, including Microsoft MVPs and partners, have submitted the following white papers for our "From the trenches" collection. These white papers contain useful information that can help…

0

Periodic Tasks for Project Server Administrators

Periodic Tasks for Project Server Administrators   Daily Check the queue for Failed and Blocking jobs.  Review the errors related to failed and blocking jobs to troubleshoot. Check for nightly cube build failures. Cancel Failed and Blocking jobs. Weekly Review application and event logs on WFEs, APP servers, and the SQL Server. Use the ULS…

4

"Reporting (Project Sync)" queue job when linking tasks to risks.

A customer pain point brought to my attention this week is related to linking tasks to risks from PWA vs linking risks to tasks via the project site’s Risks list.   The customer noticed that, in Project Server 2010, linking a task to risk from PWA’s drill down view of the project schedule does not…

0

MUST READ: "Project Server and Synchronizing Users to Project Sites" by Brian Smith

Brian Smith has posted a very interesting blog article about synchronizing users in Project Server 2010 versus Project Server 2013.  He says there are behavior differences between Project Server 2010 and Project Server 2013 regarding user synchronization to project sites.  I quote, "One key part of this change should be taken into account when migrating…

0

Best Practices for Project Server 2010, 2013, and Online Permissions

The cardinal rule of permissions: Keep It Simple   The highest rule of permissions best practice is to keep your permissions scheme simple.  If you can use the default categories, groups, and permissions with only minor changes, or none at all, do so! Avoid creating unnecessary groups and categories. Having a large number of groups…

0

Find and Manage Updates for SharePoint 2010/2013 and Project Server 2010/2013

I've always maintained a list of my own links to updates, but I learned of these two links today.  You can find and manage updates for SharePoint and Project Server with these two links.  I hope you find this useful; they both hold a coveted spot in my favorites for CUs now. Find and manage…

0

Can I make changes to the Reporting DB?

A customer asked me today if he could make changes to the Reporting database in his Project Server 2010 environment.  The short answer is, yes, you can create entities in the Reporting database.  Below is a scrubbed version of the conversation. Customer: I have a request from the business to create one or more custom…

0

Add AD group to all PWA project sites with Read Only permission using PowerShell

Until I can figure out who to cross post between the Project Server PFE Team Blog and my own blog, I will double post. My customer wanted to be able to provide his Portfolio Managers with read only access to all project sites in PWA.  Because an AD group for Portfolio Managers already exists, we…

0

Pretty darned useful – "Merge-SPLogFile" cmdlet

My favorite ULS logging PowerShell command is described here:  http://technet.microsoft.com/en-us/library/ff607721.aspx.  The Merge-SPLOgFile cmdlet pulls trace log entries from all farm computers into a single log file on the local computer and it works in Project Server 2010 and 2013, too.  I can hand this link to customers and they can run the Merge-SPLogFile command from…

4