We’ve spent the past several weeks talking about the anti-spam agents in Exchange 2010. With the closeout of this series, and the imminent release of Exchange 2013, I thought I would share a bit on the anti-x agents in Exchange 2013 so that those of you who are wanting to test the latest version will know what to do, and those of you still considering Exchange 2013 testing can rest assured that much of what you know about Exchange 2010 will transfer right across to Exchange 2013.
There are many similarities between Exchange 2010 and 2013, and this really shows in the ability to enable the anti-spam agents. In Exchange 2010, the idea was to use the Edge Transport server role to perform messaging hygiene, and in Exchange 2013 you will still be able to use Exchange 2010 Edge Transport servers in this capacity. However, in a purely Exchange 2013 environment, there is no Edge Transport server role. The CAS servers will handle this workload. To enable the anti-x agents on your CAS server open an administrative Exchange Management Shell session, browse to your Exchange scripts directory, and run the following command.
If you are thinking that looks familiar, you are right. It’s essentially the same PowerShell script stored in the same location as in Exchange 2010. Once it runs, you will need to restart the Exchange Transport service for the agents to start working. In the same session you can run the command
restart-service msexchangetransport [enter]
Once the agents are running, the ones that you are used to in Exchange 2010 will function in much the same way as they did on Exchange 2010. However, remember that Exchange 2013 includes anti-malware protections built into the product, so we have a new malware filtering agent and a new set of commands. You can manage all the agents through the Exchange Administration Console or using the EMS.
Here’s a rundown of the main types of cmdlet you will have in the EMS.
- Connection Filter
- Recipient Filter
- Sender Filter
- Sender ID
- Sender Reputation
- Mailbox Junk E-Mail
You can view a list of all the various cmdlets available for these categories over at the TechNet page, http://technet.microsoft.com/en-us/library/bb124601(v=exchg.150)