References for Project Server security and CUs

Hi Folks!

Project Server is a complete and complex solution which has been strongly documented over the years and versions. It cannot count how many time in a week I use my favourite search engine to look for some references. And the week after, I'll be surely looking for the same reference again!! 

Recently Brian Smith provided a tremendous blog where he listed (quite a gigantic job) all CUs for Project Server 2010 and 2013. It gave me the idea to do quite a similar job for the security references. We, Project admins, deeply rely on the security model which is quite complex and slightly changing at each version.

Thus I'm proud to provide you this simple table but saving it in your browser bookmarks might save you time!

Version	Global permissions	Categories	Default categories	Groups / templates	Changes versus previous version	Project CUs	Project Server CUs
2007	1	1	1	1	1	Non Applicable	Non Applicable
2010	1	1	1	1	Included in the global permissions article	1	1
2013	1	1	1	1	Included in the global permissions article	1	1

Hope you like it!

Edit 2015-03-30: in addition, I'll mention that this reference table might be particularly helpful due to the way the TechNet articles' URL are made. For example in many articles and blogs about Project Server 2010, the URL is referenced as "https://technet.microsoft.com/en-us/library/cc197631.aspx". When the Office version (ie 12 for 2007, 14 for 2010 and 15 for 2013) is not included in the URL, the latest version is automatically chosen. What is the consequence? While those blogs were first published, the lastest version was 2010, so it was fine. But now that the latest version is 2013, the articles/blogs about 2010 version refer to 2013 version. Quite not useful. That's why we include in this table URLs with the Office version (v=office.14 for example).

Edit 2015-04-15: it is not quite the same topic but talking about Brian's CU reference posts, I had the idea to include them in the above reference table, for both Project and Project Server. Kind of a reference of references...

View effective rights tool: now integrated to Project Server 2013

Much has been said on the 2013 release of Project Server, so it's kind of ambitious to write a brand new blog on the topic those days! But let's try!

Some of you guys surely faced the situation where a resource cannot access an object in Project Server? Or have been called on Monday morning by a gently customer and seeing that the security has been tweaked making a real mess?

Project Server 2007 PRK (Project Resource Kit) used to propose a "View effective rights" tool that allows the Project Server administrator troubleshooting issues regarding security settings and access control.

Here is basically what did it look like:

Figure 1: "view effective rights" tool in the PS2007 PRK

This tool has vanished in PS2010 (as far as I know..) and it is with a great pleasure that I'm presenting today the "view effective rights" functionality integrated to Project Server 2013!

It is pretty simple to use it, assuming of course you're using the Project Server permission mode. Just navigate to the server settings, then manage users. After selecting the culprit user, you can click on the "view effective rights" button.

Figure 2: "view effective right" in "manage users"

Then you'll be able to select from the drop-down list the type of rights you want to troubleshoot :

• Global permissions,
• Category rights for projects,
• Category rights for resources,
• Category rights for views,

Figure 3: type of rights selection

Figure 4: category rights on projects

Figure 5: category rights on resources

Figure 6: category rights on views

Try it and as an administrator you'll soon use it on a daily basis!

Do not open Projects in Edit Mode unexpectedly in Project Server 2013

If you are used to open projects in Project Professional in 2010 by double clicking on a project in the open window, you should know that the project is by default opened in edit mode and though checked-out.
Project Server 2013 is bringing here a nice improvement that I, as administrator, am really happy to welcome.
All Projects in Project Professional are by default opened in read-only mode and can be opened in edit whenever you want.

Then, while opened in Read Only , as for Office in 2010 and 2013, Microsoft introduced the "Notification bar" in Project 2013 allowing you to check-out the file.

I already hear you saying: "What about my modifications made while in read-only?". Don't worry, Project is clever enough to just check-out the project without reloading it. Any modification made in read-only mode are kept while checking out the project file


What if a co-worker changed the project in the meantime? Project will ask you to save you changes.

if you choose yes, it will ask you to find a place to save it before checking-out the file

You will have to pay attention while using the "Recent Projects" opening, by default, it will check-out the file for you!

From PWA the options are still the same : while clicking on the little workplan icon, the project will open in Edit mode to your computer MS Project and clicking the project link will open in Read only in PWA.

If you want to open in another manner, you'll have to select the line (not clicking the project link but next to it, this, I guess you're familiar) and select the proper open option from the rubban

You will never again lock a file without noticing it!