Hi We are running Exchange 2007 SP3 at the moment for our users. We need to carry out message tracking for troubleshooting sometimes, so use the Get-MessageTrackingLog command (e.g. Get-transportserver | Get-messagetrackinglog -sender XXX -recipient XXX etc). This has worked fine for us in 2007. I have an admin machine running the Exchange 2007 EMT for this and other tasks (creating mailboxes etc). We've built out a test Exchange 2010 SP1 Server and moved IT mailboxes across to it. I've sent a few test messages to Hotmail and the Get-messagetrackinglog command from my admin machine still seems to work fine. But Ive just read that for 2010, we should be using Search-MessageTrackingReport to get the Message Tracking ID, then Get-MessageTrackingReport for the report itself. Can anyone confirm if our old method of Get-MessageTrackingLog is now deprecated? Should we not be using this once we move to 2010 SP1?

“Get-MessageTrackingReport” is still there with exchange 2010, it returns the data for a specific message tracking report but this requires you to specify the ID for the message tracking report you want to view so first you need to use Search-MessageTrackingReport cmdlet to find the message tracking report ID for a specific message. Search-MessageTrackingReport cmdlet to find the unique message tracking report based on the search criteria provided. You can then pass this message tracking report ID to the Get-MessageTrackingReport cmdlet to get full message tracking information. See the links below…. http://technet.microsoft.com/en-us/library/dd351138.aspx http://technet.microsoft.com/en-us/library/dd351082.aspxRegards, Pushkal MishrA

Can anyone confirm if our old method of Get-MessageTrackingLog is now deprecated? Should we not be using this once we move to 2010 SP1? @Pushkal: What Pancamowants to know is the Get-MessageTrackingLog command in Exchange 2010, not Get-MessageTrackingReport command. @Pancamo: The Get-MessageTrackingLog command is still used to search message information stored in the message tracking log in Exchange 2010. For more, you can refer to the article ‘Get-MessageTrackingLog’. Hope this helps. ThanksSophia Xu

What I meant is "Get-MessageTrackingLog" is still there .......but to return the data for a specific message tracking report use the Get-MessageTrackingReport cmdlet . Use Get-MessageTrackingLog to search message information stored in the message tracking log.... I thought, I shared two diff article about -MessageTrackingLog & MessageTrackingReport but for some reason above two articles(diff URLs/IDs) resolving to same MessageTrackingReport ..... http://technet.microsoft.com/en-us/library/aa997573.aspx Thanks for pointing out Sophia... Regards, Pushkal MishrA

Thanks all, so we can still keep using our existing commands (Get-transportserver | Get-messagetrackinglog -sender XXX -recipient XXX), there is no need to update them?

Hi, The existing commands like the following command are good and you don’t need to update them: Get-transportserver | Get-messagetrackinglog -sender XXX -recipient XXX ThanksSophia Xu