#ProjectServer 2010 and #SQL 2012 #TechNet documentation updated #PS2010

March 26, 2012 at 4:21 pm | Posted in Configuration, Information, Installation | Comments Off on #ProjectServer 2010 and #SQL 2012 #TechNet documentation updated #PS2010
Tags: , ,

The hardware and software TechNet documentation for Project Server 2010 has now been updated to show support for SQL Server 2012:


SharePoint 2010 and Project Server 2010 must have Service Pack 1 installed to use SQL Server 2012 to host the farm databases.

#ProjectServer 2010 and #SharePoint 2010 performance analysis using PAL #paltool #PowerShell #PS2010 #SP2010 #Windows

March 21, 2012 at 4:12 pm | Posted in Administration, Performance, PowerShell | 2 Comments
Tags: , , ,

A really useful tool for analysing Performance Counter logs is PAL – Performance Analysis of Logs.


This is primarily a PowerShell tool with a GUI interference available to download from CodePlex:http://pal.codeplex.com/. The tool can be used to generate your Perfmon Templates, then to analyse the logs and create a nice HTML report output.

A quick overview of the tool and usage for monitoring Project Server can be found below.

From the Welcome tab switch to the Threshold tab as shown below:


There are preconfigured Threshold files including one specifically for Project Server. In this example I have created a custom threshold file that includes Project Server, IIS and SP2010:


Now export the threshold file out to a Perfmon template:


Now load the Performance Monitor and expand Data Collection Sets, right click on User Defined > New > Data Collection Set.

Give the data set a name and check the radio button “Create from template”


Click Next then Browse:


Navigate to the location of the new Template created earlier and open the template:


Click Finish. The new data collection set will appear under User defined.

Start the new data collection set when you are ready to monitor the performance counters:


Once the monitoring session has completed stop the data collection:


Now load PAL and click on the Counter Log tab and add the output file (blg file) from the counters data collection:


Now click on the Questions tab and answer the questions listed. Once answered, click on the Output Options tab and set the analysis interval, in this example I have left it to auto:


Now access the File Output tab to set the output directory and the chosen output format and file name:


Clicking on the Queue tab will display the variables used for the PowerShell script:


Click on the Execute tab and click Finish to Execute now:


The log will now be processed and generate the report:



Once completed the report will load in Internet Explorer:



Thanks to my colleague Chris Stretton who gave me a demo of this tool. For an excellent description of the options available on the GUI interface see Chris’s post here:


#ProjectServer 2010 and #SharePoint 2010 build versions #SP2010 #PS2010 #MSProject

March 9, 2012 at 5:31 pm | Posted in Administration, CU, Information, Installation, Service Pack | Comments Off on #ProjectServer 2010 and #SharePoint 2010 build versions #SP2010 #PS2010 #MSProject
Tags: , , , ,

Project Server 2010 and SharePoint 2010 build versions and KB article links thanks to my colleague Giles Hamson:



#ProjectServer 2013 / 2010 / 2007 high-level Audit Export via #PowerShell #MSProject #PS2010 #EPM

March 5, 2012 at 6:15 pm | Posted in Add-on, Administration, PowerShell, PSI, Reporting | 1 Comment
Tags: , , , , , , ,

Quite often there is a request for audit information from Project Server but unfortunately there is nothing available out of the box. This post covers a very high-level solution to this using the Project Server PSI and PowerShell.

Most actions in Project Server are processed via the Project Server queue, one simple way to get high-level audit information is to extract the queue information. The following PowerShell script uses the ReadAllJobStatusSimple method from the Queue System web service to export yesterdays processed jobs into a txt file with yesterday date appended to the filename:

The script can be downloaded from the script center:


$Today = Get-Date
$Yesterday = $Today.AddDays(-1).ToString(“yyyy-MM-d”)
$Filename = “C:\PSAuditExport\QueueExport-”
$filetype = “.txt”
$svcPSProxy = New-WebServiceProxy -uri “http://vm353/pwa/_vti_bin/PSI/QueueSystem.asmx?wsdl” -useDefaultCredential
$svcPSProxy.ReadAllJobStatusSimple(“$Yesterday 00:00:01”, “$Yesterday 23:59:59”, “200”, “0”, “QueueCompletedTime” ,”Ascending”).Status | Export-CSV $Filename$Yesterday$filetype -Delimiter “|”

Update the filename variable and PWA URL, save the script and execute using a batch file that is scheduled via the Windows task scheduler sometime after midnight to get yesterdays jobs. An example command needed in the batch file is below:

“%SYSTEMROOT%\system32\windowspowershell\v1.0\powershell.exe” -command “& ‘C:\QueuejobstatusAudit.ps1′”

Once executed this will export all of the jobs for that day to a text file in the specified location, in this case C:\PSAuditExport as shown below:


An example export looks like this:


The export could then be used for auditing purposes. For example, to see who saved or published a particular project you could search for the Project GUID in the export file and find the GUID’s of the Resources / users that saved or published that project on that particular day.

This is a very simple solution that I put together for the purpose of this post, this could be taken a lot further and made into a production solution.

#ProjectServer and #SharePoint 2010 February 2012 Cumulative Update #PS2010 #SP2010 #MSProject

March 1, 2012 at 2:04 am | Posted in CU | Comments Off on #ProjectServer and #SharePoint 2010 February 2012 Cumulative Update #PS2010 #SP2010 #MSProject
Tags: , , , ,

The Office 2010 February 2012 Cumulative Updates are now available, please see the links below:


Project Server 2010 Server Roll up package February 2012 CU (Recommended):

Project Server 2010 February 2012 CU (Included in the Server Roll up package):

Project 2010 February 2012 CU:

As always, test these updates on a test environment before deploying to production.

Create a free website or blog at WordPress.com.
Entries and comments feeds.