A Gotcha to beware of with Server 2008 and Exchange

Hi,

This came up recently on a forum and I thought it worth mentioning.

“Since moving to win2008 DC/GCs (and ex2007sp1 on win2008 as well) all of a sudden we have been unable to manually create rpc/http profiles with Lookout 2007. Automatically created profiles using autodiscover could still be created, however. After much testing with Microsoft we finally realized the problem was simply that we were so used to typing in the simple server name (netbios name) rather than the fqdn in outlook setup. Just an fyi to those of you moving to a pure win2008 environment.”

The MSFT response:

After investigation, I was able to reproduce the behavior where Outlook 2007 is unable to connect to a pure Windows 2008 Exchange 2007 SP1 environment using NetBios, but is, if using FQDN when setting up a manual RPC/HTTPS profile.

Now that I have a repro, I?m investigating further to see if this is expected behavior and if so, why is Outlook 2003 able to connect using NetBios, but Outlook 2007 is not?

The FQDN is the preferred and recommended way of setting up a manual profile.

I?ll let you know when I have additional information.

One update that has been received so far is that it appears to be related to a component of Exchange which is used to talk to the GC……

So all in all, an interesting problem. I’ll try and keep you updated.

Final UPDATE:

Here is the latest info from Microsoft. All in all, this will be solve in RU4.

“I have researched this issue and have some information for you regarding it. There were two bugs that were in Exchange 2007 relating to Windows Server 2008 and our DSProxy component. One of these was the inability to handle Ipv6 appropriately with RPC over HTTP connections; the other caused the symptom you saw with not being able to ?check name? using the netbios name of the mailbox server. Both of these issues are being corrected in the Rollup Update 4 for Exchange Server 2007 SP1. I have tested these changes in my lab and have confirmed that RU4 will resolve your issue.”

Cheers

Nathan