|
| |
|
|
Ziggyzaz
Posts: 250
Joined: 5/29/2003
Status: offline
 |
Permission Issues - 4/1/2004 18:16:46
How do we set permissions in the new windows 2003 server? We go in through Front Page and we can only acces the pages to change or add when the frontpage permissions are set, we need to be able to set permissions on the server so people not using frontpage and open up their folders and make changes. Any and all help will be much appricieated.
thanks
_____________________________
Your Chicken is on Fire
|
|
|
|
Richard Dudley
Posts: 668
Joined: 8/22/2002
From: Butler, PA
Status: offline
|
RE: Permission Issues - 4/1/2004 22:33:49
How will they be accessing the server--FTP? UNC file share?
_____________________________
I need to change my avatar--the puppy is full grown now!
| |
|
|
|
Ziggyzaz
Posts: 250
Joined: 5/29/2003
Status: offline
|
RE: Permission Issues - 4/2/2004 13:36:40
Our server is used by quite a few people, I go in through Front Page but others will be using DreamWeaver, ftp and the like. We need the permissions to be available to all of them.
_____________________________
Your Chicken is on Fire
| |
|
|
|
Ziggyzaz
Posts: 250
Joined: 5/29/2003
Status: offline
|
RE: Permission Issues - 4/4/2004 17:34:34
the only thing is they are all working off of the same web just different subwebs.
_____________________________
Your Chicken is on Fire
| |
|
|
|
Richard Dudley
Posts: 668
Joined: 8/22/2002
From: Butler, PA
Status: offline
|
RE: Permission Issues - 4/4/2004 23:05:39
ellipsces is too gracious...
I have no idea how DW will interact with Windows 2003 Server. There are basically two way to set permissions on an IIS server:
1) IIS Permissions. These are managed via FrontPage, and are best used in an all-FP environment. I have not run a Win2K3 server yet, so my knowledge is somewhat limited, but the replacement for the FPSEs is called Sharepoint Services. IIS manages the permissions when using this method.
2) NTFS Permissions. These actually have a new name in the Win2K3 environment, but I can't remember (heard it at an MS seminar the other week, and promptly forgot). In this casem you are setting permissions directly on the files and directories themselves. System Admins typically hate these.
Are you in an Active Directory environment? If so, I would create an AD group for each of the subwebs, and add the appropriate users. Then, grant the groups MODIFY NTFS permissions. If you're not AD, you can either create local groups or domaoin groups and do the same thing. Then, share the folders and limit sharing to the same groups. Users can now directly copy changed files to the server (they should never be developing on a production server). You'll have to check and see if the FP Publish feature will work on a directory share--I've never used FP 2003 in such a setup. If not, I would take the extra step of finding my FP users and setting IIS permissions so they can publish.
For exact details on managing IIS 6, grab an IIS 6 admin manual. There are a LOT of changes from IIS 5, and you could probably teach us all something.
_____________________________
I need to change my avatar--the puppy is full grown now!
| |
|
 New Messages |
 No New Messages |
 Hot Topic w/ New Messages |
 Hot Topic w/o New Messages |
 Locked w/ New Messages |
 Locked w/o New Messages |
|
Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts
|
|
|
Printable Version 
) person tie them all in
