Hidden Journaling Feature

  • Article

 

Ok it’s not really ‘hidden’ but based on what it does I’m surprised it hasn’t gotten more publicity.

If you recall our journaling recommendations for mixed Exchange 2003 and Exchange 2007/2010 deployments we required you to put the journal recipient mailbox on an Exchange 2003 database.

You can read about that here- https://blogs.technet.com/b/exchange/archive/2009/06/01/3407615.aspx

From the section ‘Location of Journaling Mailbox’ I explained why the journal mailbox needs to be on a 2003 server.

Well starting with Exchange 2007 sp3 RU1 and Exchange 2010 sp1 all that has changed!

If you run a Get-TransportConfig from an Exchange server at one of those levels you will see a new property called ‘LegacyJournalingMigrationEnabled’.

By default this is set to ‘False’.

clip_image002

Set it to ‘$True’ and you will now be able to locate the journal recipient mailbox on an Exchange 2007 sp3 RU1/Exchange 2010 sp1 database in an org that has Exchange 2003 servers.

There is no restart required as transport will pick the change up as soon as the first message passes through.

Note that while the journal report will be in the new Exchange 2007/2010 format it will NOT have the extended fields.

What this means is if a journaled sender BCCs a recipient the report will not indicate that but rather just show the recipient listed in the report.

Below is an example of a journal report of an Exchange 2003 sender who sent a message with Harpo.Marx on the TO: field and Zeppo.Marx on the BCC:-

clip_image004

You can read more about Journal reports here-

https://technet.microsoft.com/en-us/library/bb331962.aspx

Happy journaling!