Exchange 2013 - Mailbox Access Audit (without auditing enabled)


Windows 2008 R2 (functional level)
Exchange 2013 / 2010 / 2007 (mailboxes on 2013)

My question is, is there a way to audit mailbox access (historically) without mailbox auditing having been enabled.

I had been looking for errors like 1016 but they seem to not be relevant in Exchange 2013.
What event ID's are logged in Exchange 2013/ Windows 2008 R2 GC/DC's for mailbox access by a non-owner (I have searched online but cannot seem to find anything).

I have the potential that someone has been accessing mailboxes and I need to find explicitly the logs that they indeed have - As a non-owner.

Alternatively, is there a way to prove that no non-users have sent email from a mailbox.

Thanks in advance
bryan oakley-wigginsSenior Cloud EngineerAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

AmitIT ArchitectCommented:
I don't see any other way. Any reason for not enabling it?
bryan oakley-wigginsSenior Cloud EngineerAuthor Commented:
HI Amit

Thanks, my thoughts exactly and why I have struggled up to know - I was trying to look at log's on DC's/EX to see any particular Event ID's to state mailbox logon and by whom (like previous versions event id 1016 etc) - Unfortunately it's to determine historical (recent) possible mailbox access, so enabling it now wouldn't bring any benefit to my current requirements (although it looks as though mbx auditing will be enabled going forward).

I am unable either to use mfcmapi to detemine sent by/sent-as, as I do not have the endpoint message data to look through.

I could potentially get a source IP from the message tracking log as well as checking the cmdlets log to see if any spurious changes were made.

Does Exchange 2013/10 not have at least a minimum set of event's at default to log activity?

Thans for your reply though anyhow, much appreciated.

AmitIT ArchitectCommented:
Unfortunately there is no such logging enabled by default, you need to enable it first.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
bryan oakley-wigginsSenior Cloud EngineerAuthor Commented:
Hi Amit

Ok, well I guess you answered my question, so only appropriate I accept as solution.

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.