Manually Configuring Intra-Site and Inter-Site Mail Flow Synthetic Transactions

Applies To: Exchange Server, Operations Manager 2007 R2

To configure an agent-managed Mailbox server to perform a remote mail flow synthetic transaction to another Mailbox server within or outside its site, perform the steps below.

Note

You can send mail only between agent-managed Exchange 2007 Mailbox servers within the same organization. The destination mailbox servers must be in the same Exchange organization as the source mailbox server.

To configure an agent-managed Mailbox server to perform a remote mail flow synthetic transaction

  1. Go to the Object Discoveries section under the Authoring node in the Operations console. Ensure that your console is not scoped to a subset of management pack objects.

  2. Ensure that the Look for box is visible by selecting Find in the View menu in the Operations console.

  3. In the Look for box, type Remote and select Find now. A list of object discoveries appears.

  4. Right-click the Exchange 2007 Mailflow Remote Discovery, and choose Overrides\Override the Object Discovery\For a specific object of type: Exchange 2007 Mailbox Role. The Select Object message box appears.

  5. Select the Exchange 2007 Mailbox server you want to use as the sender, and click OK.

  6. The Override Properties dialog box appears. Change the Target Servers parameter. The parameter is a semicolon-separated list of destination Mailbox servers. The override supports using both the simple NetBIOS name of the target Mailbox server and the fully qualified domain name (FQDN). The FQDN is the preferred format to enter into the override.

  7. Choose a destination management pack in which to save the override (making sure not to use the default management pack), and click OK.

A discovery will now run that generates a new instance of a remote mail flow perspective. (This discovery runs every 24 hours by default.) To check that the perspective was created, go to the Mailflow view, which will show all instances of mail flow perspectives.

Changing the manually created mail flow synthetic transactions timeout and frequency

If you want to change the timeout and frequency of the manually created Mail Flow synthetic transactions, perform the following steps:

Note

You can change the Remote Mail Flow synthetic transactions created by using templates through the template wizard. See How to Configure Mail Flow Synthetic Transactions Using the Exchange 2007 Intra-Organization Mail Flow Monitoring Template

To change the timeout and frequency of synthetic transactions

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

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

    Note

    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 Remote Mail Flow Collection rule, and select Overrides\Override the rule\For a specific instance of type: Mail Flow Remote 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 (being sure not to save the overrides in the default management pack). 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.

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

    Note

    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.