Manually Configuring Local Mail Flow Synthetic Transactions

適用於: Operations Manager 2007

By default, a local mail flow synthetic transaction is automatically enabled on every agent-managed Mailbox server. This is done via the Exchange 2007 Test Local Mail Flow monitor which runs every 15 minutes by default and performs a local mail flow transaction. You can change this transaction by overriding the appropriate parameters.

To change the time-out and frequency of synthetic transactions

  1. Go to the Rules node in the Authoring section of the Operations console.

  2. Change scope to targets that start with “Mail Flow”.

    This procedure assumes that you are changing the settings for a remote mail flow procedure. Depending on the rule you are changing, you might change the scope to targets such as “Mail Flow Cross Org Connectivity”, “Mail Flow Local Connectivity”, or “Mail Flow Remote Connectivity”.

  3. Right-click the Exchange 2007 Test Local Mail Flow Collection rule, and select Overrides\Override the rule\For a specific instance of type: Mail Flow Local Connectivity.

  4. Change the Interval Seconds (which is the frequency with which the transaction runs) and Error Latency (which is the value at which the Exchange test-mailflow cmdlet marks a transaction as failed) values to the desired ones. You might also change the Time-out Seconds value, which controls how long the cmdlet can run for in total. By default, 5 minutes is allowed.

    By default, when you create a management pack object, disable a rule or monitor, or create an override, Operations Manager saves the setting to the Default Management Pack. As a best practice, you should create a separate management pack for each sealed management pack you want to customize, rather than saving your customized settings to the Default Management Pack. For more information, see Customizing Management Packs (

  5. Perform the same steps on the Exchange 2007 Test Local Mail Flow Monitor.

    Be sure to use the same Sync Time, Log Level (Logging Level), Time-out Seconds, Interval Seconds, and Error Latency values for the rule and monitor. This ensures that the synthetic transaction will run only once. If you use different overrides for the rule and monitor, the synthetic transaction will run multiple times: once for collecting performance data and once for collecting state information.