I am excited to announce that I will once again be speaking at the Australian SharePoint Conference this time in Melbourne on the new Work Management capabilities of SharePoint & Project Server 2013. Hopefully this time the demo gods will be on my side and Project’ Sync to SharePoint will work. The abstract for the session is: If you have ever tried to track work in SharePoint, lists or even on pieces of paper, you are going to love the new Work Management capabilities of SharePoint 2013.

I thought I would post this little gem so I don’t forget it. Hopefully it will be of use to someone else as well. In the last couple of weeks a few people have told me about issues they encountered running Project Server 2010 workflows on a farm where the web front-end service has been deactivated. Deactivating the service can make sense if you are configuring the farm for improved performance by removing the need to listen to and render pages, or when trying to reduce the attack surface (although this is a lesser concern).

The process of upgrading from Project Server 2010 to Project Server 2013, or migrating between environments can be quite complex, requiring a number of steps to be completed in the correct order. In this post, I am going to document some of the common and uncommon errors that you may run into. I also intend to update this post as I uncover more. Unmounted Project Service Database Unlike SharePoint Content databases, Project Service databases need to be mounted before you can run a Test against them.

A common requirement when setting up a new Project Server instance, is to replicate production data back into another environment such as Development or Test. In doing so, you have an environment where you can develop, test configuration changes or even perform training against, without impacting your production Project Server instance. In this post we will walkthrough migrating data from our production Project Server 2013 environment which will be the source, over to a development / test environment which will be the target using the simple and fool-proof database attach method.

In this post I am going to take you through the process of migrating Project Server 2010 into Project Server 2013. Usually there are two ways of doing a migration, either an in place upgrade, where if you were particularly brave, you would take your production system and then run the installer for the new binaries on it to upgrade. I say ‘Brave’ because frequently this method of upgrade would be fraught with danger, not giving you sufficient options for dry runs or rolling back.

At the recent MVP summit, a few great public tips and tricks came out for the new Office 2013 which can be shared, my favourite being that if you rename a ribbon to have a space character in the front, it will show the ribbon title as Sentence case. But there was one gem that the team didn’t share, which a little poking around with a hex editor and procmon has highlighted.

SharePoint Designer 2013 is another tool that provides a means for building workflows, what is new in the 2013 release is it can now build Demand Management workflows for Project Server 2013 and Project Online. Now I am not going to go into the specifics of the tool, as you probably already know my preference, but irrespective of that, I thought it important to share how to build workflows that leverage the Skip to Stage functionality with SPD.

One of the most obvious differences between Project Server 2013 and 2010 is the look and feel, specifically the new modern UI style tiles to help you perform tasks / find options quickly and easily called ‘The Carousel’. On a un-customised PWA site you will see two rows of these tiles, the ‘Getting Started’ and the ‘Track your work’ options. For a while I have been thinking about how powerful one of these carousels would be within your own organisation, perhaps providing a direct link to view the queue, a link to that report everyone uses, a central lessons learned register, a PMO site, or even your favourite EPM / PPM blog.

I try not to mix my day job at Nintex with my community work and the content on this site, but today I want to make an exception and share some news on one of the projects I have been working on for the past few months. I am pleased to announce that we have shipped Nintex Workflow for Project Server 2013 (NW4PS), an update to the popular workflow product for Project Server 2013.

I am excited to announce that I will be speaking at the upcoming Australian SharePoint Conference in Sydney on the new Work Management capabilities of SharePoint & Project Server 2013. The abstract for the session is: If you have ever tried to track work in SharePoint, lists or even on pieces of paper, you are going to love the new Work Management capabilities of SharePoint 2013. With SharePoint 2013, your organisation has access to a task management solution that can start simply and scale up to the enterprise level at the click of a button.