How can i change it? Is it the default?

Hi, Below you'll see the default authentication methods configured for the AutodiscoverVDir. You should not change them. [PS] C:\Windows\system32>Get-AutodiscoverVirtualDirectory | fl *auth* InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated, WSSecurity, OAuth} ExternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated, WSSecurity, OAuth} LiveIdNegotiateAuthentication : False WSSecurityAuthentication : True LiveIdBasicAuthentication : False BasicAuthentication : True DigestAuthentication : False WindowsAuthentication : True OAuthAuthentication : True AdfsAuthentication : FalseMartina Miskovic

I have the same thing.

I have the same thing. Then your settings is OK. Do you have any problems, or?Martina Miskovic

Yes when configure outlook client the securty setting is set to anonymous. When I am starting outlook it ask me for a password. To correct the problem when I change it to negotiate, but I don't find the setting on server to correct the autodiscover file that push that setting.

Hi, Not sure what you mean with client security settings is set to anonymous, but I think you should focus on the Authentication settings you have configured for Outlook Anywhere. This is the default settings (Get-OutlookAnywhere | fl *auth*): ExternalClientAuthenticationMethod : Negotiate InternalClientAuthenticationMethod : Ntlm IISAuthenticationMethods : {Basic, Ntlm, Negotiate} Martina Miskovic

If you go in the account information, in the advanced setting. On security tab, the setting on the bottom is set to anonymous.

If you go in the account information, in the advanced setting. On security tab, the setting on the bottom is set to anonymous. Aha Oki. That is not a setting that Exchange configures with Autodiscover.Martina Miskovic

Yes this setting is set by autodiscover. The EXCH provider auth package is set to anonymous for my exch 2013 clients. The EXCH provider auth package is set to none specified for my exch 2010 clients. I have only this problem with exch 2013 clients

I found the cause of the problem. There is support KB for this issue. http://support.microsoft.com/kb/2834139