Tuesday, December 21, 2010 9:53 PM
SBS 2008 included a trial for Forefront Protection for Exchange but this has been striped from the release of SBS 2011.
Is it possible to install Forefront for Exchange Server 2010 on a SBS 2011 installation?
Wednesday, December 22, 2010 8:43 AMModeratorTheoretically, I consider that we can install Forefront for Exchange 2010 on SBS 2011.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Wednesday, December 22, 2010 4:32 PM
I gave it a shot and the first problem I found was that if you enable Anti-Spam in FFPE 2010, it will automaticly disable Content Filtering in Exchange 2010. This will make "Spam protection for e-mail" turn red and the status "Critical" in the security section of SBS 2011 Management Console.
Is there any chance that you can force this error to go away (since you got a better anti-spam from MS)?
Friday, December 24, 2010 12:55 PM
Just like sbs 2008 it is possible to disable the warning but surprising that it is necessary given SBS 2011 is new and this issue existed with sbs 2008 and Forefront 2010.
To eliminate the error close the sbs console and navigate to c:\program files\Windows Small Busness Server\Data\SHE extensions. Either rename or relocate E12Antispam.xml. I created a new folder in the SHE extensions folder and moved E!2antispam.xml in it. Restart sbs console and the error will be gone. if fact the entire line about spam filtering is gone. Hopefully a sbs 2011 patch will fix this problem. when it does, it should ad a new E12antispam.xml and the spam filtering will be restored. In the meantime, this will get your security status back to green.
- Proposed As Answer by Dilip H, SantMicrosoft Employee Friday, April 29, 2011 10:28 PM
Tuesday, May 17, 2011 5:27 AM
is it recommended to install FFPE 2010 on SBS 2011?
i am in a similar situation. i had FFPE installed on my earlier SBS and now am contemplating if i should go that route again.
FFPE did a good job but it also added load to the server. so far the integrated anti spam in exchange is doing well as well.
so, what to do?
You can either be part of the problem or be part of the solution.
Wednesday, May 02, 2012 4:08 PM
GaryD9, on this thread:
posted a detailed answer which worked for me, as far as the Console alert goes. It doesn't fix the emailed reports. I'll copy it here incase that thread becomes unavailable:
$(Get-TransportAgent "Content Filter Agent").Enabled
The fix can be as simple as changing the line to:
$(Get-TransportAgent "FSE Content Filter Agent").Enabled
(just inserting "FSE " in the front of the agent name)
It should be noted that you can't edit this file unless you open it from Notepad after right clicking on the shortcut for Notepad and selecting "Run as Administrator". Also, you won't see any changes until you close and re-open the Windows SBS Console.
I'm not sure if that applies to SBS 2011 or if Forefront 2010 will work on SBS 2011, but this may solve the console reporting error. It will NOT (sadly) solve the errors reported by the emailed status reports. It also will not solve issues with warnings about the engines not having updated in the last 5 days which is perfectly normal for the Cloudmark and worm engines. I have a question posted on that issue here:
which, so far, has not attracted any reasonable answers.
Best of luck and keep us posted? Thanks!