All of my Outlook clients are automatically recieving 'Exchange Proxy Settings' which tell them how to connect using Outlook Anywhere, it appears this is done be the autodiscover service. The only problem is that it is telling clients to use Basic Authentication rather than NTLM (which is set on the server). This causes password prompting galore. How do I get in and change this? I'd also like to change the name of the server to connect to (to prepare for a 2010 migration). I have two 2007 Exchange servers (one Edge) and have two 2010 servers in the mix as well (all roles but edge/um).

Hi,When Outlook 2007 users connect to Exchange by using Outlook Anywhere, the Autodiscover service uses the default service discovery mechanism to find the values for the ExternalHostName and Auth Package parameters of the OutlookAnywhere and OutlookProvider objects in Active Directory. (The OutlookProvider object provides configuration for Outlook 2007 clients.)Outlook Anywhere use EXPR Outlook Provider to get the relevant configuration for Outlook 2007 clients. To change the name of the server, please run set-outlookprovider -identity EXPR -Server servernameFor the authentication issue, please run get-outlookanywhere |fl command in EMS, then post the information on the forum.ThanksAllen

Hi-With regard to auth and endpoint, look at the Set-OutlookAnywhere cmdlet. This exposes everything you need. If you change the endpoint you may also need to tweak the cert config via Set-OutlookProvider.Active Directory, 4th Edition - www.briandesmond.com/ad4/

Here are the results of the get-outlookanywhere | fl command, it appears they are correctly set to NTLM, not sure why my clients are still getting set to basic? ServerName : Server1SSLOffloading : FalseExternalHostname : Server1.comClientAuthenticationMethod : NtlmIISAuthenticationMethods : {Ntlm}MetabasePath : IIS://server1.com/W3SVC/1/ROOT/RpcPath : C:\WINDOWS\System32\RpcProxyServer : server1AdminDisplayName :ExchangeVersion : 0.1 (8.0.535.0)Name : Server1.comDistinguishedName : CN=server1.com,CN=HTTP,CN=Protocols,CN=MID AS,CN=Servers,CN=Exchange Administrative Group (FY DIBOHF23SPDLT),CN=Administrative Groups,CN=com,C N=Microsoft Exchange,CN=Services,CN=Configuration, DC=comIdentity : server1/server1.comGuid : 71d2ee07-2dd1-41b3-9f20-4568ecf836e0ObjectCategory : com/Configuration/Schema/ms-Exch-Rpc-Htt p-Virtual-DirectoryObjectClass : {top, msExchVirtualDirectory, msExchRpcHttpVirtual Directory}WhenChanged : 1/25/2010 12:48:12 PMWhenCreated : 5/22/2009 8:45:35 AMOriginatingServer : dc.comIsValid : True ServerName : server2SSLOffloading : FalseExternalHostname : mail.comClientAuthenticationMethod : NtlmIISAuthenticationMethods : {Ntlm}MetabasePath : IIS://server2.com/W3SVC/1/ROOT/RpcPath :Server : server2AdminDisplayName :ExchangeVersion : 0.10 (14.0.100.0)Name : Rpc (Default Web Site)DistinguishedName : CN=Rpc (Default Web Site),CN=HTTP,CN=Protocols,CN= server2,CN=Servers,CN=Exchange Administrative Group (FY DIBOHF23SPDLT),CN=Administrative Groups,CN=com,C N=Microsoft Exchange,CN=Services,CN=Configuration, DC=comIdentity : server2\Rpc (Default Web Site)Guid : 16e36e2d-8758-4bae-ac12-d526a6776a2bObjectCategory : com/Configuration/Schema/ms-Exch-Rpc-Htt p-Virtual-DirectoryObjectClass : {top, msExchVirtualDirectory, msExchRpcHttpVirtual Directory}WhenChanged : 1/14/2010 3:52:18 PMWhenCreated : 1/14/2010 11:49:16 AMOriginatingServer : dc.comIsValid : True ServerName : server3SSLOffloading : FalseExternalHostname : mail.comClientAuthenticationMethod : NtlmIISAuthenticationMethods : {Ntlm}MetabasePath : IIS://server3.com/W3SVC/1/ROOT/RpcPath :Server : server3AdminDisplayName :ExchangeVersion : 0.10 (14.0.100.0)Name : Rpc (Default Web Site)DistinguishedName : CN=Rpc (Default Web Site),CN=HTTP,CN=Protocols,CN= server3,CN=Servers,CN=Exchange Administrative Grou p (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=US URF,CN=Microsoft Exchange,CN=Services,CN=Configura tion,DC=comIdentity : server3\Rpc (Default Web Site)Guid : 309392c3-a843-43ff-b7b1-afe713cb837fObjectCategory : com/Configuration/Schema/ms-Exch-Rpc-Htt p-Virtual-DirectoryObjectClass : {top, msExchVirtualDirectory, msExchRpcHttpVirtual Directory}WhenChanged : 1/14/2010 3:51:50 PMWhenCreated : 1/14/2010 3:51:28 PMOriginatingServer : dc.comIsValid : True

Hi,Thanks for your information. From the information, there is no issue about the configuration for the Outlook Anywhere.Now please press Ctrl+right click the Outlook icon in the System, select Test E-mail AutoConfiguration, click Test button, please check the Auth Package value under Results tab for Exchange HTTP protocol. Is it NTLM or Unspecified?If it's Unspecified, that indicates someting is prevented from determining the proper authentication method, then default falls back to Basic Authentication.So you need to run get-Outlookprovider -identity EXPR |fl command, check whether the Server parameter is null. This parameter should be set to NULL. When it’s manually configured to something other than NULL, the Service Discovery API responsible for providing the Autodiscover service with the necessary values including that for authentication is prevented from determining the proper authentication method.Thus, you need to set-outlookprovider -identity EXPR -server $null, then check this issue again.http://technet.microsoft.com/en-us/library/cc411324(EXCHG.80).aspxThanksAllen

I think you're looking for the Set-AutodiscoverVirtualDirectory cmdlet. You might also check out Set-ClientAccessServer AutodiscoverServiceInternalUri.-- Ed Crowley MVP"There are seldom good technological solutions to behavioral problems.". "sgrigg" wrote in message news:e63afe30-c3b6-4e26-97dd-2bd33b42b4ee...All of my Outlook clients are automatically recieving 'Exchange Proxy Settings' which tell them how to connect using Outlook Anywhere, it appears this is done be the autodiscover service. The only problem is that it is telling clients to use Basic Authentication rather than NTLM (which is set on the server). This causes password prompting galore. How do I get in and change this? I'd also like to change the name of the server to connect to (to prepare for a 2010 migration). I have two 2007 Exchange servers (one Edge) and have two 2010 servers in the mix as well (all roles but edge/um). Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."