Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Can somebody please link me to or provide me with instructions on how to enable auditing on all Exchange 2010 mailboxes so we can view when somebody accesses a mailbox that they are not the owner of.

Additionally, what sort of performance impact will this have on an environment with 200 mailboxes? How much disk space will these logs potentially use?

Also, how can I specify exactly where I want the logs to be stored and set them to rotate after a specified amount of time.

share|improve this question

1 Answer 1

up vote 4 down vote accepted

Each mailbox has separate auditing options for administrators, delegates and the mailbox owner - all of which are disabled by default. You can view the various auditing properties by issuing Get-Mailbox jsmith |fl *Audit* in the Exchange Management Shell. To enable auditing on a particular mailbox, use the cmdlet Set-Mailbox jsmith -AuditEnabled $True.

To view the logs use the Search-MailboxAuditLog cmdlet, whose options are documented over on TechNet. An example cmdlet to run to view the audit logs is Search-MailboxAuditLog jsmith -LogonTypes Admin,Delegate -StartDate 1/1/2010 -EndDate 12/31/2010 -ResultSize 2000. This will restrict the selection criteria to reports for the user jsmith, only show admin and delegate actions between 1st January 2010 and 31st December 2010 with a maximum of 2000 results.

Alternatively, you can view a much more sensible and human-readable version of these logs in the Exchange Control Panel under Auditing Reports and then Run a non-owner mailbox access report.

Notice that auditing can be enabled for three access types - admin, delegate, and owner. The amount of logging that is generated will depend on which access types you audit. Obviously owner would be the most log intensive and is one you'd probably want to leave turned off.

The logs are stored in the mailbox, you have no control over where to store them, but you can set a retention limit on them to reduce the storage overhead.

Source for most of this information.

share|improve this answer
1  
Paul, we advise against answers here where the actual solution is a link off-site. Please consider pasting the relevant information into your answer here - that way, if the site you linked to ever goes down the solution is not lost. –  Ben Pilbrow May 24 '11 at 10:30
    
Regardless, I appreciate the reply. Wasn't sure I was going to get one to this question...thanks! –  Windows Ninja May 24 '11 at 13:06
    
I've copied most of the important information into this post, so it doesn't require off-site linkage any more to find the actual solution. –  Ben Pilbrow May 24 '11 at 17:11

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.