Nice tool to help you sort out problems accessing Exchange from out on the Internet. For more information see the blog on You Had Me At EHLO.. here and there is a quick presentation on Edge.TechNet.com here . Test EAS with Windows Mobile 5, EAS with Windows Mobile 6 (& autodiscover), OutlookAnywhere...

Quick transport rule to remove the recipient field of an SMTP message header from messages going out across an Edge Transport role server… Not going to win any awards but it’s worth a look if you haven’t tried mucking about with transport rules with Powershell . $Condition = Get-TransportRulePredicate...

Not that I believe you should be, but if you are concerned about the server names and ip addresses that are stamped on outgoing message headers have a look at the following blogs: Removing internal host names and IP addresses from message headers on Exchangepedia Removing internal SMTP headers by Jim...

I’ve heard a couple of queries recently concerning Windows NLB and the CAS\HUB combined role.  The point is that you should use NLB to load balance network traffic and you can therefore effectively de-couple HUB from CAS.  For the Hub Transport server role (since Exchange 2007 SP1) the following...

(**Be warned - this is not an interesting blog...) Nevertheless there might be someone out there that desperately needs to know how to add a carriage return to a disclaimer through powershell...?  I was that person up to about half an hour ago.  The following transport rule adds a disclaimer...

What's good about EdgeSync? It makes design\configuration\administration a lot easier Even if you have to modify the default send connector or add new send connectors you only need to do it once and the topology is pushed out to ADAM on the subscribed Edge Server.  Rather than having to create routes...

No . If you test this scenario then you'll find that Exchange 2007 will select one of the routes and will always deliver messages across that route whenever it can.  The connector is chosen based on the connector name - whichever comes first alphanumerically will be used.  i.e. AA_Connector...

I wrote a series of blogs a while back which might help.. ' Run your own Exchange Server Health Check.... ' If you are considering moving to Exchange 2007 this might be a good time to verify that your source environment is in a good state.  The blogs should not be used in place of the official Exchange...

Couple of things that might be of interest.... An updated version of the Transport Suite was released last week which now includes the 'Microsoft Transporter Suite for Internet Mail' (available for download here ).  This, as described in the readme ,... "..is a new collection of tools that...

Messaging is mission critical for most companies now and high availability is a major focus for any Exchange Server implementation. Exchange Server 2007 gives us some great options to enable us to achieve 'high availability' including LCR, CCR and, in SP1, SCR. ...but this is only really a part of the...

So AD integration with Exchange 2003 was split into 2 components: DSAccess & DSProxy . DSAccess.dll ran inside the System Attendant and was responsible for building a topology of the Domain Controllers available to the Exchange Server (increase diagnostics logging for MSExchangeDSAccess Service...

This article looks good. It’s just been re-released and consolidates several other articles: General troubleshooting for transport issues in Exchange 2000 Server and in Exchange Server 2003 http://support.microsoft.com/kb/257265 The article doesn’t mention ExTRA though. You can use the ‘Microsoft...