|
Home > Archive > FrontPage Server Extensions for Windows > March 2004 > Interactive and Network permissions
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Interactive and Network permissions
|
|
| M. M. Rafferty 2004-02-12, 10:38 am |
| I followed the instructions found at
http://www.microsoft.com/servicepro...s/fpse2002.asp,
"Deploying Microsoft FrontPage 2002 Server Extensions with Windows Server
2003". It solved the problem of adding INTERACTIVE and NETWORK to the web
content ACL.
However, it still adds those to the folder level above the web content. As
that is still within a specific client's folder area, that is not a desired
permission in a shared hosting situation. The special FP group and the
anonymous user were set so they had list folder contents set on the higher
level and read and execute for the web content folder prior to setting up
the extensions.
Am I missing something in setting this up? Or is that as good as it gets?
Mary M. Rafferty
mailto:mmr@vistagrande.com
| |
| Dave Kindness 2004-03-22, 2:37 pm |
| Hi Mary, have you figured out how to stop the extensions from changing your permissions? I too found that article, but for my environment I need to stop the extensions from modifying ALL permissions.
I need FP 2002 ext on W2K3 to work just like FP 2000 ext on W2K. Does anyone know how to completely stop the 2002 extensions from changing NTFS permissions?
Thanks, Dave.
----- M. M. Rafferty wrote: -----
I followed the instructions found at
http://www.microsoft.com/servicepro...s/fpse2002.asp,
"Deploying Microsoft FrontPage 2002 Server Extensions with Windows Server
2003". It solved the problem of adding INTERACTIVE and NETWORK to the web
content ACL.
However, it still adds those to the folder level above the web content. As
that is still within a specific client's folder area, that is not a desired
permission in a shared hosting situation. The special FP group and the
anonymous user were set so they had list folder contents set on the higher
level and read and execute for the web content folder prior to setting up
the extensions.
Am I missing something in setting this up? Or is that as good as it gets?
Mary M. Rafferty
mailto:mmr@vistagrande.com
| |
| M. Rafferty 2004-03-23, 11:36 pm |
| I learned today that the issue I am seeing with the permissions at a higher
level is a known issue and if I understood correctly, will be included in a
Windows 2003 service pack. (No idea when that will happen.)
As I recall, manual permissions isn't an option with FP 2002 extensions.
--
Mary M. Rafferty
mailto:mmr@vistagrande.com
"Dave Kindness" <davekindness@yahoo.com> wrote in message
news:B8D51BC0-08D4-4A4F-BAC1-68E87AF80678@microsoft.com...
> Hi Mary, have you figured out how to stop the extensions from changing
your permissions? I too found that article, but for my environment I need to
stop the extensions from modifying ALL permissions.
>
> I need FP 2002 ext on W2K3 to work just like FP 2000 ext on W2K. Does
anyone know how to completely stop the 2002 extensions from changing NTFS
permissions?
>
> Thanks, Dave.
>
> ----- M. M. Rafferty wrote: -----
>
> I followed the instructions found at
> http://www.microsoft.com/servicepro...s/fpse2002.asp,
> "Deploying Microsoft FrontPage 2002 Server Extensions with Windows
Server
> 2003". It solved the problem of adding INTERACTIVE and NETWORK to
the web
> content ACL.
>
> However, it still adds those to the folder level above the web
content. As
> that is still within a specific client's folder area, that is not a
desired
> permission in a shared hosting situation. The special FP group and
the
> anonymous user were set so they had list folder contents set on the
higher
> level and read and execute for the web content folder prior to
setting up
> the extensions.
>
> Am I missing something in setting this up? Or is that as good as it
gets?
>
> Mary M. Rafferty
> mailto:mmr@vistagrande.com
>
>
>
>
>
| |
| Dave Kindness 2004-03-24, 5:36 pm |
| You wouldn't happen to know the knowledge base article number would you?
Is anyone from Microsoft listening in on this? Back on our old NT 4 servers (that I inherited) we had dead SID's all over the place on the file system from FrontPage users who had left the company. And one day I discovered that a particular security grou
p had full access to the entire web site. This was the result of some junior admin playing with Front Page. When we migrated to Win2000 we built our own ASP based front end for creating new web sites and allowing users to mange their own security entirely
with groups. We do not allow users to manage security with FrontPage.
Now that we are migration to Win2003 I find that the Front Page extensions mess up (IMHO) the file permissions by un inheriting folders and adding needless permissions. Not to mention creating group name that are completely meaningless. OWS_4259896495_adm
in is really descriptive. I would like to stop the 2002 extensions from touching my file permissions just like I did with the 2000 extensions. How can this be accomplished?
----- M. Rafferty wrote: -----
I learned today that the issue I am seeing with the permissions at a higher
level is a known issue and if I understood correctly, will be included in a
Windows 2003 service pack. (No idea when that will happen.)
As I recall, manual permissions isn't an option with FP 2002 extensions.
--
Mary M. Rafferty
mailto:mmr@vistagrande.com
| |
| M. Rafferty 2004-03-25, 1:35 am |
| Sorry, it was something said in a webcast for hosting providers, not a
knowledge base article. There could be one. I just don't know of it.
I suspect you are out of luck with getting changes to allow manual
management of permissions with FrontPage 2002 extensions. Instead you may
find a solution using custom roles with FP 2002 extensions / SharePoint
Services.
--
Mary M. Rafferty
mailto:mmr@vistagrande.com
"Dave Kindness" <davekindness@yahoo.com> wrote in message
news:FE3FE755-4D5B-4BC0-809D-02F1126D41D5@microsoft.com...
> You wouldn't happen to know the knowledge base article number would you?
>
> Is anyone from Microsoft listening in on this? Back on our old NT 4
servers (that I inherited) we had dead SID's all over the place on the file
system from FrontPage users who had left the company. And one day I
discovered that a particular security group had full access to the entire
web site. This was the result of some junior admin playing with Front Page.
When we migrated to Win2000 we built our own ASP based front end for
creating new web sites and allowing users to mange their own security
entirely with groups. We do not allow users to manage security with
FrontPage.
>
> Now that we are migration to Win2003 I find that the Front Page extensions
mess up (IMHO) the file permissions by un inheriting folders and adding
needless permissions. Not to mention creating group name that are completely
meaningless. OWS_4259896495_admin is really descriptive. I would like to
stop the 2002 extensions from touching my file permissions just like I did
with the 2000 extensions. How can this be accomplished?
>
>
> ----- M. Rafferty wrote: -----
>
> I learned today that the issue I am seeing with the permissions at a
higher
> level is a known issue and if I understood correctly, will be
included in a
> Windows 2003 service pack. (No idea when that will happen.)
>
> As I recall, manual permissions isn't an option with FP 2002
extensions.
>
>
> --
> Mary M. Rafferty
> mailto:mmr@vistagrande.com
>
|
|
|
|
|