Hi All, Recently upgraded SBS 2003 w/ Exchange 2003 to SBS 2008 w/ Exchange 2007. Everything went smoothly, except for these issues that have popped up: The main problem - a login box pops up when a user launches outlook 2007 / 2010. Once details are entered, it works great until outlook is closed and started again - 'save credentials' doesn't work. Offline address book no longer works - 0x8004010F - The operation failed, An object could not be found . Out of office assitant doesn't work - Your automatic reply settings cannot be displayed because the server is currently unavailable. Try again later. Autodiscovery no longer working: http://img715.imageshack.us/img715/4540/autodiscoveryoutlook.png -- running the autodiscovery test from a outlook 2010 client from within the corporate network http://img262.imageshack.us/img262/9342/autodiscoveryxchange.png -- running the autodiscovery test from Exchange 2007 Console http://img210.imageshack.us/img210/198/autodiscovery.png -- Loading the autodiscovery URL from outside and inside the corporate network returns this - so I know it works, yet outlook / exchange can't see it and all the tests 'Fail' ? I've read around a lot.. and there seem to be many possible causes for this problem - everything ranging from DNS to Certificates. Where do I start with troubleshooting this?

You shouldn't get an authentication prompt at all if the client is a member of the same domain as Exchange. Was the server configured using the wizards? How exactly did you do the upgrade? New domain or a migration? Has the SSL certificate been changed for a commercial one? Almost certainly most of this is related, autodiscover and Out of Office are linked to the availability service. When one of those fails the other usually does as well. The error code for the OAB means cannot find. The usual reason for that is the OAB is configured to use public folders but there is no public folder store. However without knowing exactly how the upgrade was done, it is hard to say much more. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources

Hi, Please check below thinks...... 1. The main problem - a login box pops up when a user launches outlook 2007 / 2010. Once details are entered, it works great until outlook is closed and started again - 'save credentials' doesn't work. ------Check the certificate for client access server and make sure that host entry for cliect access should be created.. 2. Offline address book no longer works - 0x8004010F - The operation failed, An object could not be found . 3. Out of office assitant doesn't work - Your automatic reply settings cannot be displayed because the server is currently unavailable. Try again later. 4. Autodiscovery no longer working: --------for above Create the hots record for client access server on DNS and wait for replication its should be work. Sachin Hodge Exchange server admin

You shouldn't get an authentication prompt at all if the client is a member of the same domain as Exchange. Was the server configured using the wizards? How exactly did you do the upgrade? New domain or a migration? Has the SSL certificate been changed for a commercial one? Almost certainly most of this is related, autodiscover and Out of Office are linked to the availability service. When one of those fails the other usually does as well. The error code for the OAB means cannot find. The usual reason for that is the OAB is configured to use public folders but there is no public folder store. However without knowing exactly how the upgrade was done, it is hard to say much more. Simon. Simon Butler, Exchange MVP Blog | Exchange Resources Hello Simon, Yeah the client is part of the domain (and is located in the corporate network), so there should indeed be no prompts. There are no prompts for credentials on outlook 2003 clients - only 2007 and 2010 (which use Autodiscovery etc) so I'm inclined to believe that all these issues are intertwined somehow. Was the server configured using wizards - No New Domain or a Migration - Migration (using answer file) SSL Cert - Has not been changed - is the self signed/generated one. I have checked that the Subject Alternative Name in the certificate contains "<netbiosName>.<domain>.local, remote.<topLevelDomain>, <topLevelDomain> - is this correct? Also I've noticed that there are multiple certificates for the same domain (remote.<topLevelDomain> and (<netbiosName>.<domain>.local in IIS manager - is this normal?) Hope that helps us figure out what is wrong.

Hi, ------Check the certificate for client access server and make sure that host entry for cliect access should be created.. --------for above Create the hots record for client access server on DNS and wait for replication its should be work. Sachin Hodge Exchange server admin Hi Sachin, When you say I should check the certificate for the CAS server and make sure the host entry is created, what exactly do you mean? What area specifically in the certificate should I be looking at? And when you say I should create the host record, where should the host record point to? Do you mean the autodiscovery URL? If so, please see this screenshot - the autodiscovery URL is indeed 'visible' both from within and outside the corporate network, however the exchange test fails! (See Screenshot of Exchange autodiscovery test )

