Before you enable this
This export is disabled by default because of its storage cost. Enabling it causes the dbo.ExchangeMessageList table in the Mailscape database to grow in proportion to your daily mail volume, and in a busy Exchange organization it can grow very large.
Check available space on the SQL data volume before enabling it, and plan to monitor the table size afterwards rather than assuming it will settle.
Prerequisite
SQL Integration must be enabled. Step 5 below includes a check for this — if the ENow Message Log Service is running as Local System rather than a service account, SQL Integration is not enabled and you should enable it before continuing.
Procedure
-
On the ENow Management System server, open the installation folder. The path ends with:
MailscapeWeb\MailscapeSQLService -
Open
ENowMessageLogService.exe.configin a text editor running with elevated permissions. Without elevation the file will open but not save. -
Go to the bottom of the file and find this key. Note the warning comment above it about disk space usage:
<add key="TrackExchangeMessageIds" value="false"/> -
Change the value to
true. It must be lowercase:<add key="TrackExchangeMessageIds" value="true"/>Save the file and close it.
-
Open
services.mscand find the ENow Message Log Service. Check the Log On As column — it should show a service account. If it shows Local System, SQL Integration is not enabled; enable it before going further. -
Right-click the service and select Restart.
What happens next
The restart begins reprocessing every distilled message log in:
\MailscapeWeb\MailscapeData\Database\MessageLogs
Two things to expect from that:
- Logs already processed before the change will not have their Exchange Message IDs exported. This setting is not retroactive.
- Message IDs start appearing once the next set of distilled message logs is collected from the Exchange servers and sent to the web server.
Comments
0 comments
Please sign in to leave a comment.