|
Home > Archive > IIS Server > December 2004 > setting up iis6 for publishing
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 |
setting up iis6 for publishing
|
|
|
| hello,
trying to figure out the best way to allow some web publishing to happen on
our Intranet development server.
Here is the info:
iis6
2003 domain
xp sp2 clients
frontpage 2002 (from the office xp cd)
Directory structure:
\Intranet
\images
\sales
\research
\includes
\library
\pdf
default.htm
etc.....
2 groups of people need access:
1. We have some library staff that use Frontpage 2002 and they need to be
able to manipulate files in the following folders:
\images
\includes
\library
2. Our web developers do not use frontpage (use dreamweaver) and they need
permissions to everything. No issues here.
Right now, I have the root folder "Intranet" shared out. If I give the
library group read/write at this level, and therefore every directory
underneath, they can connect with FP and publish just fine. (but they can
also connect directories they are not supposed to...unless i go through
perms on every directory)
If I give them just read access at the root, then give them read/write to
just the directories they need, they get this error in FP:
"Server error: the server extensions were unable to access the file
"I:\_vti_pvt\service.lck. Check file permissions".
The IIS6 pocketbook I am paging through appears to say if the app is WEBDav
enabled, then I can use IIS permissions to just give Read, Write and Browse
Directory for folders, etc. I do this, but when try to add a network place
for the library staff to connect to it tells me I need a share to connect
to.
So, do I need to mess with all the NTFS permissions until they are correct,
or am I going about this the wrong way? I figured maybe I dont even need
the share, the webdav enabled FP would connect and allow publishing based on
IIS perms I set?
Also, I was thinking, that since the Frontpage 2002 extensions are installed
on this server, but I have not yet "Extended" this Intranet web yet because
I am trying to get a better idea of what that means. Is THIS the issue and
should I extend?
Thanks in advance for reading all of this.
Jeff
| |
| Ken Schaefer 2004-12-28, 7:56 am |
| My suggestion?
a) Have a share (or whatever you are using at the moment) for the
Dreamweaver people. That seems to be under control.
b) Use FPSE for the FPSE2002 users. Within FPSE Administration Site you can
choose which folders can be edited by which users (you'll need to setup a
group to contain your users, add either a Windows group, or individual user
accounts to that FPSE group, then give the FPSE group appropriate authoring
permissions). FPSE on the server will take care of the editing stuff (and
you can reset all the NTFS permissions back to the default except for the
Dreamweaver users).
Cheers
Ken
"JJP" <anonymous@discussions.microsoft.com> wrote in message
news:undppLG7EHA.3944@TK2MSFTNGP12.phx.gbl...
> hello,
> trying to figure out the best way to allow some web publishing to happen
> on our Intranet development server.
> Here is the info:
>
> iis6
> 2003 domain
> xp sp2 clients
> frontpage 2002 (from the office xp cd)
>
> Directory structure:
> \Intranet
> \images
> \sales
> \research
> \includes
> \library
> \pdf
> default.htm
> etc.....
>
> 2 groups of people need access:
> 1. We have some library staff that use Frontpage 2002 and they need to be
> able to manipulate files in the following folders:
> \images
> \includes
> \library
>
> 2. Our web developers do not use frontpage (use dreamweaver) and they
> need permissions to everything. No issues here.
>
> Right now, I have the root folder "Intranet" shared out. If I give the
> library group read/write at this level, and therefore every directory
> underneath, they can connect with FP and publish just fine. (but they can
> also connect directories they are not supposed to...unless i go through
> perms on every directory)
>
> If I give them just read access at the root, then give them read/write to
> just the directories they need, they get this error in FP:
> "Server error: the server extensions were unable to access the file
> "I:\_vti_pvt\service.lck. Check file permissions".
>
> The IIS6 pocketbook I am paging through appears to say if the app is
> WEBDav enabled, then I can use IIS permissions to just give Read, Write
> and Browse Directory for folders, etc. I do this, but when try to add a
> network place for the library staff to connect to it tells me I need a
> share to connect to.
>
> So, do I need to mess with all the NTFS permissions until they are
> correct, or am I going about this the wrong way? I figured maybe I dont
> even need the share, the webdav enabled FP would connect and allow
> publishing based on IIS perms I set?
> Also, I was thinking, that since the Frontpage 2002 extensions are
> installed on this server, but I have not yet "Extended" this Intranet web
> yet because I am trying to get a better idea of what that means. Is THIS
> the issue and should I extend?
>
> Thanks in advance for reading all of this.
> Jeff
>
>
>
>
>
>
| |
|
| Ken, thank you for the reply.
I have a couple of follow-up questions for you.
1. On the FPSE Admin Site, I cannot find where to specify which folders can
be edited by a group. I have went to the admin site, created some roles,
created a group and assigned a role to them....but I cannot find where to
specify which folders they can access.
2. How does FrontPage on the client connect to this web? I log onto the XP
client, open FrontPage, "open web" browse My Network Places to the IIS6
server, but nothing shows up to connect to.
Thanks again for your help.
Jeff
"Ken Schaefer" <kenREMOVE@THISadopenstatic.com> wrote in message
news:eneQU5N7EHA.3944@TK2MSFTNGP12.phx.gbl...
> My suggestion?
>
> a) Have a share (or whatever you are using at the moment) for the
> Dreamweaver people. That seems to be under control.
>
> b) Use FPSE for the FPSE2002 users. Within FPSE Administration Site you
> can choose which folders can be edited by which users (you'll need to
> setup a group to contain your users, add either a Windows group, or
> individual user accounts to that FPSE group, then give the FPSE group
> appropriate authoring permissions). FPSE on the server will take care of
> the editing stuff (and you can reset all the NTFS permissions back to the
> default except for the Dreamweaver users).
>
> Cheers
> Ken
>
> "JJP" <anonymous@discussions.microsoft.com> wrote in message
> news:undppLG7EHA.3944@TK2MSFTNGP12.phx.gbl...
>
>
| |
|
| I think I figured out my question 2. Looks like when in FP and you Open
Web... you have to type in the URL of the iis server to connect.
But I am still struggling with #1.
I cannot find where to manipulate permissions on a folder by folder basis.
I created the Library group on the FPSE admin page and gave them author
rights.
But now they can author any file in any folder in the "Intranet" folder.
I check the NTFS permissions and that FPSE group I created for them has
"List" permissions only....which is fine, I dont care if they can see
everything. But I only want them to be able to edit in certain folders.
I will keep digging, any more help is much appreciated.
Jeff
"JJP" <anonymous@discussions.microsoft.com> wrote in message
news:OFkMARP7EHA.2156@TK2MSFTNGP10.phx.gbl...
> Ken, thank you for the reply.
> I have a couple of follow-up questions for you.
> 1. On the FPSE Admin Site, I cannot find where to specify which folders
> can be edited by a group. I have went to the admin site, created some
> roles, created a group and assigned a role to them....but I cannot find
> where to specify which folders they can access.
>
> 2. How does FrontPage on the client connect to this web? I log onto the
> XP client, open FrontPage, "open web" browse My Network Places to the IIS6
> server, but nothing shows up to connect to.
> Thanks again for your help.
> Jeff
>
>
>
> "Ken Schaefer" <kenREMOVE@THISadopenstatic.com> wrote in message
> news:eneQU5N7EHA.3944@TK2MSFTNGP12.phx.gbl...
>
>
|
|
|
|
|