Periodic tasks for Project Server administrators

Applies to: Project Server 2016, Project Server 2013

This article describes periodic checks Project Server admins should perform to maintain their environments. It was contributed by Microsoft Senior Premier Field Engineer Brooks White. (To access this link you will need a LinkedIn account)

Project Server administrators should perform the following periodic checks to their environment as an important part of their job:

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.
Review application and event logs on web front end (WFE) servers, APP servers and the SQL Server.
Use the Unified Logging Service (ULS logs) as needed, based on the finding in the application and system event logs. Use the Merge-SPLogFile PowerShell cmdlet to filter output from all servers.
Check Active Directory synchronization jobs to ensure they were successful.
Update Resource Breakdown Structure (RBS) values for new users. Newly synched users won't have an RBS.
NOTE - This may be the job of the PMO.
Clear any overly long delegation sessions in Server Settings
Maintain a valid enterprise resource pool by checking for users who haven't logged in for 60 days and find out why. For example, they may have left the company, are unaware of PWA, or could have been added mistakenly when someone else needed access.
Check the ADMINISTRATORS group for admins that should be removed.
Provide timesheet training to new users.
Provide project manager training to new project managers.
Close timesheet periods for the previous quarter plus one or some similar period. For example, if you are in Q4, close the timesheet reporting periods for Q2. The interval will be based on business or reporting needs.
Check with the project manager first, then close tasks to updates on projects that are complete or mostly compete or that have older tasks.
Archive and delete projects/sites for old completed project plans. But first create an archive plan that is documented and adhered to.
> [!NOTE]> Generally speaking, don't ever delete any resources from Server Settings
Delete timesheets from the past. Again, this will be defined by a policy that is based on business needs for reporting timesheet data.
Create fiscal periods for the next calendar year.
Create timesheet periods for the next calendar year. The prefix might equal "Week.", starting at 1, and the suffix might be the calendar year, such as ".2016". Week 1's period will show as "Week.1.2016".
Consider deleting timesheets for long-ago periods.