EDIT 10/4/2007: Since this post has been published, we have updated the Exchange 2007 Autodiscover Service whitepaper to include this information. Please consult the whitepaper for most up-to-date ...
Updated Jul 01, 2019
Version 2.0
Blog Post
2 MIN READ
Outlook 2007 can now use DNS SRV records to find the location of the Exchange Autodiscover Service
Hi all,
Wondering if anyone would be prepared to help me with an issue we are having. We are a subsiduary of a larger company who has an e-mail domain of "company.com" (not real obviously). Our e-mail domain is "subsiduary.com". We have our own separate AD domain and Exchange 2007 server and all our users are configured with a primary (reply) address of user@company.com and secondary addresses of user@subsiduary.com. Any e-mail sent to us are sent to the company.com mail servers and then forwarded on to our subsiduary.com addresses. If we reply to e-mails they are stamped with user@company.com. All users have Outlook 2007. We have a Thawte certificate installed on the Exchange 2007 server which is registered for www.portal.com (not real again), this certificate is also used for many other uses and my boss has told me he doesn't want to buy another one. I have set up all the virtual directories both internal and external to point to www.portal.com and created the necessary DNS entries to resolve these to the CAS server. I've also set the internal URI on the CAS (why can't we set an external one in the same way rather than letting Outlook generate it's own?), and I've enabled the certificate for the services required.
The issue we are having is that our users keep getting certificate prompts, especially when they are on the outside of our network. It would appear Outlook is trying to resolve the autodiscovery URL to addresses involving company.com, unfortunately, I am not able to add DNS entries for our server to these DNS zones as we do not own them and the parent company has said no way.
Is there anyway of changing the way Outlook handles autodiscovery and specifying what domain should be used in the autodiscovery process. Or, does anyone have any other ideas how we might get round this problem?
I tried logging a support call with Microsoft in Australia, but they were not interested since we run our environment on VMware ESX Servers. Yes, I know it is not supported but this issue is hardly caused by the Virtual Infrastructure, plus we can't be the only people in the world who work in this way.
I am finding autodiscover a real step back from Exchange 2003 which just worked perfectly without any hassle.
Any assistance would be greatly appreciated.
Regards,
Richard
Wondering if anyone would be prepared to help me with an issue we are having. We are a subsiduary of a larger company who has an e-mail domain of "company.com" (not real obviously). Our e-mail domain is "subsiduary.com". We have our own separate AD domain and Exchange 2007 server and all our users are configured with a primary (reply) address of user@company.com and secondary addresses of user@subsiduary.com. Any e-mail sent to us are sent to the company.com mail servers and then forwarded on to our subsiduary.com addresses. If we reply to e-mails they are stamped with user@company.com. All users have Outlook 2007. We have a Thawte certificate installed on the Exchange 2007 server which is registered for www.portal.com (not real again), this certificate is also used for many other uses and my boss has told me he doesn't want to buy another one. I have set up all the virtual directories both internal and external to point to www.portal.com and created the necessary DNS entries to resolve these to the CAS server. I've also set the internal URI on the CAS (why can't we set an external one in the same way rather than letting Outlook generate it's own?), and I've enabled the certificate for the services required.
The issue we are having is that our users keep getting certificate prompts, especially when they are on the outside of our network. It would appear Outlook is trying to resolve the autodiscovery URL to addresses involving company.com, unfortunately, I am not able to add DNS entries for our server to these DNS zones as we do not own them and the parent company has said no way.
Is there anyway of changing the way Outlook handles autodiscovery and specifying what domain should be used in the autodiscovery process. Or, does anyone have any other ideas how we might get round this problem?
I tried logging a support call with Microsoft in Australia, but they were not interested since we run our environment on VMware ESX Servers. Yes, I know it is not supported but this issue is hardly caused by the Virtual Infrastructure, plus we can't be the only people in the world who work in this way.
I am finding autodiscover a real step back from Exchange 2003 which just worked perfectly without any hassle.
Any assistance would be greatly appreciated.
Regards,
Richard