Exchange 2013 Autodiscover

1. Test-OutlookWebservices -  to test Autodiscover.

2. Get-ClientAccessServer | FL AutoDiscoverServiceInternalUri - To see Autodiscover URL

3. Set-ClientAccessServer -Identity SERVER -AutoDiscoverServiceInternalUri https://autodiscover.domain.com/Autodiscover/Autodiscover.xml - To set Autodiscover URL

ok

Test-OutlookWebservices comes back with an error --- Unable to find the client access monitoring user

Get-client accessserver returns hosting.domain.local

Seems its not authenticating.

Try : Test-OutlookWebServices -Identity:username@extdomain.com -MailboxCredential:(Get-Credential domain\username)

Regarding the Get-client accessserver - this is wrong. should be mail.domain.com which should resolve to localserver.domain.local. Use the cmdlet i gave you above to correct this.

Make sure you have a DNS entry that points mail.domain.com to Exchange. Do you have more than 1 exchange 2013 server?

If I explain my issue it may become clearer

We have an Exchange 2013 Server that hosts a company's email, they are all External Users, everything works fine except for 2 users who are using Windows XP and Office 2007, both with latest Patches.

Only the XP users have the issue where if they open Outlook they are continually asked for Password, now I believe this is because XP users will only read the The subject Name in the Cert and not the associated SAN's.

so my thought is if I were to change EXPR to be the Subject name of the Cert then they would not be asked for credentials any more.

My worry is if I change that will it cause issues to the users working ok???

When trying the Test autodiscover I got Result Failure

the service Endpoint is pointing to a .local, my domain is a .local domain if that helps shed light on anything?

Are you 100% Office 2007 is fully patched? It will not work without all latest patches.

Please download this tool to check your office - https://www.microsoft.com/en-us/download/details.aspx?id=36852

I have had the exact same issue before with 3 XP computers and I resolved it my filling in the Exchange Proxy settings in Outlook manually and installing the certificate.

However that being said these users should immediately move away from XP and office 2007. It is obsolete and prone to give issues.

For troubleshoot Autodiscover error do the follwing :

Test-OutlookWebServices -Identity:username@extdomain.com -MailboxCredential:(Get-Credential domain\username) | fl >> TestResult.txt

Browse to the directory you ran this command from and open the txt file you created. In that log file you will be able to see why it is failing. Post it here if you need help.

I have attached the .txt file

TestResult.txt

Although I am thinking this may be another issue and not the question I need answering

That error there just shows that the account you are using to test with is not authorised to do that test. Autodiscover is most likley working as you said other users do not have an issue,

I still stick by my answer of checking latest patches for 2007. It will not work without it.

You can also try to manually enter exchange proxy settings. Do you know how?

Ok Just to confirm All latest Patches etc are installed

on the XP Clients msstd: is set to msstd:webmail.domain.co.uk, im think if I could change this to to subject name it will work. these setiings get populated once It connects to exchange I do not put anything in the msstd: part

if I manually change it in Outlook settings it just goes back once restarted

I do not think that will resolve your issue as it is working for other clients.

The msstd : should be msstd:mail.domain.co.uk and this setting comes from Outlook anywhere in Exchange 2013.

Keep this question open another day as there might some1 else who can shed light on this.

Yes but if XP only reads the subject name which is Hosting.domain.co.uk

and mail.domain.co.uk is entered as a Subject Alternate Name then that would cause Password Prompts?

Found Answer myself