Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

what is the best practice if I want to have a retention of let say 6 months ?

I'm confused which parameter that is should/can be changes.

Get-ExchangeServer | where {$_.isHubTransportServer -eq $true} | Get-TransportServer | select Name, *MessageTracking* | ft -AutoSize

Name        MessageTrackingLogEnabled MessageTrackingLogMaxAge MessageTrackingLogMaxDirectorySize MessageTrackingLogMaxFileSize MessageTrackingLogPat                                                                                                                                h                    
----        ------------------------- ------------------------ ---------------------------------- ----------------------------- ---------------------
ExHTServer1                      True 20.00:00:00              250MB                              10MB                          D:\Program Files\M...
ExHTServer2                      True 20.00:00:00              250MB                              10MB                          D:\Program Files\M...
ExHTServer3                      True 20.00:00:00              250MB                              10MB                          D:\Program Files\M...



share|improve this question
up vote 1 down vote accepted

The MessageTrackingLogMaxAge parameter directly controls the length of time after which logs will be deleted; setting that to 180.00:00:00 will get you 6 months.

However, MessageTrackingLogMaxDirectorySize will also be a limiting factor. You will want to set the max directory size to large enough to fit all of the logs you'd like to keep, but keep the limit set to something reasonable - the last thing you want is for that drive to fill up if you have a reply-all storm.

I'd also recommend using a more robust log aggregation and search tool if you're gonna want to look at those logs; Splunk comes to mind.

share|improve this answer
ah yes, many thanks for that Shane – Server System Specialist Mar 2 '11 at 1:50

Your Answer


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.