Please note that this export is turned off by default as it can cause the Mailscape DB table dbo.ExchangeMessageList in the Mailscape Database to grow excessively large depending on the amount of daily traffic sent by your Exchange Organization.
- Open the location the Enow Management System was installed the folder path should end with “MailscapeWeb\MailscapeSQLService”
- you should see the following files located in the folder:
-
from these files we want to select the “EnowMessageLogService.exe.config file and open it using an editor program with Elevated permissions:
-
Once file is open navigate to the bottom of the file to locate the configuration “<add key="TrackExchangeMessageIds" value="false"/>”, note the warning comment above about Disk Space usage:
-
To enable export of the Exchange Message IDs we want to change the value from “value=false” to “value=true” make sure that “true” is all lowercase characters.
-
Save the changes made and close the file
-
Open Services.msc and locate the Enow Message Log Service make sure this is running as a Service account and Local System, if you see Local System in the Log On As column then SQL Integration is not enabled and you should enable it before moving forward:
-
Right-click the Service and choose to the restart option, keep in mind this will begin the reprocessing of all Distilled MessageLogs in the “\MailscapeWeb\MailscapeData\Database\MessageLogs” folder, however, any MessageLogs previously processed will not export the Exchange Message Ids.
-
you have now enabled the export of the ExchangeMessageIds into the Mailscape Database. When the next set of Distilled MessageLogs are captured from the Exchange Servers and sent to the Web Server the Exchange Message Ids will be exported.
Comments
0 comments
Please sign in to leave a comment.