Let's say for example, you have a single Exchange 2003 server in your network. You decide to tansition it to Exchange 2007. You have a small network, less than 75 users so you don't go to all the trouble of setting up an Edge Transport role since you rely on an external provider for message hygiene, spam filtering, etc. So you have a single server running the Mailbox, Hub & Client Access roles.
All seems well, until you notice that you seem to be getting a lot of delivery failures on your outbound messages. Upon investigating, you discover that in the message headers the server name is the internal name of the server, NOT the external FQDN you used in Exchange 2003. Hmmm... that's weird.
If you poke around in Exchange 2007 you'll discover that there is a FQDN field right on the Send Connector property page. Great! Just set the FQDN and you are in business, right? Wrong.
If you do a quick check of the Exchange 2007 help file, you find the following nugget...
If the Send connector is configured on a Hub Transport server that also has the Mailbox server role installed, any value that you specify for the FQDN field is not used. Instead, the FQDN of the server that is displayed by using the Get-ExchangeServer cmdlet is always used.
So you can set the value there or through the Command Shell and Exchange will happily ignore it. Instead, you'll get the Exchange Server name. There are instructions in the help file for removing the Exchange server name from the headers, along with some warnings about how its not recommended. In my case, I just decided to create an external DNS entry, AND reverse DNS entry with the internal name of the server.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment