Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 310758 - Last Review: February 21, 2007 - Revision: 2.1
Permission Changes on a Web Site Are Not Implemented Correctly
This article was previously published under Q310758
When you adjust permissions on a Microsoft FrontPage-extended Web, there may be unwanted permission changes to subwebs that are contained in that Web.
You may see the following behaviors:
- Permission changes that you configure are not implemented or are incorrectly implemented.
- The permissions that you configure in a subweb are overwritten by permissions in the Web that contains the subweb.
This behavior can occur in the following situation:
- You create subwebs in a FrontPage-extended Web.
- You manually configure permission settings in those subwebs.
- You use FrontPage to configure permissions in the FrontPage-extended Web.
This issue occurs because the FrontPage Server Extensions that are installed on a Web site attempt to control all content in that site. When you attempt to manually configure the permissions on a subweb within the FrontPage Web, permission conflicts may arise between the manually applied permissions and the FrontPage Server Extensions that are effectively applied to the entire Web site.
To resolve this issue, use one of the following methods.
Method 1: Create Additional Virtual Servers
To avoid permission conflicts between FrontPage-extended Webs and subwebs in which permissions are manually configured, create new virtual servers (Web sites) for each subweb that you want to configure with separate permissions.
Method 2: Create Additional Content Areas
If you have only one virtual server available, or if it is impractical to create additional virtual servers, create a content area outside of the folder structure of the FrontPage-extended Web site. Configure a virtual directory to point to this new content area for the content of the subweb. Manually configure permissions on the new content area.
For additional information about how to create a virtual directory, click the article number below
to view the article in the Microsoft Knowledge Base:
308135Â
(http://kbalertz.com/Feedback.aspx?kbNumber=308135/EN-US/
)
HOW TO: Create a Virtual Directory
For additional information about configuring security on your FrontPage Web, click the article number below
to view the article in the Microsoft Knowledge Base:
306011Â
(http://kbalertz.com/Feedback.aspx?kbNumber=306011/EN-US/
)
FP2000: Security Best Practices for FrontPage 2000
301432Â
(http://kbalertz.com/Feedback.aspx?kbNumber=301432/EN-US/
)
FP2000: How to Create a Subweb and Add Permissions
216705Â
(http://kbalertz.com/Feedback.aspx?kbNumber=216705/EN-US/
)
How to Set Permissions on a FrontPage Web on IIS
240735Â
(http://kbalertz.com/Feedback.aspx?kbNumber=240735/EN-US/
)
How to Reset Multiple Virtual Server Permissions
296596Â
(http://kbalertz.com/Feedback.aspx?kbNumber=296596/EN-US/
)
Front Page Server Extensions Do Not Work As Expected
APPLIES TO
- Microsoft FrontPage 2000 Server Extensions
- Microsoft FrontPage 2000 Standard Edition
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate