Project Server 2010 Rename Project Site

I have a requirement, that is to change Projects' Names, it has to be done automatically (By code using PSI).
I used Project.QueueRenameProject and its working fine, however the associated project site/workspace is not renamed (updated).
I need suggestions about how can I rename the Project Site Programmatically (by code)?
I want the URL to use the new name.
I am thinking of two ideas, but I don't know the feasibility.
Idea 1, create a new site with the new name, copy the contents of the old site, and disassociate the old site, associate the new site, and delete the old one.
Idea 2, is to create a sharepoint/pwa event handler that triggers on Project Rename and execute what is mentioned in Idea 1.

Hi Mohammed,
What about using this method:
http://msdn.microsoft.com/en-us/library/gg178089(v=office.14).aspx
Paul
Paul Mather | Twitter |
http://pwmather.wordpress.com | CPS

Similar Messages

DAG in exchange server 2010 across different sites

hello ;
I want to know the best way to implement DAG for exchange server 2010 across 2 sites in the same domain ,
I have 2 exchanger server in one site in DAG ,with 300 gb database size
but I want to implement exchange server 2010 in a new site within the same domain and this will be my 3rd exchange server and will be a member on my existing DAG in the head office
the new site is linked to my head office using ipvpn connection which is 6 mb , and ADC is there in the new site,
what is the best way to implement the new exchange server in the new site to join the existing DAG .
is there is any problem related to DAG in this scenario ?
what is the best way to implement this scenario ?
Thanks

Hi,
For each AD site, it is recommended to have at least there Exchange roles: CAS, HUB, and MBX roles.
Do you plan to have active users in this new site?
If there are active users in this new site, you can deploy a Three-Member DAG in two AD sites. However, it is recommended to deploy two DAGs in two AD sites and you should have at least two DAG members each AD site. This scenario, two witness servers in
separate site is necessary.
If the new site is only for DR purpose, you can install this new Exchange server and add it to DAG. After that, add database copy to this new server.
Besides that, here are two articles which may help you for your reference.
Database Availability Group Design Examples
http://technet.microsoft.com/en-us/library/dd979781(v=exchg.141).aspx
Understanding Database Availability Groups
http://technet.microsoft.com/en-us/library/dd979799(v=exchg.141).aspx
Hope this helps.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Exchange Server 2010 SP1 DR Site Setup

I will need to setup a new CAS/MBX server in a DR site. WAN link can max to about 2MB/s speeds
Main site: 2CAS / 2MBX servers in Load Balanced CAS and MBX1 and MBX2 in DAG of 4 databases
DR Site: 1CAS / 1MBX but I will place this MBX server in Stretched DAG and have passive copies
DR SITE: I would create the 4 databases on the MBX server, but seeding will take 5 days since I have over 800GB for all 4 databases
If I have backups of my databases in the DR SITE from main site, can I copy them(EDB) and logs and then mount them? Then add them to main DAG group? or the only way it can be done is to set up new CAS/MBX servers on same LAN as main servers,
let them sync and travel the servers to DR site?
Also, is my WAN link poor in speed for this DR scenario?

Hi Sectorzero,
FYI Exchange2010 SP1 and SP2 is out of support. Please upgrade to SP3.
You can manually seed the database by copying the complete to the exact location in the destination server. Steps below
1.Run the below command on the current server to get the details
Get-MailboxDatabase | fl name, edbFilePath, logFilePrefix, logFolderPath
2. Dismount the database and copy the database folder and logs folder to the server in DR and to thee same directory of server in primary site.
3. Mount the database.
4. Add the databases using the below command
Add-MailboxDatabaseCopy -Identity <DBNAME> -MailboxServer <DRSERVER> –SeedingPostponed
5.Check the content index state using the command below
Get-MailboxDatabaseCopyStatus | fl name, contentindexstate, status
6. Resume/update the database copy.
Here is the reference
Resume-MailboxDatabaseCopy “DBName\DRServer“
7.If status failed you have to update by the below command and make both contentindexstate and status healthy
Update-MailboxDatabaseCopy DBNAME\DRSERVER –databaseonly
Update-MailboxDatabaseCopy DBNAME\DRSERVER –CatalogOnly
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Project Server 2010 Migratet from one farm to another farm

