Wayne88
asked on
Exchange and Outlook Autodiscover service
Hi,
I noticed that some of our Outlook clients are having autodiscover issues like Out of Office not working, global address book is not syncing when the other half of the outlook users are fine.
This is what I noticed that when you go to Outlook 2007, in FILE then INFO....the ones that are able to use OOF and GAL without issues are able to see the external URL which is associated with an SSL ceritifcate. (See attached).
I need help in troubleshooting and solving to why the problematic Outlook clients are not seeing the url REMOTE.DOMAIN.COM that's associated with the SSL certificate and some do. Please be detailed with your answer.
Thank you
OUTLOOK-SCREENSHOTS.docx
I noticed that some of our Outlook clients are having autodiscover issues like Out of Office not working, global address book is not syncing when the other half of the outlook users are fine.
This is what I noticed that when you go to Outlook 2007, in FILE then INFO....the ones that are able to use OOF and GAL without issues are able to see the external URL which is associated with an SSL ceritifcate. (See attached).
I need help in troubleshooting and solving to why the problematic Outlook clients are not seeing the url REMOTE.DOMAIN.COM that's associated with the SSL certificate and some do. Please be detailed with your answer.
Thank you
OUTLOOK-SCREENSHOTS.docx
ASKER
Hi MegaNuk3,
Yes, the Exchange server was patched with SP3 and all Outlook 2007 are running the latest updates. Also yes that all Outlook are running the same version joined to the domain.
Thanks,
Wayne
Yes, the Exchange server was patched with SP3 and all Outlook 2007 are running the latest updates. Also yes that all Outlook are running the same version joined to the domain.
Thanks,
Wayne
are they internal or external?
is your autodiscoveruri configured correctly
have you tried the outlook test email autoconfiguration to see what url the users are looking for to retrieve the info?
is your autodiscoveruri configured correctly
have you tried the outlook test email autoconfiguration to see what url the users are looking for to retrieve the info?
ASKER
can you resolve remote.company.com internally without any ssl errors?
It appears it is using that from the scp setting in Active Directory
It appears it is using that from the scp setting in Active Directory
ASKER
Hi Brota,
When I ping remote.company.com internally I get the server reply with the server's IP address so yes I can.
Thanks.
When I ping remote.company.com internally I get the server reply with the server's IP address so yes I can.
Thanks.
ASKER
Also, I can connect to https://remote.company.com which will direct me to https://remote.company.com/remote internally. I know it is internally because the SSL ports are blocked by the firewall from outside.
I would check and make sure EWS and OAB urls are set correctly
http://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/configuring-exchange-server-2007-web-services-urls.html
Also if you are doing some sort of redirection in IIS with the /remote make sure it is not redirecting the autodiscover to /remote too
http://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/configuring-exchange-server-2007-web-services-urls.html
Also if you are doing some sort of redirection in IIS with the /remote make sure it is not redirecting the autodiscover to /remote too
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for your help Brota and MegaNuk3!
MegaNuk3, you solved it! Thanks again for your help!
MegaNuk3, you solved it! Thanks again for your help!
ASKER
I had the SSL set to IGNORE because during the rollout I didn't have SSL and thus the Outlook clients were prompted for logon each time it was started.
Once it's set back to ACCEPT as instructed and ran the Outlook test was successful.
Once it's set back to ACCEPT as instructed and ran the Outlook test was successful.
Are you running outlook 2007 with the latest updates? Have you compared the Outlook versions of working ones vs. Non working?
Are all the machines domain joined?