Replication Host Names

In Exchange 2007 Service Pack 1, a new feature was introduced that allowed additional redundant networks to be added to a CCR environment for the purposes of log shipping and database seeding. With specific networks dedicated to log shipping and database seeding, the remaining network is dedicated to its task of servicing client communications. Such a configuration avoids situations where the network that is servicing client communications also has to process a large number of transaction logs.

Replication Host Names are an Exchange 2007 SP1 feature that I don't think is used very often or that well known. This is a great article on setting it up from both a Windows 2003 and 2008 perspective.

Via Neil Hobson.

Office 2008 SP1 fixes some Exchange 2007 Problems

Recently a few of the folks I work with that use Macs noticed Entourage 2008 was having trouble using Exchange 2007 Web Services properly (as it advertised it would). I tried it out from home and verified the same thing, that the Out of Office Assistant and Free/Busy lookups didn't go so well. I've been meaning to get around to building an OS X 10.5 virtual machine so I could hook it into my VM environment and do a packet trace to see what was going on, but it seems like I won't need to anymore. Just update your friggin' client to SP1 and EWS works properly. They've also added support for Autodiscover. I haven't had a chance to play yet, but I wonder what kind of lookups and certificate restrictions Entourage has compared to Outlook.

So, moral of the post - problems with Entourage 2008 for Mac and you've got an Exchange 2007 environment? Upgrade your clients to SP1.