Exchange 2003, Exchange 2007, Exchange 2010

What about Legacy / Coexistence for OWA?

  Hi After reading and answering in MS forum I can tell you all that this is a very common question that need to be clarified. Before Exchange 2010 was released there was a built-in function that handled the co-existence for OWA. A little background check, Exchange 2003 and 2007 could co-existence by pointing to the Exchange 2007 CAS server(s) and use /exchange. In Exchange 2010 this function is removed and replaced by “Legacy”. What to think about when you are planning for a co-existence? You need to add the…

Continue Reading

Exchange 2007, Exchange 2010

How to update legacy email address policys

  This is an easy step-by-step guide how to upgrade the legacy policies when transition from Exchange 2000 or 2003 to 2007 or 2010 there’s a need for upgrading the email address policies. Also remember, this is example without any guarantee! Don’t forget! Before running these commands make sure that you remove mailbox management policy, or else you will get problems. Get-EmailAddressPolicy | where { $_.RecipientFilterType -eq “Legacy” } | Set-EmailAddressPolicy –IncludedRecipients AllRecipients Set-AddressList “All Contacts” -IncludedRecipients MailContacts Set-AddressList “All Groups” -IncludedRecipients MailGroups Set-AddressList “All Users” -IncludedRecipients MailboxUsers Set-AddressList “Public…

Continue Reading

Exchange 2007, Exchange 2010

Relay Connector

Many times the question comes up in forums how to create a relay connector that works just like it did in Exchange 2003. At that time it was like…. If the IP address was in the list, that IP was able to relay no matter what. In Exchange 2007/2010 it’s not working that way.. Now we need to create a receive connector, give it a proper name (like Relay Connector) and also set an extra security setting on it. Here are the commands that I usually use to create the…

Continue Reading

Exchange 2003, Exchange 2007, Exchange 2010

Friday Tip #3 – DNS/Spamcheck

  This is the third Friday tip and maybe the best of them all J To have a complete check on the customers external DNS when doing a mail project is maybe the best thing to do. Very often I see that “everything” looks OK but when checking for PTR records they doesn’t exists. This can be a problem, some receivers doesn’t accept the mail if the PTR records doesn’t match the mx record and the banner on the server. With this link below you can search for the domain…

Continue Reading

Exchange 2007

Entourage Issues with Exchange 2007 on Windows 2008

  Issue Using Entourage for Mac (2004 or 2008) while connecting to an Exchange 2007 mailbox on a Windows 2008 Server, user cannot download any e-mail message which has a plus sign in the subject line, like ‘Mail + Issue’. Cause Entourage’s request to download this e-mail message goes thru IIS 7 on Windows 2008 Server, which is configured (by default) to deny ‘double escape sequences’ in any HTTP request and thus it rejects the request with a ‘404.11’ error. Resolution As Entourage talks to ‘Exchange’ virtual directory (for mailbox…

Continue Reading

Exchange 2007, Exchange 2010

Recover failed Exchange 2007/2010 server installation

A time ago I had a little problem with an Exchange 2007 (SP1) installation. The server I was using was prepared with Windows 2008 R2 Standard and I was told that this should be supported if Exchange 2007 is using SP2. Well, with that said I could install Exchange 2007 including SP1 if I used Compatibility mode. But when I should update it to SP2 it wouldn’t run the installation even if I used the Compatibility mode. The only option that was available for me was to uninstall Exchange 2007,…

Continue Reading

Exchange 2003, Exchange 2007

OWA/ActiveSync with Exchange 2007 coexist with Exchange 2003

  In this scenario when have a single Exchange 2003 standard server installed and installed a new server with Exchange 2007 standard with CAS/HUB/MBX role (multi-role server). Our problem was that we had too many users that used OWA and ActiveSync so we couldn’t be without this function. I this case we had 3 different solutions to choose between. 1. Use two different IP addresses; one for the Exchange 2003 OWA/AS and one for the Exchange 2007 OWA/AS 2. Use a front-end firewall like ISA server or something else to…

Continue Reading

Exchange 2003, Exchange 2007

Can’t mount Public Folders

For a couple of months ago i had a really hard problem while demoting an old Exchange 2003 after a transition to Exchange 2007. I couldn’t uninstall it and had to do it the hard way with disable services, delete them from registry and delete files etc. After the operation the Exchange 2007 server couldn’t mount the Public Folder database store. But found a solution well hidden on a forum and I want to share it with you J it’s kind of copy and paste on this. Open adsiedit.msc Select…

Continue Reading

Exchange 2007

Receive Connector; Create, manage and troubleshoot

Some companies do not like the idea of displaying the server name in SMTP connections. We can change the banner information used by a Receive Connector using the cmdlet. Set-ReceiveConnector ‘<Connector Name>’ -Banner “220 Mail Server” We can control the number of protocol errors in a single session. The default value is 5, to configure it to 2 we can use the following cmdlet: Set-ReceiveConnector ‘<Connector Name>’ -MaxProtocolErrors 2 When you suspect you have a problem with the receive connector it’s a good idea to start the verbose logging and…

Continue Reading