Friday 3 April 2009

SBS 2008 – Outlook Anywhere Hanging Outlook

Outlook over HTTPS, now renamed to Outlook Anywhere, is a great feature that we use in-house and at a number of clients.  It basically gives you Exchange connectivity outside of the network without using a VPN.  I use it on my laptop as my primary profile and it means Outlook works whether I’m in the office or not.

After recently deploying SBS 2008 in the office we noticed Outlook would struggle to connect over HTTPS.  Once connected it would generally work without a problem for a number of hours, but it would then become un-responsive and we had to move to OWA while it recovered.  If you left Outlook it would generally recover, although it could take up to an hour.

I raised this with my ever resourceful friends over at microsoft.private.sbsc.windowsserver.sbs and yet again they came back with the right answer.  In our case that was the TCP Chimney Offload problem, as described in this MS article.

Following the above article I found that TCP Chimney Offload was already disabled in the OS, but not on the network card. First of all I replaced the network card drivers that the SBS setup had installed with the correct drivers from HP. Then in the Advanced tap of the network card properties I set ‘Receive Side Scaling’ to disabled.

These two actions together have cured all the problems we were having with Outlook and another hats off to Robert in the newsgroups.

SBS 2008 – Stop Mail Being Marked as Spam in the IMF

The new anti-spam engine in SBS 2008 seems to be doing a good job on one of our customer’s sites.  However, the interface isn’t the greatest and I struggled to find a way to stop a particular email being marked as spam.  My struggle was explained when I raised a post in microsoft.private.sbsc.windowsserver.sbs – you can’t do it through the GUI, you need to use the Exchange shell (EMS).  One note about said shell, always right-click and choose ‘Run as Administrator’, certain commands, including the ones below, don’t work if you run it as a normal user.

Use the following shell command to add sender SMTP addresses to the BypassedSenders list:

Set-ContentFilterConfig -BypassedSenders foo@somedomain.com,foo2@somedomain.com

Use the following command to whitelist the sending domain:

Set-ContentFilterConfig -BypassedSenderDomains somedomain.com,someotherdomain.com

You don’t get any confirmation that the action has been taken, but you also don’t get any error message.  Use the following commands to list which users or domains have been added to the BypassedSenders lists:

Get-contentFilterConfig |fl BypassedSenders
Get-contentFilterConfig |fl BypassedSenderDomains

Thanks to Robert Li in the newsgroups for this info.

Related info:

How to Specify Recipient and Sender Exceptions for Content Filtering
http://technet.microsoft.com/en-us/library/aa995952.aspx

Get-ContentFilterConfig
http://technet.microsoft.com/en-us/library/aa998807.aspx