SSL Mismatch – Outlook Anywhere

UPDATE: Checked with Exchange 2010, and this also resolves the issue.

Today I was dealing with a customer who was receiving errors in Outlook for autodiscover each time they opened Outlook. This was all after they’d changed their domain name.

I’d run a script I use to alter all of the host names, to check that they were all correct and then spent considerable time hunting around Exchange for this incorrect setting, and eventually found it.

It’s in the OutlookAnywhere settings, rather than in all of the other URL’s my other script alters. Usually, this URL doesn’t change, and so I’d missed it, but as they’d changed their domain name, this also needed alteration.

So, if you get SSL mismatch errors, and you think you’ve changed all of the necessary URL’s, check this one:

get-outlookanywhere | select Identity, ExternalHostName

if the External Host Name is incorrect, then adjust it with this:

get-outlookanywhere | set-outlookanywhere -externalhostname ""

This certainly works with Exchange 2007, I’ve not yet checked it on Exchange 2010, but believe it’s the same cmdlets.

I’ll write up a full blog post this weekend with a list of all of the places that need to be changed, so that it’s all in one place.

Exchange Certificate Cleanup via PowerShell

A short post today, just to find all MS Exchange certificates which have expired, filtered by domain name, and remove them from your exchange server. This should work with Microsoft Exchange 2007 and 2010.

$Domain = read-host "Enter Domain Name to Search for (e.g. webmail.domain.tld)"

Get-ExchangeCertificate | where {$_.NotAfter -lt (get-date) -and $_.Subject -like "*$Domain*"} | Remove-ExchangeCertificate -confirm: $false

Problem connecting MS Outlook 2003 to MS Exchange 2010

I recently came across a problem after migrating a company from Exchange 2003 to Exchange 2010… none of the Outlook 2003 clients would connect to the server once their mailbox had been migrated. Other clients (MS Outlook 2007 and 2010) would work perfectly… so I knew this wasn’t necessarily a server-based problem…

After some digging around I came across this:

Outlook 2003 Exchange 2010 fix

This screenshot is from the advanced settings section of an Exchange connector in Outlook 2003. All that’s needed to be changed here, is to put a tick in the “Encrypt data between Microsoft Office Outlook and Microsoft Exchange Server”. Once you’ve clicked OK, and saved the changes to the profile, Outlook works properly again.