Skip to main content

Exchange Server 2010 – Changing Message Tracking Log Retention Period

Exchange Server 2010 – Changing Message Tracking Log Retention Period

To ensure that the Message Tracking Log is enabled, inside the Exchange Management Console, navigate to the following area:
Server Configuration >
Hub Transport >
Right click on your Hub Transport entry > Properties
Log Settings Tab >
Check the box labeled "Enable message tracking log" and directly underneath it, enter the path where your log files will reside.
Open the Exchange Management Shell console and determine your server’s identity and verfiy logging is enabled with either of these commands.
Get-TransportServer | Select Name,MessageTrackingLogEnabled | ft -auto
Get-MailboxServer | Select Name,MessageTrackingLogEnabled | ft -auto
Here you can check the current Message Logging values. It also aids in determining which switches to set.
Get-MailboxServer YourServerName | fl messagetracking*
You should see something like this…
MessageTrackingLogEnabled               : True
MessageTrackingLogMaxAge                : 30.00:00:00
MessageTrackingLogMaxDirectorySize      : 1000 MB (1,048,576,000 bytes)
MessageTrackingLogMaxFileSize           : 10 MB (10,485,760 bytes)
MessageTrackingLogPath                  : C:\Program Files\Exchange\TransportRoles\Logs\MessageTracking
MessageTrackingLogSubjectLoggingEnabled : True
Change your values to something more useful. In my case, space was not an issue so I enabled logging for 365 days and allocated 10 GB for log files.
Set-TransportServer YourServerName -MessageTrackingLogMaxAge 365
Set-TransportServer YourServerName -MessageTrackingLogMaxDirectorySize 10000MB
Link: https://www.paperstreetonline.com/2013/11/11/exchange-server-2010-changing-message-tracking-log-retention-period/

Comments

Popular posts from this blog

[RAID] SWITCH FROM AHCI TO RAID WITH INTEL C600 CONTROLLER

I personally have used other ways to do this. Manipulating some registry settings in combination with a safe boot before booting normally does the trick as well. This works with both SATA SSD and M.2 NVMe drives and it enables relatively fast switching between back and forth between AHCI and RAID. I have described this method below.  I have also tried the same process used to switch from RAD to AHCI and that works as well. Switch to safe boot Reboot into BIOS Change from AHCI to RAID in the BIOS Boot into safe mode Turn off safe mode and reboot normally again Nothing else and that also did the trick, just like with moving from RAID to AHCI.  So the link above and my step by step below is here for completeness. You have options in case one of them doesn’t work! Step by step AHCI to RAID registry method This procedure I describe below works on Windows 10 1803/1809 and has been tested on Dell Latitude E6220 an XPS 13 9360. Editing the registry is...

TẠO DKIM RECORD CHO EXCHANGE SERVER

  Source: https://www.linkedin.com/pulse/how-configure-dkim-exchange-2019-simple-way-seyed-abdollahi Installation In Exchange Online DKIM is a built-in service, but on an on-prem Exchange 2019 deployment we need a 3rd party application to add this functionality to our Exchange infrastructure. In this guide we use Stefan Profanter's excellent dkim-exchange application for this purpose, which is available here:  https://github.com/Pro/dkim-exchange/releases/latest After installing the program, we open  Configuration.DkimSigner.exe and click on the "Install" button, or download the installer straight from https://codeload.github.com/Pro/dkim-exchange/legacy.zip/v*** Configuration After installation finished, open the configurator. C:\Program Files\Exchange DkimSigner\Configuration.DkimSigner.exe Click on the "Configure" button and move the DkimSigner agent to the very bottom of the list. Under the DKIM settings tab select relaxed canonicalization as Exchange t...

GIA HẠN SSL CHO EXCHANGE SERVER 2019

LINK: https://www.alitajran.com/create-certificate-exchange-server/#h-step-2-generate-exchange-certificate-request  ==Create request SSL New-ExchangeCertificate -Server "EXIDC1" -GenerateRequest -FriendlyName "EXCERT2025" -PrivateKeyExportable $true -SubjectName "c=VN, s=HCM, l=HCM, o=TTT, ou=IT, cn=mail.ttt.vn" -DomainName mail.ttt.vn,autodiscover.ttt.vn,autodiscover.saigonxanh.com,autodiscover.mpu.edu.vn ==Complete SSL Import-ExchangeCertificate -FileData ([System.IO.File]::ReadAllBytes('\\exidc1\Cert$\2378696128.crt')) -PrivateKeyExportable:$true -Password (ConvertTo-SecureString -String 'tttcompany' -AsPlainText -Force)