Project Site Permissions Being Overwritten

Hi there!
We're on Project Server 2010.
We've been having an ongoing struggle with custom Project Site permissions being overwritten from time to time. We've unchecked the auto sync for Project Site Permissions. I believe that's working well. I suspect where our troubles
come from are the PSI. Calling QueuePublish through the PSI is the only way I've been able to replicate the issue. However, we've been unable to find out what is making this call. For example, Our tier 1 support person will
see all is well with a Project Site's custom permissions late in the afternoon. But the next day the permissions will have been overwritten and it seems everyone in the Project Managers group and Web Administrators have been added back to the site.
I can even see in the ULS logs where it appears the Publish occured, but unable to identify what called it.
I also attempted the steps in this article ( http://technet.microsoft.com/en-us/library/hh670402(v=office.14).aspx ) to disable synchronization for Project Sites (DisablePWS = 2) with no success. Even when I use DisableAll (4) the user sync fires when
the QueuePublish is used through the PSI. This would be a great solution if I can get it to work.
Has anyone had success completely eliminating PWA to Project Site permission syncs? Either through identifying what jobs may trigger a full publish or by making the sync change detailed in the article I linked?
Thanks so much for your help!

Hi Raddius
There has been a similar discussion going on this thread, hope this answers your query
http://social.technet.microsoft.com/Forums/projectserver/ar-SA/ffdc437b-883b-4190-aa86-8f16452b1e09/i-want-to-break-inheritence-and-create-unique-permissions-in-a-project-server-2010-project-site?forum=projectserver2010general#706ac83d-83ba-4046-acab-4b279ff4d7ba
Thanks | Sunil Kr Singh | http://epmxperts.wordpress.com

Similar Messages

PS2010 - Project Site Provisioning Settings - Project Site Permissions

If the option is selected, are there any projects that will not have the permissions synced to the project site? I would like to not update the security on the 5000+ closed/completed project sites as this takes an excessive amount of SQL resources,
especially when the Team Members group has grown to more than 500 users.
I changed the Team Members category setting of 'View Project Sites' to unselected so changes to the group membership will not initiate a bulk project sync. This was bringing my server to its knees. Site sync now takes only a few seconds to reset
security for ~40 users (per site).
If Project Mangers membership changes, the auto-sync will initiate over 5000 jobs to have all users removed and readded back to each project site. Even at 90 seconds per site, this will take hours and block the queue. If I could instead have
it only sync against the Active or at least non-archived project the time would be reduced to less than an hour.

Hi Greg,
Project Server Sync will be for all the users if a ERP Sync or User Sync is invoked. However you can perform a Site Synchronization from Project Sites link in Server Settings.
Ideally, it would be best if you can take a backup of the closed or completed projects so that the backup is available in Archive DB. Once the backup is complete delete these projects from the Draft and Published DB's.
This should meet your requirements and also will have less number of projects in display whenever a user is trying to work on any of the projects.
Cheers! Happy troubleshooting !!! Dinesh S. Rai - MSFT Enterprise Project Management Please click Mark As Answer; if a post solves your problem or Vote As Helpful if a post has been useful to you. This can be beneficial to other community members reading
the thread.

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

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: 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 site security best practise - project server 2010

I have following requirement
environment:
project server 2010
project sites created out of project site templates. So they follow project server security model.
requirement:
the are users who do not needs to see any thing except the content on project site. The user does not need to access project \pwa
Question:
what is the best approach
create sharepoint based groups for the projectsite?
Create project server based group?

pgshah570,
If you are using the automatic synchronization for project site permissions, then the permissions are granted based on the following rules:
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.
If you are NOT using the automatic synchronization, then project sites are like any other SharePoint Sites, and you can use SharePoint groups or AD groups. I recommend using AD groups to grant permissions. The Project Server Security groups in this scenario
do not have any impact on Project Site permissions.
Cheers,
Prasanna Adavi, Project MVP
Blog:
Podcast:
Twitter:
LinkedIn:

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

I've noticed that many web sites have data areas that are being overwritten. But they display just fine with IE

Columns are being overwritten. Seems like a "table" command doesn't know where all the columns should be displayed. Don't know if the web sites are being written by Microsoft type software or what......:-(

Reset the page zoom on pages that cause problems: <b>View > Zoom > Reset</b> (Ctrl+0 (zero); Cmd+0 on Mac)
*http://kb.mozillazine.org/Zoom_text_of_web_pages
If you have increased the minimum font size then try the default setting "none" as a high value can cause.
*Tools > Options > Content : Fonts & Colors > Advanced > Minimum Font Size (none)
*Tools > Options > Content : Fonts & Colors > Advanced > [X] "Allow pages to choose their own fonts, instead of my selections above"
*http://kb.mozillazine.org/Website_colors_are_wrong
*http://kb.mozillazine.org/Websites_look_wrong

Project Site Contributor Rights for all Projects in PS 2010

Hi
We have a requirement where some users, need a group which gives them the rights to upload documents and create folders in the project sites.
Team Members, unless assigned to a task, can only read projects they belong too. But we need another group, which allows the people to see all projects, and put content into the project sites - nothing else as such.
Any ideas what permission to set? See Manage SharePoint Foundation, but that seems overkill like they can manage anything SP?

Tibsy,
Unfortunately, there is no easy way to do this as long as you are using the permission sync.
The closest you can get to this is by creating a new group, which gives users the "Save to Project Server" category permission on the "My Organization" category. This adds the users to the "project Managers for PWA" group on
all Project Sites, which gives the "contribute" rights to the site.
The downside to this is that  this permission level gets the users closer to the "Design" permission, than the "Contribuite"
permission, which means they can create new libraries, lists etc., in addition to uploading content.
As far as being able to "Save" all projects in My organization, that could be mitigated by not giving any other permissions like "open Project" or View Project Schedule" for that category.
So essentially, they cannot even see the project in the Project Center, if they are not supposed to see that.
This is the closest I have gotten to a workaround in this scenario.
Cheers,
Prasanna Adavi, Project MVP
Blog:
Podcast:
   Twitter:
LinkedIn:

Unable to Open Project Site Access Denied Issue Project 2013

This issue is happening to select projects and select project managers, they can view certain project sites but receive the error on other projects. After some extensive testing
it looks like if the PM is the owner of the project plan they are not getting added to any of the synced groups for the project site. I can change the project owner to any another PM and it processes correctly and adds them to the PM synced group on
the Project site. As soon as I make the original PM the Project plan owner again the previous PM gets removed from the PM synced group and added to the Team member synced group, the way its supposed to work. However the PM with the problem never
gets added to any group. I have to manually add them to the non-synced Owner group on the project site so they don't get removed from the synced PM group the next time the sync runs at midnight.
As I stated it is happening on select project plans and select PMs. I have tried replublishing the project plan via Project professional and the web and the results are the same.
If I create a new project plan and assign one of the PMs with the issue to the plan everything works correctly. We noticed the issue a few weeks ago; most of the plans with the issue are several months to a year old so they were working correctly until
recently. They had also made PM owner changes prior to the issue on most of those plans and everything worked correctly.
If anyone is experiencing this issue and has a fix please let me know. I am trying not to open an MS support ticket if possible.
Frank Miranda Florida Hospital MIS

I believe I've found the fix for this issue. After opening a ticket with MS support and not getting anywhere with this issue I decided to do an in-depth review of all the Project and SharePoint 2013 CU's starting with December 2013 to September 2014.
To my amazement buried inside the July 2014 CU was a hotfix for this issue described almost word for word. (I will list all the relevant KB's at the end) I contacted my support engineer inquiring about this hotfix and he stated it wasn't relevant because
the "Synchronize Project Web App permissions to Project Site" was not failing or even generating any warnings in our Prod or Test environments. I stated that is not always an indicator as ULS doesn't always catch all relevant errors.
I informed him that I also found a second hotfix pertaining to the same issue released August 2014, apparently the first hotfix in July didn't totally resolve the issue and a second hotfix was released. He was adamant that this would not resolve
our issue and he requested or production databases because he was unable to replicate the issue in his test environment. The reason, you may wonder, is because he was at a higher patch level that our farm.... Obviously! His farm had the most current
CU which included the hotfixes from July and August. Apparently he didn't see the flaw in his logic.
I decided to install the September CU on our test farm. Low and behold that fixed the problem, even though MS support stated the hotfix was not relevant to our issue. I learned a long time ago to take MS support comments as suggestions instead
of gospel truth, this isn't the first time they have confidently given me erroneous information.
We are currently doing further testing to verify that this CU didn't break something else. Unfortunately these rollups are not GA and Microsoft is very clear that you should only install them if the hotfixes pertain directly to your issue.
Finding the hotfixes was a chore as Microsoft loves to create multiple KB's for the same thing and then nest (bury) them so you have to dig through four or five KB's to find the relevant fix. I'll save you the trouble and list them below.
Watch the
September CU Webcast Brian Smith and team go into depth explaining why this issue has been happening and how they fixed it.
September 2014 CU http://support.microsoft.com/kb/2882990 (the one I installed)
August 2014 CU https://support.microsoft.com/kb/2989078
August Project site sync hotfix
https://support2.microsoft.com/kb/2883083
July 2014 CU http://support.microsoft.com/kb/2882990
July Project Site Sync hotfix http://support2.microsoft.com/kb/2882995
Microsoft Project Server Blog
http://blogs.technet.com/b/projectsupport/ (I find this to be more helpful than the TechNet site)
Frank Miranda Florida Hospital MIS

Unable to Open Project Site Access Denied Issue (Project Manager)

Hi
We got an issue that one project manager is having 12 projects, in that she can able to view 5 projects-- project sites but remaining 7 projects --- she is not able to open the project site (access denied) error is throwing when she try to open.
She is the project manager of the 12 projects and having project manager permissions on the project sites.
Please suggest any solution for this.
Geeth If you feel that the answer which i gave you is Helpful please select it as Answer/helpful.

I believe I've found the fix for this issue. After opening a ticket with MS support and not getting anywhere with this issue I decided to do an in-depth review of all the Project and SharePoint 2013 CU's starting with December 2013 to September 2014.
To my amazement buried inside the July 2014 CU was a hotfix for this issue described almost word for word. (I will list all the relevant KB's at the end) I contacted my support engineer inquiring about this hotfix and he stated it wasn't relevant because
the "Synchronize Project Web App permissions to Project Site" was not failing or even generating any warnings in our Prod or Test environments. I stated that is not always an indicator as ULS doesn't always catch all relevant errors.
I informed him that I also found a second hotfix pertaining to the same issue released August 2014, apparently the first hotfix in July didn't totally resolve the issue and a second hotfix was released. He was adamant that this would not resolve
our issue and he requested or production databases because he was unable to replicate the issue in his test environment. The reason, you may wonder, is because he was at a higher patch level that our farm.... Obviously! His farm had the most current
CU which included the hotfixes from July and August. Apparently he didn't see the flaw in his logic.
I decided to install the September CU on our test farm. Low and behold that fixed the problem, even though MS support stated the hotfix was not relevant to our issue. I learned a long time ago to take MS support comments as suggestions instead
of gospel truth, this isn't the first time they have confidently given me erroneous information.
We are currently doing further testing to verify that this CU didn't break something else. Unfortunately these rollups are not GA and Microsoft is very clear that you should only install them if the hotfixes pertain directly to your issue.
Finding the hotfixes was a chore as Microsoft loves to create multiple KB's for the same thing and then nest (bury) them so you have to dig through four or five KB's to find the relevant fix. I'll save you the trouble and list them below.
Watch the
September CU Webcast Brian Smith and team go into depth explaining why this issue has been happening and how they fixed it.
September 2014 CU http://support.microsoft.com/kb/2882990 (the one I installed)
August 2014 CU https://support.microsoft.com/kb/2989078
August Project site sync hotfix
https://support2.microsoft.com/kb/2883083
July 2014 CU http://support.microsoft.com/kb/2882990
July Project Site Sync hotfix http://support2.microsoft.com/kb/2882995
Microsoft Project Server Blog
http://blogs.technet.com/b/projectsupport/ (I find this to be more helpful than the TechNet site)
Frank Miranda Florida Hospital MIS

Adding a Second Project Site with same restore data

This is the first time I've had to accomplish this
I have a dev server where I restore a backup from 2 weeks ago to http://devserver/pwa
My team has asked for a restore from 2 weeks + 1 day to http://devserver:99/pwa - I've tried deleting site collections, tried several other ways of doing the restore; however, during the mount-spdatabase I get only 1 site to come back (pwa) but
it doesnt show in the site list
The enumallwebs shows the following (notice the in sitemap)
stsadm -o enumallwebs -databasename content_database
databse site count 1
<site ID = random characters > <owner = farmguy> <In sitemap = False>
Web count = 235
==============
I believe/know the issue deals with the same site ID being on the first pwa site; however when I try to do a Mount-SPContentDatabase content-database -WebApplication "http://dev:99" -AssignNewDatabaseID I still get the same issues - new database
ID but still same site ID for the "dev/pwa" site database
Is there anyway to clone (yes I've seen the other articles) or have two sites with the same data?
I've also thought about trying to export the stsadm enumallwebs data and copying that to a new PWA site but have been unsuccessful in the export (or even finding a way to do it)
Can I get any ideas on how to either
1) Change the site ID from a database backup/restore
2) Restore a PWA site to the same server/database server
3) other ideas?
My team members would like to do a comparison of the two dates between a project to check for differences (I just found out about
FluentPro Audit Lite Pro)
Any and all suggestions would be appreciated...
Thank you

I'm still experiencing issues
I tried the following (http://social.technet.microsoft.com/Forums/projectserver/en-US/edc6f56a-5850-4102-841b-32d4df6e6882/how-i-to-restore-the-project-site-deleted-on-project-server-2010-?forum=projectserver2010general) by recovering the data from an unattached
Database (I also did the site collection backup)
1) Trying to do an Import-SPWeb but this was unsuccessful
created a web application 99 -> provisioned a pwa with the old databases -> data appear in project center but when you click on the sites it gives an error message
created a web application 99 -> create a site collection -> provisioned a pwa with the old databases -> data appear in project center but when you click on the sites it gives an error message - same as above
the below while it held promise it didnt work for going against a separate port... using the data from an unattached content database export (link above)
also reference (http://pwmather.wordpress.com/2012/06/28/move-a-sharepoint-2010-sub-site-to-a-different-location-on-the-same-farm-sp2010-ps2010-powershell/)
2) Tried to do a SPSite Restore and it ends up deleting the provisioned PWA and still appears to be there but no PWA soo
3) removing the ophaned PWA site (http://mrhodes.net/2011/02/24/fixing-an-orphaned-site-collection-within-project-server-2010/) wont help since it will remove the PWA sites/subsites from the content database I want
4) I'm still unsure how to approach what Krishnp stated...
unless #2 was his approach
Any other help would be greatly appreciated - I'm trying everything it's time consuming since the backup files take over an hour to restore to a site - while it is faster to do the original when its just one content database/4 pwa databases...
I've read its possible to do to different ports (of course I closed the page) but I have only seen one post point it out
thanks again

Read Only Permission on project site (PS 2013)

In Project Server 2010, if someone could see all projects, and had the “View Project Site” permission (basically the Executives group), you would end up with only Read rights on a project site. You could view stuff, but not edit anything.
In Project Server 2013 we are having an issue with giving read only access to project sites. After comparing our customized groups/categories with the ‘out of the box’ Portfolio Viewers security permissions we have actually given our groups less permissions.
We want these users to be able to see all projects, but only have read only permissions on the project sites. That is not happening. The executives end up with contribute permissions similar to what a team member with assignments on a project
would get.
any feedback will be appreciated.
Thanks,
Ali Al . Consultant & Development Manager.

Hi Paul,
This issue was fixed in the November 2014 cumulative update for Project Server 2013:
Hotfix KB2899547 for Project Server 2013 November 11, 2014 (Projectserverwfe-x-none.msp; Projectservermui-<Language-Code>.msp)
http://support.microsoft.com/en-us/kb/2899547
The fix is also included in the cumulative update for Project Server 2013:
November 11, 2014 Cumulative Update for Project Server 2013 package
http://support.microsoft.com/en-us/kb/2889949
More recent updates will include this fix.
Brian Smith published a blog with additional information:
Project Server 2013: Project now controls the Visitors group on Project Sites
http://blogs.technet.com/b/projectsupport/archive/2015/02/03/project-server-2013-project-now-controls-the-visitors-group-on-project-sites.aspx
Thank you,
Suzanne
Microsoft Corp.
Suzanne Sylliaasen [MSFT]

Files being overwritten

I just upgraded to Dreamweaver CS3 from MX 2004. I have the
following enabled for my site definition: Maintain synchronization
information; Enable file check in and check out; and Check out
files when opening. The problem is, every time I open a file
locally, it automatically and instantaneously gets overwritten by
the remote file. This did not happen with MX 2004, and this has
caused many problems for me. Is this supposed to be happening, or
do I have a problem here? I've tried disabling Maintain
synchronization information, but this doesn't change anything. Any
and all help is greatly appreciated.

> Isn't that the point of the
> synchronization feature - to alert you when your files
are not synched and
> then
> let you choose what you want to do?
If you are using checkin/checkout, the remote site is the
gold standard for
all checked-in files. Thus, overwriting your local copy is of
no
consequence, since you cannot have made changes to the file
after it has
been checked in. It would be unnecessary for DW to ask if you
want to
overwrite it, because DW assumes that you know it will be
overwritten by
virtue of the fact that you have just initiated a checkout
operation. Get
it?
> If a co-worker checks
> out a file, makes a change to it and checks it back in.
I can then check
> out
> that file and make changes of my own and check it back
in, right? Am I
> misunderstanding you on that?
Your understanding as expressed in the first two sentences is
absolutely
correct.
If your co-worker checks out a file, you cannot check it out
until it's
properly checked in by your co-worker. Once the file is
checked in, you can
then check it out.
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
==================
"akirell" <[email protected]> wrote in
message
news:[email protected]...
> If the automatic overwriting of files upon opening has
always been, I
> never
> noticed it. I have always had file check in/check out
enabled, yet never
> experienced my files being overwritten until CS3. The
specific problem
> with the
> file being automatically overwritten is simply the fact
that I feel I
> should be
> asked first if I want to overwrite the file. Isn't that
the point of the
> synchronization feature - to alert you when your files
are not synched and
> then
> let you choose what you want to do?
>
> Also, you said if a file is properly checked in, then I
will not be able
> to
> make any local changes. That doesn't make sense to me.
If a co-worker
> checks
> out a file, makes a change to it and checks it back in.
I can then check
> out
> that file and make changes of my own and check it back
in, right? Am I
> misunderstanding you on that?
>

SendAs being overwritten on all mailboxes

We have had persistent problems getting SendAs to work; we set it up in EMC on a mailbox (delete old SendAs, add a few new ones), all seems OK, then an hour later the SendAs has been overwritten by the old SendAs setting. I've checked and all the mailboxes
have the same SendAs accounts attached: one domain user (non-admin) and a UUID presumably from a deleted account.
Any ideas?

Hi,
Please refer to the following article:
http://3cvguy.com/active-directorys-sdprop-process-vs-exchange-send-as-permissions/
Obviously the “right” way to solve this is to remove a user’s account for the protected groups and create them a supplemental admin account. It is important to note that even if you remove a users from the protected group the “AdminCount” value will
NOT change from “1” back to “Null” (which is why users who were removed months ago were still having the issue). You will have to manually go into ADSIedit and manually change the attribute back to “0”. So, if you can’t remove the user from the
protected group in a pinch the one solution I like is to modify the “adminSDHolder” object’s permissions in ADSIedit so the changes propagate to anyone in the protected group. This will prevent my “send-as” permissions from being overwritten.
Please note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information. And the changes made in the above blog is not supported officially by
Microsoft.
Thanks.
Niko Cheng
TechNet Community Support

Project Site Permissions Being Overwritten

Similar Messages

Maybe you are looking for