Exchange 2007 set up using a combination of server.xxx.local and mail.xxx.com - is this normal? If not how can I correct it?
I had an outside consultant come in and help me install Exchange 2007 in our environment. They seem to have used a combination of two different FQDN's to set this up - server.xxx.local and mail.xxx.com. Is this a normal way to set up Exchange 2007?
We had to set up some kind fix to get SSL certificates working correctly since internally it resolves to the .local FQDN. It seems like it would make more sense to have set up Exchange 2007 to only use mail.xxx.com internally AND externally for any name resolution.
For example to access OWA, you go to mail.xxx.com. To set up Outlook Anywhere however you have to use a combination of both server.xxx.local in the Exchange server box and mail.xxx.com in the HTTP box.
From a logical standpoint, I would say he got confused and used two different FQDN's while setting up Exchange 2007. Am I correct, or is this a standard practice way to set up Exchange 2007 and should I leave it alone?
We had to set up some kind fix to get SSL certificates working correctly since internally it resolves to the .local FQDN. It seems like it would make more sense to have set up Exchange 2007 to only use mail.xxx.com internally AND externally for any name resolution.
For example to access OWA, you go to mail.xxx.com. To set up Outlook Anywhere however you have to use a combination of both server.xxx.local in the Exchange server box and mail.xxx.com in the HTTP box.
From a logical standpoint, I would say he got confused and used two different FQDN's while setting up Exchange 2007. Am I correct, or is this a standard practice way to set up Exchange 2007 and should I leave it alone?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Mestha,
Thanks for the detailed breakdown, that is really helpful.
Regarding the Exchange 2007 SSL cert, we used a standard one from Godaddy. It was licensing for the public domain so we had to do some messing around to get that to work for internal Outlook clients so it doesn't prompt them every time asking if the cert is okay.
My primary irritation with this is how Outlook Anywhere works. I'd prefer it if I could put in mail.xxx.com for the Exchange server name instead of server.xxx.local. What setting is it that controls what FQDN is used internally for Outlook to connect to it?
Thanks for the detailed breakdown, that is really helpful.
Regarding the Exchange 2007 SSL cert, we used a standard one from Godaddy. It was licensing for the public domain so we had to do some messing around to get that to work for internal Outlook clients so it doesn't prompt them every time asking if the cert is okay.
My primary irritation with this is how Outlook Anywhere works. I'd prefer it if I could put in mail.xxx.com for the Exchange server name instead of server.xxx.local. What setting is it that controls what FQDN is used internally for Outlook to connect to it?
When it comes to Outlook Anywhere, you cannot change the URL. The server's real internal FQDN will always appear. If you are using Outlook 2007 then Autodiscover will configure Outlook Anywhere for you automatically. If you are using Outlook 2003 then you have to configure manually before you hit next on pure external clients.
A standard SSL certificate would have given you grief - if you switched to a SAN/UC certificate then you would not have had that grief.
Simon.
A standard SSL certificate would have given you grief - if you switched to a SAN/UC certificate then you would not have had that grief.
Simon.
ASKER