I would suggest that you start by running through the wizards in the management console. This will ensure that everything is configured correctly. After doing so, if things are still not working as they should, run the Fix My Network wizard from the management console. I would also download and install the SBS 2008 BPA, which can flag issues. SSL certificate ideally should be changed to a commercial certificate. The self signed certificate can cause problems. However if you are using Outlook 2007 or higher and it was certificate related it would generate a certificate prompt. Multiple certificates shouldn't be in place, but I wouldn't touch them for the time being. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources

Hi, The main problem - a login box pops up when a user launches outlook 2007 / 2010. Once details are entered, it works great until outlook is closed and started again - 'save credentials' doesn't work. Please try to create a new autodiscover virtual directory and test if the issue persists: Open EMS, type: Remove-AutoDiscoverVirtualDirectory -Identity "CasServer\autodiscover(autodiscover.contoso.com)" New-AutoDiscoverVirtualDirectory Then restart exchange server when it is possible.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Thanks Gen Lin-MSFT

Hi, My issue is still not fixed. I have added an A record in my forward lookup zone and this still hasn't fixed the issue. Gen Lin, that command doesn't work for me - I realise I need to modify it to fit my server, but my setup is like this: http://img340.imageshack.us/img340/7741/72487490.png How do I re-write that command so it removes this autodiscovery directory and re-create it properly?Thanks

I think I'm getting closer to the problem. When I go to add an outlook exchange account, it tries to autoconfigure itself - it asks me for a username and password. If I enter enter my username and password, the login box repeats almost 15 times, and then on the 16th of so try, it just goes straight through as if it automagically found the autoconfigure file. I think what's happening is that it's using "guess smart", wehre it tries a range of different URLs to get to the xml file: 1. autodiscover.domain.com <fails 5 times, incorrect password, move on to next guess smart autodiscover url> 2. domain.com/autodiscover.xml <fails 5 times, incorrect password, move on to next guess smart autodiscover url> 3. domain.com/autodiscover/autodiscover.xml <fails 5 times, incorrect password, move on to next guess smart autodiscover url> 4. domain.com/autodiscover/ <enter password, authentication succeeded, autoconfiguration completed, account added> And my server is responding to ALL those requests, even though it shouldn't. So to recap, there's nothing wrong with the autoconfigure itself, it's outlook trying out a million How can I fix this? Asides from the obvious solution (moving the autodiscover directory to autodiscover.domain.com)

Was the client on the same domain as the Exchange server? If so, then it shouldn't be doing a full autodiscover, as the information comes from the domain. You need to verify where domain.com resolves to. With AD, if your WINDOWS domain is domain.com, then domain.com will resolve to a domain controller. However if it resolves to an external host, then that can cause problems as well. Have you been through the wizards to ensure the server is configured correctly? Have you run the SBS BPA against the system to ensure that nothing is flagged? Simon.Simon Butler, Exchange MVP Blog | Exchange Resources

Hiya, I've run both the Exchange BPA and SBS 2008 BPA and it's come up with a bunch of errors / warnings.. I can't see anything that would directly cause this issue, but this is the first time I've tackled and issue of thsi magnitude in SBS 2008 so I will try to fix these over the next week and see if that fixes the problems. Will post back with results. Thanks

Hi, I've fixed my issue - one of the things the SBS 2008 BPA reported was that I was running on Exchange SP1. Installed SP3, and the issue disappeared instantly. OFA & OAB work great now, and as does the autodiscover service. However, the exchange test-outlookwebaccess | fl is still showing the same thing: http://img262.imageshack.us/img262/9342/autodiscoveryxchange.png Internally, autodiscover works great. I'm not having much luck setting up outlook anywhere, but that's a problem for another day.