Microsoft KB Archive/216431

= Unique Permissions Are Not Inherited from the Parent Web =

Article ID: 216431

Article Last Modified on 2/22/2007

-

APPLIES TO


 * Microsoft FrontPage 2000 Server Extensions

-



This article was previously published under Q216431



SYMPTOMS
When you use the FrontPage client to change a Web's permissions on the Microsoft Internet Information Server (IIS) from Use same permissions as parent Web to Use unique permissions for this Web, some users and groups are dropped.



CAUSE
Setting a Web to use unique permissions changes the permissions for the Web so that its permissions can be managed separately from the root Web. This allows you to have different content areas which are managed by different accounts. You might assume that setting the Web to use unique permissions would cause the Web to initially inherit the parent Web's accounts, and that they could be modified after changing the setting to unique. The actual behavior is that FrontPage will drop Administrator and Author accounts that are not the person who is logged on making the change to unique permissions. Any account with Browse access and the account that is making the change to unique are kept. The Administrators group is also kept if that is the group the person making the change belongs to.



RESOLUTION
To resolve this problem, open the sub Web in FrontPage, and add back any accounts that were dropped.



STATUS
Microsoft has confirmed that this is a problem in the FrontPage 2000 Server Extensions.

Additional query words: front page

Keywords: kbbug kbpending KB216431

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.