Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

Users have access to all archives. Now what?

Updated: 31 Oct 2010 | 4 comments
Marc van Duuren's picture
0 0 Votes
Login to vote
This issue has been solved. See solution.

I have the following issues.

All permission rights on the mailbox archives have the proper permission.

However somone gave all users the "send on behalf" right in Exchange. Because of this everyone can search each others archive.

Ofcourse we removed the "send on behalf" right in Exchange, but it looks like still the users can view each others archive.

Do I have to do something else, or is this a time issue and must Enterprise Vault process something first before this is corrected?

 

Any help is appreciated.

Comments

TonySterling's picture
28
Sep
2010
0 Votes 0
Login to vote

You should perform and

You should perform and synchronization of all mailboxes.

 

Right click the archive tasks and choose properties.  On the Synchronization tab choose to synch all mailboxes.

Tony Sterling
www.bluesource.net or www.bluesource.co.uk
Offices in the US and the UK

Marc van Duuren's picture
28
Sep
2010
0 Votes 0
Login to vote

Tony, Thank you for the

Tony,

Thank you for the information. We tried that, but no result (so far).

We can synchronize at any time or not? It's not related to our archiving schedule or anything?

TonySterling's picture
28
Sep
2010
0 Votes 0
Login to vote

yes, you can run that at

yes, you can run that at anytime.  Make sure to include folder heirarchy and permissions.

Tony Sterling
www.bluesource.net or www.bluesource.co.uk
Offices in the US and the UK

JesusWept2's picture
30
Sep
2010
0 Votes 0
Login to vote

remember though that Exchange

remember though that Exchange is gonna cache that for about 2 hours or upon restart of the Information store, EV Caches the security also but should clear it if the security has clearly changed, if all else fails and its not working, you may need to do a permissions zap