Hi ,
I need to migrate existing Project server 2010 farm one server to another server.
Kindly suggest me what is the best way we need to fallow.
Existing Environment two server:
1. App server(SharePoint 2010 +Project Server 2010)- Existing PWA site is running
2.Database server(with DNS instance name)
New Environment:
1.App server (fresh installed SharePoint + project server 2010)
2.DB server fresh server with sql 2008
Hasan Jamal Siddiqui(MCTS,MCPD,ITIL@V3),Sharepoint and EPM Consultant,TCS
|
| Twitter

Event viewer Error:
Failed to provision site PWA with error: Microsoft.Office.Project.Server.Administration.ProvisionException: Membership synchronization failed. ---> System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
at Microsoft.SharePoint.Library.SPRequest.RemoveRoleDef(String bstrUrl, Int32 lRoleID)
at Microsoft.SharePoint.SPRoleDefinitionCollection.Delete(SPRoleDefinition roleDefinition)
at Microsoft.Office.Project.Server.BusinessLayer.SharePointSecurityHelper.DeleteRoleByName(SPWeb web, String roleName)
at Microsoft.Office.Project.Server.BusinessLayer.SharePointSecurityHelper.DeleteRoles(SPWeb web)
at Microsoft.Office.Project.Server.BusinessLayer.SharePointSecurityHelper.ConfigureDefaultPWAWSSSecurityModel(SPSite topSite, SPWeb web)
at Microsoft.Office.Project.Server.BusinessLayer.Admin.<>c__DisplayClass18.<QueueUpdateUsersAddRemoveStatusOnPwaRootsAndWorkspaces>b__17()
at Microsoft.SharePoint.SPSecurity.<>c__DisplayClass4.<RunWithElevatedPrivileges>b__2()
at Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated secureCode)
at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(WaitCallback secureCode, Object param)
at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(CodeToRunElevated secureCode)
at Microsoft.Office.Project.Server.BusinessLayer.Admin.QueueUpdateUsersAddRemoveStatusOnPwaRootsAndWorkspaces(Dictionary`2 deletedUserUidsLoginNames, Guid[] addedUserUids, Boolean isFullSync, Boolean syncWorkspaces)
at Microsoft.Office.Project.Server.BusinessLayer.Admin.SynchronizeMembershipForPwaAppRootSite()
at Microsoft.Office.Project.Server.Administration.PsiServiceApplication.SynchronizePwaMembership(ProjectProvisionSettings provset, ProjectSite projectSite)
--- End of inner exception stack trace ---
at Microsoft.Office.Project.Server.Administration.PsiServiceApplication.SynchronizePwaMembership(ProjectProvisionSettings provset, ProjectSite projectSite)
at Microsoft.Office.Project.Server.Administration.PsiServiceApplication.CreateSite(ProjectProvisionSettings provset
Hasan Jamal Siddiqui(MCTS,MCPD,ITIL@V3),Sharepoint and EPM Consultant,TCS
|
| Twitter

Project Server 2010 Migration

Hi
Just for my information, I wanted to know, if any one can provide me (best) procedures to follow regarding PWA 2010 instances migration from test server to new server with workspaces as well.
I am preparing for a (major) migration. So please, if you can give me links on web or to some posts by EPM leadears, it will be very helpful for me.
Thanks.
Manish

Hi Manish,
The Project Detail Pages (PDPs) are stored in the Content DB. Did you restored the content database too?
http://blogs.technet.com/b/epmcontent/archive/2010/06/10/restoring-or-migrating-project-web-app-2010-instances.aspx
If you have restored the content database but getting the error, Here is the code which might help you.
http://blogs.msdn.com/b/brismith/archive/2010/05/18/project-server-2010-my-pwa-site-thinks-it-is-a-workspace-site-revisited.aspx
Web properties may be pointing to old URL, so read the Web properties to get the PWA URL & verify
using (SPSite site = new SPSite("hhtp://servername/pwa"))
using (SPWeb web = site.OpenWeb())
String sPWAURL = web.AllProperties["PWAURL"].ToString();
String sMsPWAPROJUID = web.AllProperties["MSPWAPROJUID"].ToString();
Once you know that migrated instance is pointing to the source PWA url, you can update using the console application:
using (SPSite site = new SPSite("http://servername/pwa”))
using (SPWeb web = site.OpenWeb())
web.AllProperties["PWAURL"]="";
web.AllProperties["MSPWAPROJUID"]="";
web.Update();
To fix it from powershell:
http://blogs.msdn.com/b/brismith/archive/2010/05/07/project-server-2010-my-first-fix-with-powershell-a-pwa-site-that-thought-it-was-also-a-workspace.aspx
Hope that helps.
Thanks, Amit Khare |EPM Consultant| Blog: http://amitkhare82.blogspot.com http://www.linkedin.com/in/amitkhare82

Multiple content databases and Project Sites

Hi,
I am in the process of migrating our Project 2007 PWA + Project Workspaces data to Project 2010. Our PWA site and the Project Workspaces are in a single content DB (2007) and I am trying to work out what I should do when I migrate it. Our content
DB is about 150GB which I believe is around the maximum that it should be.
I am unsure about a couple of things.
1. In SharePoint, you can assign multiple content DBs to a single web application, but each Site Collection will only live in a single content DB. Given that all of the Project Sites are actually just sub-sites of a single Site Collection I cannot see
a way to ever split them up into multiple content DBs. Am I missing something?
2. There is another post in this forum talking about whether to split PWA and Project Sites into different content DBs (and therefore Site Collections) with Project 2010 or not. Even though I have read it I am still unclear as to whether or not I should
do this and what the actual pros and cons are.
Thanks in advance for the replies.
Cheers,
David

All,
The requester wants more than 1 Site Collection for Project Sites and he wants more than 1 content database for each site collection. Neither of which apparently SharePoint can do. However,
for large numbers of Projects and associated Project Sites this will almost certainly be a necessity.
The Suggestion was that the PWA site collection and Project Sites site collection could be different and hence on different databases (even web apps). Fine. But not helpful, really, since that
only gets us to two site collections. One very small and one that will potentially grow very large, too large.
What appears to also have been suggested was to create a separate site collection for very large project sites.
While this approach could work, it is administration intense and is bound to have issues related to PWA navigation, etc...and certainly not part of the Project Server 2010 PWA automatic Site
Creation methodology. It also is after the fact and not really scalable. it would be possibe, but tricky to do this after the fact - moving it from one site collection to another - and then reset the URL in PWA Server Settings,
could be done.
I would suggest something similar, but a bit more pragmatic...Thanks Bruce!
Create 1 new Site Collection for Project Sites (same web app) in a new content DB - use script.
Setup PWA to provision all new Project Sites to that new site collection. Maintains automatic site provisioning.
Monitor
the size of the DB, when it reaches a reasonable limit (? 50GB ?) - repeat this process, create another site collection in a new DB - but
change the PWA provisioning settings to have all new sites go to the new (next) site collection. Existing sites will still be found (keep the site collections in the same web app for continuity) and can have content added (I guess up
to a point - monitor). Repeat as needed.
Another way I can conceive of is to create a fixed set of a small number of site collections (in the same web app) and manage the Project Site creation manually selecting which
project site goes against which site collection. Division along some logical boundary such as Departments makes sense. But other divisions may be used. This could scale by simply adding more site collections at each department (HR-2), should any given department's
DB grow too big. Then all the logically related Project Sites will hang off the site collection selected and be part of that database for that site collection for that "department" let's say.
just a variation of the above solution. Monitoring the DB size is key in both cases.
There may of course be caveats to any approach other than OOTB and all in 1 site collection, around navigation, web parts, solution starters, etc...some of which are addressed elsewhere. Of
course, this is admin intensive but retains automatic provisioning for new sites. I believe it would work and meet the requirements for smaller DB's and multiple Site collections for PWA Project Sites and scale to thousands of project sites.
Thanks,
Eric S.
Eric S.

Project Server 2010: PWA Removing Default Project Site Security Groups When Creating a New Project

I looked for this specific issue with Project Server 2010/PWA/SharePoint and could not find an exact answer... hopefully someone can help.
We are currently using Project Server 2010 and have a number of project site templates that are used dependent upon the enterprise project type selected. Each of these project site templates have unique permissions which should create the default security
groups on the project site upon publishing/syncing:
<Project Name> Members
<Project Name> Owners
<Project Name> Visitors
<Project Name> Project Managers (Project Web App Synchronized)
<Project Name> Team Members (Project Web App Synchronized)
Web Administrators (Project Web App Synchronized)
Whether a user creates a project through PWA or Project Pro 2010 and imports the project into PWA, we get a weird result in the Site Permissions of the newly created project site. PWA will remove all default security groups from the project site template
and add a whole list of users in the Site Permissions list without groups.
Once the project is published and the project site is created, we can then go back and add those default security groups back in the project Site Permissions and even add a couple of custom groups without them being removed on all subsequent project syncs
or publishing.
How do we get PWA to not overwrite the project site templates' security groups and place each user in the proper default security groups? At the same time, how is PWA adding a number of users into the Project Site Permissions?
Thanks in advance.

Paul,
Thanks for that information. Right now we are using the Test environment to turn the Auto-sync feature back on. I suspect that the reason this is happening is due to PWA groups/categories/security templates. There may be more than one PWA group that is "overwriting"
the default project site groups upon initial creation of the project. We will look further into the security settings to tighten up the policies.

Project Server 2010 / Sharepoint 2010 Permissions not syncing to Project Site

Project Permissions not syncing to Project Site
Project Manager Group
New project is created and published project server sends permissions to Sharepoint which puts users into the following groups:
<dir><dir></dir></dir><dir><dir>
Web Administrator (Microsoft Project Server)
Project Managers (Microsoft Project Server)
Team members (Microsoft Project Server)
Readers (Microsoft Project Server)
At this time the creator/owner, owner’s management, portfolio managers, and executives should all have Project Manager rights on the sharepoint site, and Admins will have Web Admin permissions.
Issue #1: Only the Web Admin permissions and creator/owner permissions are being added to the Sharepoint permission groups
Workaround #1: Going into the project site permissions and adding the
Project Managers (Microsoft Project Server) group manually and the sync will keep the permissions
Workaround #2: Going into the Server Settings, Manager Groups then removing or add all users to the No Permission Group, which forces an sync to all workspaces. Con: This workaround can only be down at night when users are not active since it will
block the queue for at least an hour.
Project Owner Transfer
Previously created project has owner change, once saved and published project server sends permissions to update user’s permission to
Project Managers (Microsoft Project Server) on Sharepoint project site.
Issue #2: When Project owner is changed and project is published the owner is not getting permissions to the Sharepoint project site. However, if owner is also added to the team using the Build Team Feature the sync will give the owner Project
Manager permissions on the Project Site.
Workaround #1: Going into Server Settings, Project Sites, select project and Synchronize. Once this is done, the owner will have Project Manager Permissions without being added to the team.
Users who have been added to this project in Project Server 2010, but not assigned to tasks. Users who have assignments in this project in Project Server 2010 and are contributors to the project workspace site,
meaning that they can create and edit documents, issues, and risks. Users who have published this project or who have
Save Project permission in Project Web App and are contributors to the project workspace site, meaning that they can create and edit documents, issues, and risks. Users who have
Manage SharePoint Foundation permission in Project Web App and are contributors to the project workspace site, meaning that they can create and edit documents, issues, and risks.</dir></dir>

By default when you create project build team add users in the task and publish the project plan then All the User which are available in the project plan including Project owner will go to below mentioned group in project site:
1. creator/owner, owner’s management, portfolio managers, and executives should all have Project Manager will get access to Project Managers (Microsoft Project Server)
2. User who are having team member access to PWA will get Team members (Microsoft Project Server) access if they are assigned to the project task.
3. User who are having team member access to PWA will get Readers (Microsoft Project Server) access if they are not assigned to the project task.
4. Only PWA Administrator will get the access to Web Administrator (Microsoft Project Server)
Sharepoint permission you have to use when you want to give permission manually to users on project site
In the Project Site provisioning setting under Server setting if you have Check to automatically synchronize Project Web App users with Project Sites when they are created, when project managers publish projects, and when user permissions change in Project
Server.
Then all the user get access as per describe above and if you will give access manually to any of the user either in project server group or in Sharepoint group once you will publish the project next time all the manually given permission will go away.
IF you want to give permission to user manually to sharepoint group or project server group then uncheck automatically synchronize Project Web App users with Project Sites when they are created, when project managers publish projects, and when user permissions
change in Project Server.
You check PWA site setting --> Site permission then member of Sharepoint group user who will have access to sharepoint group in PWA site setting site permission will have access to all the project site sharepoint group as Project site inherit permission
from PWA root site.
Both the issue which you have described is behavior of project site.
For issue 2 when first time project owner create and publish the project and projectsite is getting created then porject owner name gets access in the porject manager (project server group) nect time if you will change the owner and publish the project
until he will not present in the project plan will not get the permission.
If you want to give sharepoint permission to users then uncheck automatically synchronize Project Web App users with Project Sites when they are created, when project managers publish projects, and when user permissions change in Project Server and give
the permission manually.
Project site in 2010 has some issue and not full filling customer need some time ,Ms has came up with 2013 which is having tight integration with project sites .
Project workspace security groups are equal to the SharePoint Server 2010 security groups.
Web Administrator equals Full Control
Project Managers equals Design
Team members equals Contribute
Readers equals Read
Users who have Manage
SharePoint Foundation permission in Project Web App and are contributors to the project workspace site, meaning that they can
create and edit documents, issues, and risks will get access to Web Administrator (Microsoft Project Server)
http://technet.microsoft.com/en-us/library/cc197668(v=office.14).aspx
kirtesh

MS Project 2010 Server - How to move a single MS Project plan and SharePoint Project site from a PWA server to another PWA server (one at a time)

MS Project 2010 Server
How to move a single MS Project plan and it's SharePoint project site from a PWA server to another PWA server (one at a time)
I have 2 Project PWA servers, i know how to copy all the databases (Publishing, Draft, Reporting, archive, content) from one SQL server and copy it to the other PWA server so both server can be identical.
I need to only move a single project from a PWA server to another,
Moving the Project plan, actual time data, SharePoint site with all it's content
Is there a 3rd party tool that can be added on to the server to help me move single project plans? to different PWA servers?
-Isaack

Visit my friends at FluentPro and try FluentBooks
http://www.fluentpro.com/productsfluentbooks2013.html
they have a 2010 version also.
Hope that helps,
Thanks, Eric S. Pcubed

Need solution to make changes in existing project sites in Project Server 2010 environment

Dear Folks,
Hope you all are doing good and ready to give a way for this requirement. :)
In project server 2010 environment, I am using InfoPath documents library, Issues, Risks etc in each and every project sites.
Say, after creation of 100 projects/project sites, I have got a requirement to make some changes in the InfoPath document library and in Issues, Risks list, so I have decided to use the following solution which is actually weird:
Make the changes in InfoPath document library, Issues/Risks list for 1 of the project site and save that site as template and associate it with running EPT.
Then, delete the existing project sites (after taking backup) and start recreating it from PWA/Server Settings/ Operational Policies/ Project Sites, so that it will take the latest template. But, seems like it is time taking and handy and actually it's not
working for some of the projects.
Request all of you to provide some solution for this.
Ask more, if my explanation is not clear.
Regards,
Shravan

Hello,
Regarding mass deleting and recreating Project Sites via the PSI, firstly delete the project sites then run the following PowerShell script to bulk create project sites:
https://gallery.technet.microsoft.com/Bulk-create-Server-Sites-784f7b29
I have got a script that bulk deletes projects but this is not published as this could be a dangerous script to run if you did know what to update etc. To give you an idea of how to delete project sites via the PSI see a code snippet below:
$EPMTYGUID = [system.guid]::empty
$projectOwnerID = 'd6a0a720-12ac-e211-93f9-00155d153dd4'
$ProjectList = $svcPSProxy.ReadProjectStatus("$EPMTYGUID","PublishedStore","", "0").Project | format-table proj_uid -hidetableheaders | out-string -stream
foreach ($projectUid in $projectList)
if ($projectUid -ne "")
$projectsforDeletions = $svcPSProxy.ReadProject($projectUid, "PublishedStore").Project | where {$_.projectOwnerID -eq $projectOwnerID} | format-table proj_uid -hidetableheaders | out-string -stream
foreach ($projUid in $projectsforDeletions)
if ($projUid -ne "")
$svcWSSProxy.DeleteWSSSite($projUid)
Write-host 'Project UID for deleted site' $projUID
That particular example deletes the project sites for a particular project owner, you could easily modify that to remove the project owner filter if needed.
Regarding your query about having to delete the project sites to get the changes to take affect, there is no easy option to get the issues and risks list changes to filter though, this would either be manual on each existing site or using code to iterate
through each existing site and apply the changes programmatically. Depending on if you used site collection content types to set up the Issues and Risks lists, it might be simple to add a new column etc. as you could do this centrally and it will cascade
down. If you didn't use content types and or its view changes etc. this is a per site change that can be manual or programmatically done. The same applies to the document library, if this was set up using a site collection content type, the changes can
be modified on the content type and cascaded down. If the library was set up with just a library that used local columns / templates then it will be a per site change - the same as the issues and risks.
The company I work for (CPS) does have a site sync tool that will programmatically update existing sites based on a specified site so I know it is all possible to do in code!
Paul
Paul Mather | Twitter |
http://pwmather.wordpress.com | CPS |
MVP

Bulk Project Site option isn't working in project server 2010 migrated from PS 2007.

Hi,
I am doing a test migration from epm 2007 to epm 2013.
So first, i need to migrate the project server 2007 to project server 2010. i have 2 separate environments for EPM 2007 and EPM 2010).
there is no problem in migration process and i successfully migrate entire PWA 2007 to 2010, except Workspaces (Project sites).
Bulk project site option is not helping. I have tried 4-5 times with different PWA 2007 databases (PWA1, PWA2...) but this option did not work. and errors in queue are WSSWebDoesNotExist(16405) and GeneralQueueJobFailed(26000).
Then next time while migrating all over again i kept the same port and same PWA name then bulk project site option worked.
Question is, Do i need to keep the same PWA name and same port for the new upgraded PWA??, one more issue regarding this is that if don't keep the same PWA name and i open the project site and click on the "Project web app" back link, it
redirects me to old PWA site which doesn't exist and give me page not found error (Obviously).
Below, you can see the both scenarios.
my previous PWA 2007 site, say - http://epm2007:2222/PWA
When - migrated PWA 2010 site, say - http://epm2010:3000/NewPWA (Bulk project site update just doesn't work)
When - migrated PWA 2010 site, say - http://epm2010:2222/PWA (Bulk project site update worked)
Whats the solution of this problem. is there any utility or query to link all project sites correctly?
Will i face the same problem while migrating PS 2010 to PS 2013??
Thank you.
sandeep

Hi,
I would say it is easier to keep the same PWA name between 2007 and 2010 (no need to have the same port).
If you want to move to a new PWA URL maybe you can use stsadm backup/restore as detailed in this article?
http://technet.microsoft.com/en-gb/library/ee662500(v=office.14).aspx
Hope this helps
Paul

Where can I find the web site ID of a project site in Project Server 2010?

Hi, I need to find the ID of the project site of a project in Project Server 2010 in order to be able to identify that web site in the Sharepoint Content DB (in the reporting DB, in Projects_View appears the URL of the project site but not its web
site ID). I need to list the documents stored in the project sites of the projects contained in the Project Center inside PWA.
Thank you very much
Regards
Carlos Negroni

Hi Mahesh:
Thanks but what I need is to link that ID with the related project in Project Server databases. Anyway I think I'll use the FullURL information to join the tables because that information appears in the Reporting Database of Project Server (although maybe
it is not the best alternative).
Regards

Add Bulk Users to Project Server 2010 site using a Script

I have 100 users that I need to add to a Project Server 2010 site. Add these through server settings would take a week to do. Is there a way to add users in bulk like with a script or something that can pull from an CSV
Thank you for your help!

Hi,
I am not sure if I got your question?
If you want to add these users to a site of a specific project, just add them as team members to this project. This will provide read access to them. If you assign them to a task within this project, they will alos get write access in this site.
If you want to add this users as Project Server resources and users and just have a list of them, you can use copy/paste. Go to Resource Center and click on Open. Project client will start with checked out Enterprise Resources. Add columns Windows User Account,
Email Address, and all other fields you want to fill. Make sure that the columns and the sequence of columns does match the columns in your file. Use copy/paste to insert all users into Project. Save and Close. Use Option Bulk Edit, if you want to define
eg Timesheet Manager. As a last step go to Server Settings - Manage Groups and add them to the appropriate groups.
Does this answer your question?
Barbara

I want to break inheritence and create unique permissions in a Project Server 2010 project site list/library.

Some Project Managers want to restrict permissions on certain lists or libraries in their Project Server 2010 project site. However, when I have done this for them, by breaking inheritence to the parent site and then removing/adding users with unique
sharepoint permissions, it seems that when the project schedule is published, some of the newly created permissions are lost.
I have tried creating a SharePoint group at the project site level and then applied it with specific permissions (eg. Contribute) to the list/library and this seems to work better but I haven't been able to confirm yet if this will work in the
longer term.
Does anyone know what is the best method to break inheritence and set up unique permissions on a list in a Project Server 2010 project site that will not be lost when the project schedule is published?
Thanks
Peter

Thanks Lynda
I am aware that I can disengage the entire permissions sychronisation using that setting but that is not what I want to do. I just want to be able to break the inherited permissions on individual document libraries or lists on specific Project Sites
so that I can restrict access to nominated people.
My issue is that when I do this, I find that some of the amended permissions disappear from time to time. It seems to be related to when the schedule is published. They
don't revert to the inherited permissions, just some of the people who I have given direct access to no longer have access.
Im just trying to find out the best way to manage setting non-automated permissions on a single list or library in a Project Server project sites so the changes stick.
Peter

Project Server 2010 permissions granted through RBS are not flowing through to Project Sites.

Hi,
I have configured RBS as "The Project Owner is a descendant of the user via RBS" its working fine for Projects.
But users are facing access denied issue when working with project sites RBS is not working for project sites.
Can any one Help me How can i grant permissions Automatically for project sites also as same like projects is it possible ?
The Members in Executives group can see all projects in organization but same like can they see all project sites ?
I have found one blog of
RaymondRis he is recommending to do it manually as its not possible to grant Project site permissions Automatically.
http://blogs.technet.com/b/raymond_ris/archive/2013/05/09/project-server-2010-permissions-granted-through-rbs-are-not-flowing-through-to-project-sites.aspx
Thank You, Kumar KSV

Kumar,
The permissions to project sites is not cotrolled by the RBS, as you have discovered. It is controlled by the Security Category permisisons, and the settings if the permssions are auto synced. The permissions work like this:
Project managers who have published a project or who have Save Project permissions on a project are added to the Project Managers (Microsoft Project Server) site group.
Team members with assignments in a project are added to the Team members (Microsoft Project Server) site group.
Other Project Server users who have View Project Site permission on a project are added to the Readers (Microsoft Project Server) site group.
As long as you use the Auto Sync of permisisons for project sites, i do not think there is any work around.
Cheers,
Prasanna Adavi, Project MVP
Blog:
Podcast:
Twitter:
LinkedIn:

Project Server 2010 Rename Project Site

Similar Messages

Maybe you are looking for