Changing owner in MSPS 2007

[FrankC]

I have administrator privileges and am a member of both the Administrator and
Project Manager groups. After I import a project from MSPP 2007 I go to the
Project Center in PWA to edit the project's properties to change the owner
but I only see others with administrator privileges in the list of possible
owners. Shouldn't I see all in the Project Manager group? I have tried to
add the to-be PM to the Administrator's group temporarily but them I get a
save error.

Suggestions please!

 

[Dale Howard [MVP]]

FrankC --

The behavior you see with the Owner field is a known and reported but in
pre-SP1 Project Server 2007. The bug is that the Owner list does not
display the list of members of the Project Managers group. Here's a
workaround I discovered that will solve this problem:

1. Log into PWA with administrator permissions.
2. Click the Server Settings link in the Quick Launch menu.
3. Click the Manage Groups link in the Security section of the page.
4. Click the Project Managers group to edit the Group.
5. In the Categories section, select the My Organization category.
6. In the Permissions grid for the Categories section, set the "Save
Project to Project Server" permission to Allow:
7. Click the Save button.

Don't ask me WHY that works or HOW I discovered it, but it should solve your
problem temporarily until Microsoft fixes it permanently. Hope this helps.

 

[FrankC]

Amazing! Works. I would never have found this on my own. thank you very
much.

 

[Dale Howard [MVP]]

FrankC --

You are more than welcome, my friend!

 

[Mike]

FrankC --

You are more than welcome, my friend!









- Show quoted text -

There is a catch. If PM's have open permission in the My Org category
(to give them read access to all plans) this additional permission
might be a problem.

regards

Mike

 

[Dale Howard [MVP]]

Mike --

Yea, so what's the workaround?

There is a catch. If PM's have open permission in the My Org category
(to give them read access to all plans) this additional permission
might be a problem.

regards

Mike

 

[Mike]

Mike --

Yea, so what's the workaround?









- Show quoted text -

Dale

Sorry for the delayed response. A solution I follow depends on
following a process. Create a "Change of Owner" group which has no
global permissions set and just this one permission set against My
organisation category. When you need to chnage owner, add the proposed
owner to this group, make the change then remove from group. Bit
kludgy but limits pemissions to minimum.

regards

Mike

 

[Dale Howard [MVP]]

Mike --

Thanks for sharing an alternate solution. I do appreciate it. Microsoft's
bug on the project Owner list is really a pain, isn't it?

 

[Scott Morrissey]

Dale,
I tried your solution to get all Project Managers to populate in
the Project "Owner" field in PWA - but it does not work for me. I am on a
post SP1 version called the "Infrastructure Release" which I think is the
most recent?

I need to be able to change the project owner on projects - it happens quite
frequently.

thanks.

 

[Dale Howard [MVP]]

Scott --

I believe that Microsoft has fixed this bug in one of the Cumulative
Updates. If you are only using the Infrastructure Update, there have been
numerous Cumulative Updates released by Microsoft since then. I think it's
time for your organization to "catch up" on Cumulative Updates, don't you?
Hope this helps.

 

[Scott Morrissey]

Dale - can you point me in the right direction to find these Cumulative
updates? the latest upgrade I see on the MS site is for the Infrastructure
Release.

Thank you.

 

[Dale Howard [MVP]]

Scott --

Refer to the following blog post from Brian Smith at Microsoft, as it will
give you the “skinny†on why you need to install the February CUs:

http://blogs.msdn.com/brismith/arch...2007-cumulative-update-for-february-2009.aspx

In Brian’s blog post, he references the correct KB numbers for each of the
three Cumulative Updates, which are:

Windows SharePoint Services 3.0
http://support.microsoft.com/kb/961755

Project Server 2007
http://support.microsoft.com/kb/968271

Microsoft Project 2007
http://support.microsoft.com/kb/966308

The updates need to be installed in the order shown above, which is WSS
first, then Project Server 2007, and then Project Professional 2007. Hope
this helps.

 

[Scott Morrissey]

Thanks, Dale. I did not see the Project Owner issue mentioned in the kb
article. Is it a known fact that this Cumulative update fixes the Owner issue?

Thanks again ..

 

[Dale Howard [MVP]]

Scott --

I know that the issue is fixed, but I cannot tell you exactly where. On the
other hand, what I don't know is if some Group/Category settings are
actually the source of your problem. Are you the Project Server
administrator, for example? And if so, have you changed any of the default
Group/Category permissions in Project Server 2007? If so, what have you
changed? If you are the Project Server administrator, are you only a member
of the Administrator group? If not, remove yourself from any other Groups
and see if that resolves the problem. Let us know.

 

[Scott Morrissey]

Dale - I am the administrator and am only on the Administrator group. All
other Project Managers are on a group called "Project Manager" and have
rights to save to the server. I thought that would populate the Owner
drop-down list box.

There was nothing in the default group - so I tried to add a few PM's there
- but it still did not work. Any other ideas to get that drop-down list box
populated?

 

[Dale Howard [MVP]]

Scott --

So, are you using the default permissions in Groups and Categories or not?
I couldn't really tell from your latest message. When you said, "There was
nothing in the default group...", that led me to believe you are using
custom Groups and/or Categories, or have changed default permissions. Let
us know.

 

[Scott Morrissey]

Dale - we are using Custom Groups and Categories to define rights for our
Project Managers.

 

[Dale Howard [MVP]]

Scott --

Since you are using custom Groups and Categories, it makes it much harder to
troubleshoot the source of your problem. However, if memory serves me
correctly, I think the New Project permission in the Global Permissions grid
is what populates a project manager's name on the potential list of Owners.
Obviously, this permission also allows PMs to create new projects. Have you
confirmed that your PMs have the New Project permission? Let us know what
you find.