message transport logs

1) What determines (in exchange 2010) how far back message transport logs go? Is there log files defaults which when surpassed are overwritten?

2) If you have more than one mailbox server in your environment - if you are only interested in one users "message tracking logs" - do you only have to look at the logs for the server that hosts their mailbox? Or does the message tracking app store all logs for all servers?
LVL 3
pma111Asked:
Who is Participating?
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.

Chad FranksSenior System EngineerCommented:
1:  This is a setting within Exchange on whether the logs are enabled and how long to retention will be.

2:  You don't have to specify a server when using message tracking, you are looking at the mailbox/user account level, Exchange will know where to look.
0

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
Adam FarageEnterprise ArchCommented:
1) What determines (in exchange 2010) how far back message transport logs go? Is there log files defaults which when surpassed are overwritten?

You can view the attribute "MessageTrackingLogMaxAge" which is a per transport server configuration. This can be done as follows:

Get-TransportServer | Select Identity, MessageTrackingLogMaxAge

Open in new window


When logs hit there maximum time period, they will then be purged out from the system. If you want to extend this across the organization (or shorten the timeframe):

Get-TransportServer | Set-TransportServer -MessageTrackingLogMaxAge dd.hh:mm:ss

dd = days
hh = hours
mm=minutes
ss=seconds

----------------------------------------------------------------------------------------------------------------

2) If you have more than one mailbox server in your environment - if you are only interested in one users "message tracking logs" - do you only have to look at the logs for the server that hosts their mailbox? Or does the message tracking app store all logs for all servers?

Each hub transport server stores there own set of message tracking logs, which essentially shows the transactions that the HUB transport server has completed and processed.. When you search these (Get-TransportServer | Get-MessageTrackingLogs) you are actually querying all of the HUB transport servers Message Tracking Logs for the items you are looking for. Same goes for "Message Tracking" in ECP for Exchange 2010, or EAC in 2013 (and EMC for Exchange 2007). Same principle and theory has applied forever in Exchange :)

Here is more about the "Get-MessageTrackingLog" command: http://technet.microsoft.com/en-us/library/aa997573%28v=exchg.141%29.aspx

I would highly recommend adding switches to it (such as -Start, -End -Sender and -Recipient) as this can take a while. Also, instead of just running Get-MessageTrackingLog run "Get-TransportServer | Get-MessageTrackingLog -Switches". This will ensure you are actually searching all of the servers.
0
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
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.