Message Tracking

Exchange 2007 tiene una solucion de track, una salvedad es q cuado se ejecuta desde una consola solo buscara el track con los logs locales de ese particular hub server.
La consola muestra por debajo la opcion de Pshell para ejecutarla, con lo q la solucio n seria:

Get-ExchangeServer | where {$_.isHubTransportServer -eq $true -or $_.isMailboxServer -eq $true} | parametros de consola

http://technet.microsoft.com/en-us/library/bb124926%28EXCHG.80%29.aspx

Working With the Search Results

Once you have a search which returns the results you need, you may want to convert those results into other formats, perhaps to use for reports or to provide information to others. PowerShell includes built-in cmdlets for re-formatting output data, and those can be used in conjunction with the Get-MessageTrackingLog cmdlet. For the ‘Recipients’, ‘RecipentStatus’ and ‘Reference’ properties it’s necessary to convert the data so that it appears in the output files.

To convert the results to CSV format you can pipe the search command to the Export-CSV cmdlet. This command will create a CSV file called C:\Temp\SearchResults.csv, exporting all the available fields:

[PS] C:\>Get-MessageTrackingLog -Server EXCHANGE01 -EventID SEND -Sender john@example.com -Recipients bill@example.net -Start 12/3/2009 -End 13/3/2009 | Select Timestamp, ClientIp, ClientHostname, ServerIp, ServerHostname, SourceContext, ConnectorId, Source, EventId, InternalMessageId, MessageId, {$_.Recipients}, {$_.RecipientStatus}, TotalBytes, RecipientCount, RelatedRecipientAddress, {$_.Reference}, MessageSubject, Sender, ReturnPath, MessageInfo | Export-CSV C:\Temp\SearchResults.csv

This command will create a CSV file including only the timestamp, event ID, sender, recipients, and subject line:

[PS] C:\>Get-MessageTrackingLog -Server EXCHANGE01 -EventID SEND -Sender john@example.com -Recipients bill@example.net -Start 12/3/2009 -End 13/3/2009 | Select Timestamp, EventID, Sender, {$_.Recipients}, MessageSubject | Export-CSV C:\Temp\SearchResults.csv

Alternatively, to convert the results to HTML you can pipe the search command to the ConvertTo-HTML cmdlet. Use this command to export the results to an HTML file showing the timestamp, event ID, sender, recipients, and subject line:

[PS] C:\>Get-MessageTrackingLog -Server EXHUB-00-UK -EventID SEND -Sender john@example.com -Recipients bill@example.net -Start 12/3/2009 -End 13/3/2009 | ConvertTo-Html Timestamp, EventID, Sender, {$_.Recipients}, MessageSubject | Set-Content C:\Temp\logs.html

El siguiente ling tiene un script muy bueno de como sacar una metrica del dia anterior:

http://www.simple-talk.com/content/print.aspx?article=681

Reporting on e-mail messages sent and received yesterday

Circular loging

Switching CCR Storage Groups into Circular Logging during Migration - and why you might want to do this…

De la pagina Telnetport25, (jajaj muy bueno el nombre), estos muchachos subieron un script muy bueno q habilita CL en forma automatica, claro q esto implica montar y desmontar las bases de datos, este script lo hace en forma automatica.

La mala noticia es q para exchange2007 CCR cluster esto no es suficiente, tenemos q reinicia el servicio de MSExchangeIS o hacer un Fail Over.

http://www.telnetport25.com/component/content/article/16-exchange-2007-ccr/318-switching-ccr-storage-groups-into-circular-logging-during-migration-and-why-you-might-want-to-do-this.html

Esto es lo q dice MS con respecto a CL, ya es voz populi:

n the release to manufacturing (RTM) version of Exchange 2007, combining circular logging with cluster continuous replication (CCR) or local continuous replication (LCR) is supported. However, we do not recommend this because it does not allow a roll-forward recovery after a backup has been restored. Exchange 2007 Service Pack 1 (SP1) also allows storage groups in a CCR, LCR or standby continuous replication (SCR) environment to have circular logging enabled. However, this practice is also not recommended for the reason indicated previously. When enabled in either of these environments, the functionality is CRCL and not ESE circular logging (also known as Joint Engine Technology (JET) circular logging). In a CCR, LCR, or SCR environment, you should always use the following process to enable or disable circular logging:

1. Suspend continuous replication by using the Suspend-StorageGroupCopy cmdlet.
   
2. Enable or disable circular logging. For detailed steps about how to enable or disable circular logging, see How to Enable or Disable Circular Logging for a Storage Group.
   
3. Dismount and then mount the database in the storage group that is being enabled or disabled for circular logging.
   
4. Resume continuous replication by using the Resume-StorageGroupCopy cmdlet.

http://technet.microsoft.com/en-us/library/bb331951%28EXCHG.80%29.aspx

Esto ultimo no es tan asi por mi comentario anterior.