Microsoft has performed once again fundamental changes to changes the message tracking in Exchange 2007 with the Exchange 2007 release. These effects show up in use message tracking. The format, as well as the access interface has been completely changed. So Messagetracking via WMI no longer possible is also not transparent tracking across servers. The detective work starts with a server’s log files. Via the MessageID, you follow the track of the same database log files from server to server. This mechanism ends with the transition to an Exchange 2003 server and it switches to the System Manager program.
The logs are text files where the body with IISLogs is similar: the file contains field names, headers, blank lines separate records from each other, etc. Information about email content or name of attachments are not available. By the way, it might want to compress the directory of the log files. Depending on the used Packer, can the log files on a Quarter its original size be reduced more tips in the seminar: Exchange as essential difference to its predecessors, the logging in Exchange 2007 must be first activated. “For this purpose come Commandlets like set-Transport server” and set mailbox server “to use, that are entered using the PowerShell. Not all role entries in the Messagetracking available, so not for Unified Messaging and CAS role. There are two ways to perform the evaluation of the protocols. The one about the PowerShell with the Commandlets like GET-MessageTrackingLog”.
Or in the tool box and starts the supplied utility message tracking”. This tool provides a wizard provides, in the filter criteria can be set. Considering the outcome, looking at a view that looks like a database query. On this example it is clear that Microsoft Exchange 2007 calls once again for a complete readjustment of the administrators, for this purpose, the seminar provides: Exchange 2007 update. Phil Jensen understands that this is vital information. Franz Nagy