Enable the Antispam Agents on the Hub Transport Server for Multi-Tenancy

 

Applies to: Exchange Server 2010 SP2

Topic Last Modified: 2012-07-23

Because the Edge Transport server role isn't available for Exchange 2010 Service Pack 1 (SP1) multi-tenant deployments, you must configure anti-spam features to run on Hub Transport servers if you want to use that functionality.

To install and enable the anti-spam features on a Hub Transport server, you must run the Install-AntispamAgents.ps1 script. This script is installed when you run Exchange Setup. After you run the script, you must restart the Microsoft Exchange Transport service to finish the installation of the following anti-spam features:

  • Connection filtering

  • Content filtering

  • Sender ID

  • Sender filtering

  • Recipient filtering

  • Sender reputation

importantImportant:
Most Exchange 2010 documentation doesn't refer to the anti-spam features in the context of the Hub Transport server. Therefore, as you read documentation about how to configure, manage, and maintain anti-spam features, remember that all functionality that's documented in the context of the Edge Transport server is also available on the Hub Transport server, unless specifically noted otherwise.

Looking for other management tasks related to managing anti-spam and antivirus features? Check out Managing Anti-Spam and Antivirus Features.

After you run the Install-AntispamAgents.ps1 script, restart the Microsoft Exchange Transport service, and set the InternalSMTPServers parameter.

You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "Hub Transport server" entry in the Transport Permissions topic.

  1. Run the following command from the %system drive%/Program Files\Microsoft\Exchange Server\V14\Scripts folder.

    ./install-AntispamAgents.ps1
    
  2. After the script has run, restart the Microsoft Exchange Transport service by running the following command.

    Restart-Service MSExchangeTransport
    

You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "Hub Transport server" entry in the Transport Permissions topic.

You must specify all internal SMTP servers on the transport configuration object in Active Directory forest before you run connection filtering. Specify the internal SMTP servers by using the InternalSMTPServers parameter on the Set-TransportConfig cmdlet.

importantImportant:
For all anti-spam features to work correctly, you must have at least one IP address of an internal SMTP server set on the InternalSMTPServers parameter on the Set-TransportConfig cmdlet. If the Hub Transport server on which you're running the anti-spam features is the only SMTP server in your organization, enter the IP address of that computer.

The following example adds the internal SMTP server addresses 10.0.1.10 and 10.0.1.11 to the transport configuration of your organization.

Set-TransportConfig -InternalSMTPServers 10.0.1.10,10.0.1.11
 © 2010 Microsoft Corporation. All rights reserved.

Community Additions

Show: