|
|||||||
![]() |
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|
#1 |
|
Resident Slacker
Join Date: Dec 2001
Location: Suisun City, California (i know, where the hell is that?!?!?)
Posts: 2,620
|
permissions in exchange 2000
hey guys,
i just set up a brand new exchange 2000 server. on the public folders, i set up the users so they all have permission to edit stuff, but not delete. when they tried to, they got the following message: your changes could not be saved because you don't have permission to modify some or all of the items in this folder. so, i set them up as owners, and they still get the message. am i missing something? aren't owners supposed to be able to modify everything in their folder?
__________________
Friends help you move. REAL friends help you move bodies. - me quite possibly the best book ever written... by me |
|
|
|
|
|
#2 |
|
Member (12 bit)
Join Date: Feb 2001
Location: UK
Posts: 2,469
|
Hi homer15,
Sorry I have no experience with Exchange, but in W2K there is a thing about inheriting permissions from an object's parents Does this apply here? Do you need to set properties for certain items in the folders? Perhaps that's what the users are having problems with Again, just a thought but it might help Jim |
|
|
|
|
|
#4 |
|
Resident Slacker
Join Date: Dec 2001
Location: Suisun City, California (i know, where the hell is that?!?!?)
Posts: 2,620
|
thanks guys.
fatboyjim: yea, the inherent permissions apply here... but it's a little bit different. the public folder structure is set differently than the rest of 2000. mairving: thanks, i came accross that yesterday while i was working through fixing this problem. apparently, this is a big problem with exchange 2000. most stuff that i find just ends with "Microsoft acknowledges that there is a problem with Exchange 2000 Server" but they apparently don't try to fix it. ![]() what i had to do was completely recreate the public folders, and set permissions on them before anything got copied into them. it was as if the existing items weren't inheriting the permissions that were being changed. so, i set the folders up with pre-defined permissions, and then copied the items. this forced them to take on the parent folders permissions. i have the default set with edit but no delete permissions, and i have the administrator and 2 other users set up as owners. i realize that if our employment structure changes (ie, if one of those owners quits), it might be hard to get someone to be able to delete existing items, but at least the administrator can always do it. what a hunk of junk. |
|
|
|
![]() |
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|