Periodic Tasks for Project Server Administrators


Periodic Tasks for Project Server Administrators

 

Daily

  1. Check the queue for Failed and Blocking jobs. 
  2. Review the errors related to failed and blocking jobs to troubleshoot.
  3. Check for nightly cube build failures.
  4. Cancel Failed and Blocking jobs.

Weekly

  1. Review application and event logs on WFEs, APP servers, and the SQL Server.
  2. Use the ULS logs, as needed, based on the finding in the application and system event logs. Use merge-splogfile PowerShell cmdlet to filter output from all servers: https://technet.microsoft.com/en-us/library/ff607721(v=office.15).aspx
  3. Check AD synchronization jobs to ensure they were successful.
  4. Update resource RBS values for new users.  Newly synched users won’t have an RBS. Note: this may be the job of the PMO.
  5. Clear any overly long delegation sessions in Server Settings > Delete Enterprise Objects > User Delegation.

Monthly

  1. Provide Timesheet training to new users.
  2. Provide Project Manager training to new project managers.

Quarterly

  1. Close timesheet periods for the previous quarter plus 1.  For example, if you are in Q4, close the timesheet reporting periods for Q2.
  2. Check with the Project Manager first, then close tasks to updates on projects that are complete, mostly compete, or have older tasks.
  3. Archive and delete projects/sites for old completed project plans.  (But first, create an archive plan that is documented and adhered to.)
  4. Generally speaking, don’t ever delete any resources from Server Settings > Delete Enterprise Objects.
  5. Delete timesheets from the past.  Again this will be defined by a policy that is based on business needs for reporting timesheet data.

Semi-annually

  1. No recommendations, currently.

Yearly

  1. Create fiscal periods for the next calendar year.
  2. Create timesheet periods for the next calendar year. 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.
  3. Consider deleting timesheets for long ago periods.

Originally posted at http://blogs.technet.com/b/brookswhite.

Comments (0)

Skip to main content