A recent discussion has prompted me to write this and clarify some of the cmdlets and features relating to Antispam agents on Hub Transport servers; so here are the facts around it:
- To install antispam agents on a Hub Transport server: From EMS, Install-AntiSpamAgents.PS1
- To enable the Antispam Tab in the Exchange Management Console: Set-TransportServer -AntiSpamAgentsEnabled $True (Automatically run as part of the script mentioned above)
- To view the list of INSTALLED Transport Agents: Get-TransportAgent (Note: If you disable an agent from the EMC, it will still show under this task as ENABLED)
- To view the status of a specific Transport Agent, for example Content Filtering agent: Get-ContentFilterConfig | FL (Note: If you disable the agent from the EMC, it will show under this task as DISABLED)
- To disable a specific Transport Agent, for example Content Filtering agent: Set-ContentFilterConfig -Enabled $False
Confused yet?
Basically, when you disable an agent from the list of agents in the EMC, and run a Get-TransportAgent, it shows as enabled. That is because you are disabling the filtering feature of the agent from the EMC and not the actual agent running on the messages. The whole thing is really not documented anywhere and may lead to confusion from some admins. Even more confusing, if you run the Set-TransportServer -Antispamagentsenabled $True cmd, the tab will show up in the EMC, but the agents will actually NOT be installed.
