|
|
|
date: Tue, 2 Aug 2005 07:54:10 -0700,
group: microsoft.public.exchange2000.clients
back
Re: Public Folder Permission Problem
Hi John,
Yes you can have item level permissions in E2k public folders. The usually
turn out to be set unintentionally. We have a utility that will strip the
item level permissions from public folder objects. The utility is
pfdavadmin; you can download a copy from here:
ftp://ftp.microsoft.com/pss/tools/Exchange%20Support%20Tools/PFDavAdmin/
It includes documentation on how to use it. The only thing to be aware of
is that this is a best effort support utility. So I would recommend making
sure you have a good backup of your Pub and that you test it out before
running it on your production folder. But it should correct the issue for
you.
Hope this helps,
--
Matthew Byrd
Microsoft PSS
Run Microsoft Exchange Server Best Practices Analyzer Today
http://www.microsoft.com/exchange/downloads/2003/exbpa/default.mspx
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
This posting is provided "AS IS" with no warranties, and confers no rights.
"John Page" wrote in message
news:847C0B04-46FE-4DE5-909A-CFFC4468D3AA@microsoft.com...
> We are running Exchange 2000 and Office 2003. When some users attempt to
> open a contact in a public folder, it is opening up read-only. Other
> contacts in the same folder open fine. The user has Read, Create, Edit
> All,
> Delete None, Folder Visible as permissions.
>
> I thought the permissions were set at a folder level and could not be set
> on
> a per contact basis. How can I fix this? What additional information is
> needed to help solve this problem?
>
> Thanks,
>
> John
>
date: Thu, 4 Aug 2005 13:04:44 -0400
author: Matthew Byrd [MSFT]
Re: Public Folder Permission Problem
Matthew,
Thanks the tool did remove the item level permissions and restore everyone's
ability to edit as set by the folder permissions. I did, however, need to
increase the timeout value for the software in order for it to complete on
our folder with just over 10,000 entries.
Thanks again,
John
"Matthew Byrd [MSFT]" wrote:
> Hi John,
>
> Yes you can have item level permissions in E2k public folders. The usually
> turn out to be set unintentionally. We have a utility that will strip the
> item level permissions from public folder objects. The utility is
> pfdavadmin; you can download a copy from here:
>
> ftp://ftp.microsoft.com/pss/tools/Exchange%20Support%20Tools/PFDavAdmin/
>
> It includes documentation on how to use it. The only thing to be aware of
> is that this is a best effort support utility. So I would recommend making
> sure you have a good backup of your Pub and that you test it out before
> running it on your production folder. But it should correct the issue for
> you.
>
> Hope this helps,
> --
> Matthew Byrd
> Microsoft PSS
>
> Run Microsoft Exchange Server Best Practices Analyzer Today
> http://www.microsoft.com/exchange/downloads/2003/exbpa/default.mspx
>
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "John Page" wrote in message
> news:847C0B04-46FE-4DE5-909A-CFFC4468D3AA@microsoft.com...
> > We are running Exchange 2000 and Office 2003. When some users attempt to
> > open a contact in a public folder, it is opening up read-only. Other
> > contacts in the same folder open fine. The user has Read, Create, Edit
> > All,
> > Delete None, Folder Visible as permissions.
> >
> > I thought the permissions were set at a folder level and could not be set
> > on
> > a per contact basis. How can I fix this? What additional information is
> > needed to help solve this problem?
> >
> > Thanks,
> >
> > John
> >
>
>
>
date: Fri, 5 Aug 2005 05:36:04 -0700
author: John Page
Re: Public Folder Permission Problem
Hi John,
Excellent, Glad to hear that we were able to get you fixed up.
Thanks for the Feedback
--
Matthew Byrd
Microsoft PSS
Run Microsoft Exchange Server Best Practices Analyzer Today
http://www.microsoft.com/exchange/downloads/2003/exbpa/default.mspx
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
This posting is provided "AS IS" with no warranties, and confers no rights.
"John Page" wrote in message
news:A1E2B33B-F273-4AE8-ACAF-BAD7F5929863@microsoft.com...
> Matthew,
>
> Thanks the tool did remove the item level permissions and restore
> everyone's
> ability to edit as set by the folder permissions. I did, however, need to
> increase the timeout value for the software in order for it to complete on
> our folder with just over 10,000 entries.
>
> Thanks again,
>
> John
>
> "Matthew Byrd [MSFT]" wrote:
>
>> Hi John,
>>
>> Yes you can have item level permissions in E2k public folders. The
>> usually
>> turn out to be set unintentionally. We have a utility that will strip
>> the
>> item level permissions from public folder objects. The utility is
>> pfdavadmin; you can download a copy from here:
>>
>> ftp://ftp.microsoft.com/pss/tools/Exchange%20Support%20Tools/PFDavAdmin/
>>
>> It includes documentation on how to use it. The only thing to be aware
>> of
>> is that this is a best effort support utility. So I would recommend
>> making
>> sure you have a good backup of your Pub and that you test it out before
>> running it on your production folder. But it should correct the issue
>> for
>> you.
>>
>> Hope this helps,
>> --
>> Matthew Byrd
>> Microsoft PSS
>>
>> Run Microsoft Exchange Server Best Practices Analyzer Today
>> http://www.microsoft.com/exchange/downloads/2003/exbpa/default.mspx
>>
>> When responding to posts, please "Reply to Group" via your newsreader so
>> that others may learn and benefit from your issue.
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "John Page" wrote in message
>> news:847C0B04-46FE-4DE5-909A-CFFC4468D3AA@microsoft.com...
>> > We are running Exchange 2000 and Office 2003. When some users attempt
>> > to
>> > open a contact in a public folder, it is opening up read-only. Other
>> > contacts in the same folder open fine. The user has Read, Create, Edit
>> > All,
>> > Delete None, Folder Visible as permissions.
>> >
>> > I thought the permissions were set at a folder level and could not be
>> > set
>> > on
>> > a per contact basis. How can I fix this? What additional information
>> > is
>> > needed to help solve this problem?
>> >
>> > Thanks,
>> >
>> > John
>> >
>>
>>
>>
date: Fri, 5 Aug 2005 10:43:17 -0400
author: Matthew Byrd [MSFT]
|
|
