exchange 2007 autodiscover fails to connect

Hi all,
      Looking for some help with exchange 2007 autodiscover. clients not able to connect via Outlook Anywhere. I notice that it keeps changing to the local "internal" hostname.  I'm sure it has something to do with the autodiscovery but I have yet to find the issue.

 
 

- Here are the results from testexchangeconnectivity.com:

ExRCA is attempting to test Autodiscover for josh.williams@greshamchamber.org.
       Autodiscover was tested successfully.
       
      Test Steps
       
      Attempting each method of contacting the Autodiscover service.
       The Autodiscover service was tested successfully.
       
      Test Steps
       
      Attempting to test potential Autodiscover URL https://greshamchamber.org/AutoDiscover/AutoDiscover.xml
       Testing of this potential Autodiscover URL failed.
       
      Test Steps
      Attempting to test potential Autodiscover URL https://autodiscover.greshamchamber.org/AutoDiscover/AutoDiscover.xml
       Testing of this potential Autodiscover URL failed.
       
      Test Steps
      Attempting to contact the Autodiscover service using the HTTP redirect method.
       The attempt to contact Autodiscover using the HTTP Redirect method failed.
       
      Test Steps
      Attempting to contact the Autodiscover service using the DNS SRV redirect method.
       ExRCA successfully contacted the Autodiscover service using the DNS SRV redirect method.
       
      Test Steps
       
      Attempting to locate SRV record _autodiscover._tcp.greshamchamber.org in DNS.
       The Autodiscover SRV record was successfully retrieved from DNS.
       
      Additional Details
       The Service Location (SRV) record lookup returned host exchange.greshamchamber.org.
      Attempting to test potential Autodiscover URL https://exchange.greshamchamber.org/Autodiscover/Autodiscover.xml
       Testing of the Autodiscover URL was successful.
       
      Test Steps
       
      Attempting to resolve the host name exchange.greshamchamber.org in DNS.
       The host name resolved successfully.
       
      Additional Details
       IP addresses returned: 173.11.26.174
      Testing TCP port 443 on host exchange.greshamchamber.org to ensure it's listening and open.
       The port was opened successfully.
      Testing the SSL certificate to make sure it's valid.
       The certificate passed all validation requirements.
       
      Test Steps
       
      ExRCA is attempting to obtain the SSL certificate from remote server exchange.greshamchamber.org on port 443.
       ExRCA successfully obtained the remote SSL certificate.
       
      Additional Details
      Validating the certificate name.
       The certificate name was validated successfully.
       
      Additional Details
      Certificate trust is being validated.
       The certificate is trusted and all certificates are present in the chain.
       
      Test Steps
       
      ExRCA is attempting to build certificate chains for certificate CN=greshamchamber.org, OU=Domain Control Validated, O=greshamchamber.org.
       One or more certificate chains were constructed successfully.
       
      Additional Details
      Analyzing the certificate chains for compatibility problems with versions of Windows.
       Potential compatibility problems were identified with some versions of Windows.
       
      Additional Details
       ExRCA can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature isn't enabled.
      Testing the certificate date to confirm the certificate is valid.
       Date validation passed. The certificate hasn't expired.
       
      Additional Details
       The certificate is valid. NotBefore = 8/31/2011 5:29:01 PM, NotAfter = 8/31/2012 5:29:01 PM
      Checking the IIS configuration for client certificate authentication.
       Client certificate authentication wasn't detected.
       
      Additional Details
       Accept/Require Client Certificates isn't configured.
      Attempting to send an Autodiscover POST request to potential Autodiscover URLs.
       ExRCA successfully retrieved Autodiscover settings by sending an Autodiscover POST.
       
      Test Steps
       
      ExRCA is attempting to retrieve an XML Autodiscover response from URL https://exchange.greshamchamber.org/Autodiscover/Autodiscover.xml for user josh.williams@greshamchamber.org.
       The Autodiscover XML response was successfully retrieved.
       
      Additional Details
       Autodiscover Account Settings
XML response:
<?xml version="1.0"?>
<Autodiscover xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
<Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a">
<User>
<DisplayName>Josh Williams</DisplayName>
<LegacyDN>/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=Josh.Williams</LegacyDN>
<DeploymentId>4af3e138-15a7-448d-94cb-084cce514a41</DeploymentId>
</User>
<Account>
<AccountType>email</AccountType>
<Action>settings</Action>
<Protocol>
<Type>EXCH</Type>
<Server>GACOC.greshamchamber.local</Server>
<ServerDN>/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=GACOC</ServerDN>
<ServerVersion>720180F0</ServerVersion>
<MdbDN>/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=GACOC/cn=Microsoft Private MDB</MdbDN>
<ASUrl>https://exchange.greshamchamber.org/Ews/Exchange.asmx</ASUrl>
<OOFUrl>https://exchange.greshamchamber.org/Ews/Exchange.asmx</OOFUrl>
<OABUrl>https://exchange.greshamchamber.org/Oab/ec002968-2a22-4808-bb52-c0280ee0e400/</OABUrl>
<UMUrl>https://remote.greshamchamber.org/UnifiedMessaging/Service.asmx</UMUrl>
<Port>0</Port>
<DirectoryPort>0</DirectoryPort>
<ReferralPort>0</ReferralPort>
<PublicFolderServer>GACOC.greshamchamber.local</PublicFolderServer>
<AD>GACOC.greshamchamber.local</AD>
<EwsUrl>https://exchange.greshamchamber.org/Ews/Exchange.asmx</EwsUrl>
</Protocol>
<Protocol>
<Type>EXPR</Type>
<Server>exchange.greshamchamber.org</Server>
<ASUrl>https://exchange.greshamchamber.org/Ews/Exchange.asmx</ASUrl>
<OOFUrl>https://exchange.greshamchamber.org/Ews/Exchange.asmx</OOFUrl>
<OABUrl>https://exchange.greshamchamber.org/Oab/ec002968-2a22-4808-bb52-c0280ee0e400/</OABUrl>
<UMUrl>https://remote.greshamchamber.org/UnifiedMessaging/Service.asmx</UMUrl>
<Port>0</Port>
<DirectoryPort>0</DirectoryPort>
<ReferralPort>0</ReferralPort>
<SSL>On</SSL>
<AuthPackage>Ntlm</AuthPackage>
<EwsUrl>https://exchange.greshamchamber.org/Ews/Exchange.asmx</EwsUrl>
</Protocol>
<Protocol>
<Type>WEB</Type>
<Port>0</Port>
<DirectoryPort>0</DirectoryPort>
<ReferralPort>0</ReferralPort>
<External>
<OWAUrl AuthenticationMethod="Fba">https://exchange.greshamchamber.org/owa/</OWAUrl>
<Protocol>
<Type>EXPR</Type>
<ASUrl>https://exchange.greshamchamber.org/Ews/Exchange.asmx</ASUrl>
</Protocol>
</External>
<Internal>
<OWAUrl AuthenticationMethod="Basic, Fba">https://gacoc.greshamchamber.local/owa/</OWAUrl>
<Protocol>
<Type>EXCH</Type>
<ASUrl>https://exchange.greshamchamber.org/Ews/Exchange.asmx</ASUrl>
</Protocol>
</Internal>
</Protocol>
</Account>
</Response>
</Autodiscover>

image1.jpg
image2.jpg
definitivellcAsked:
Who is Participating?
 
Madan SharmaConsultantCommented:
Your Auto discover Settings are correct.
I believe exchange server name will remain same either you are in office network of out of office. How are you configuring you outlook for out side users manually or automatically. If you are using autodiscover then it should work in both networks inside office and outside networks. But if you are configuring it then use the following settings
Exchange Server Name:= gacoc.greshamchamber.local (doesn't matter your inside office network or outside office)
User Name :- User Display Name
Click on more settings:-
Goto Connections tab check outlook anywhere click on exchange proxy settings
in https url put :- exchange.greshamchamber.org
check connect using SSL and check only connect to proxy servers that have this principal name in their certificate and enter this value:- msstd:greshamchamber.org
check both on fast and slow network choose authentication type as Basic Authentication
ok and apply ok and check if this not works then once change the msstd value to exchange.greshamchamber.org

if the above procedure doesn't work then once test your server on testexchangeconnectivity.com for outlook anywhere test it will show you the exact error where the issue is.
hop it will be helpful for you.
0
 
endital1097Commented:
autodiscover is retrieving your settings successfully
the settings it pulls for Outlook Anywhere are
<Type>EXPR</Type>
<Server>exchange.greshamchamber.org</Server>
<ASUrl>https://exchange.greshamchamber.org/Ews/Exchange.asmx</ASUrl>
<OOFUrl>https://exchange.greshamchamber.org/Ews/Exchange.asmx</OOFUrl>
<OABUrl>https://exchange.greshamchamber.org/Oab/ec002968-2a22-4808-bb52-c0280ee0e400/</OABUrl>
<UMUrl>https://remote.greshamchamber.org/UnifiedMessaging/Service.asmx</UMUrl>
<Port>0</Port>
<DirectoryPort>0</DirectoryPort>
<ReferralPort>0</ReferralPort>
<SSL>On</SSL>
<AuthPackage>Ntlm</AuthPackage>
<EwsUrl>https://exchange.greshamchamber.org/Ews/Exchange.asmx</EwsUrl>

So based on this response your external hostname is exchange.greshamchamber.org
your certificate subject name is just greshamchamber.org
so you need to set your outlook provider
Set-OutlookProvider EXPR -CertPrincipalName msstd:greshamchamber.org
0
 
definitivellcAuthor Commented:
Thank you for your response I have made the change you said:

Name                Server              CertPrincipalName   TTL
----                ------              -----------------   ---
EXCH                                                        1
EXPR                GACOC               msstd:greshamcha... 1
WEB                                                         1

but no change to outlook. still can not connect while out-of-office
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
definitivellcAuthor Commented:
Testing RPC/HTTP connectivity.
       The RPC/HTTP test completed successfully.
       
      Test Steps
       
      ExRCA is attempting to test Autodiscover for josh.williams@greshamchamber.org.
       Autodiscover was tested successfully.
       
      Test Steps
       
      Attempting each method of contacting the Autodiscover service.
       The Autodiscover service was tested successfully.
       
      Test Steps
       
      Attempting to test potential Autodiscover URL https://greshamchamber.org/AutoDiscover/AutoDiscover.xml
       Testing of this potential Autodiscover URL failed.
       
      Test Steps
      Attempting to test potential Autodiscover URL https://autodiscover.greshamchamber.org/AutoDiscover/AutoDiscover.xml
       Testing of this potential Autodiscover URL failed.
       
      Test Steps
      Attempting to contact the Autodiscover service using the HTTP redirect method.
       The attempt to contact Autodiscover using the HTTP Redirect method failed.
       
      Test Steps
      Attempting to contact the Autodiscover service using the DNS SRV redirect method.
       ExRCA successfully contacted the Autodiscover service using the DNS SRV redirect method.
       
      Test Steps
       
      Attempting to locate SRV record _autodiscover._tcp.greshamchamber.org in DNS.
       The Autodiscover SRV record was successfully retrieved from DNS.
       
      Additional Details
       The Service Location (SRV) record lookup returned host exchange.greshamchamber.org.
      Attempting to test potential Autodiscover URL https://exchange.greshamchamber.org/Autodiscover/Autodiscover.xml
       Testing of the Autodiscover URL was successful.
       
      Test Steps
       
      Attempting to resolve the host name exchange.greshamchamber.org in DNS.
       The host name resolved successfully.
       
      Additional Details
       IP addresses returned: 173.11.26.174
      Testing TCP port 443 on host exchange.greshamchamber.org to ensure it's listening and open.
       The port was opened successfully.
      Testing the SSL certificate to make sure it's valid.
       The certificate passed all validation requirements.
       
      Test Steps
       
      ExRCA is attempting to obtain the SSL certificate from remote server exchange.greshamchamber.org on port 443.
       ExRCA successfully obtained the remote SSL certificate.
       
      Additional Details
       Remote Certificate Subject: CN=greshamchamber.org, OU=Domain Control Validated, O=greshamchamber.org, Issuer: SERIALNUMBER=10688435, CN=Starfield Secure Certification Authority, OU=http://certificates.starfieldtech.com/repository, O="Starfield Technologies, Inc.", L=Scottsdale, S=Arizona, C=US.
      Validating the certificate name.
       The certificate name was validated successfully.
       
      Additional Details
       Host name exchange.greshamchamber.org was found in the Certificate Subject Alternative Name entry.
      Certificate trust is being validated.
       The certificate is trusted and all certificates are present in the chain.
       
      Test Steps
       
      ExRCA is attempting to build certificate chains for certificate CN=greshamchamber.org, OU=Domain Control Validated, O=greshamchamber.org.
       One or more certificate chains were constructed successfully.
       
      Additional Details
       A total of 1 chains were built. The highest quality chain ends in root certificate OU=Starfield Class 2 Certification Authority, O="Starfield Technologies, Inc.", C=US.
      Analyzing the certificate chains for compatibility problems with versions of Windows.
       Potential compatibility problems were identified with some versions of Windows.
       
      Additional Details
       ExRCA can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature isn't enabled.
      Testing the certificate date to confirm the certificate is valid.
       Date validation passed. The certificate hasn't expired.
       
      Additional Details
       The certificate is valid. NotBefore = 8/31/2011 5:29:01 PM, NotAfter = 8/31/2012 5:29:01 PM
      Checking the IIS configuration for client certificate authentication.
       Client certificate authentication wasn't detected.
       
      Additional Details
       Accept/Require Client Certificates isn't configured.
      Attempting to send an Autodiscover POST request to potential Autodiscover URLs.
       ExRCA successfully retrieved Autodiscover settings by sending an Autodiscover POST.
       
      Test Steps
       
      ExRCA is attempting to retrieve an XML Autodiscover response from URL https://exchange.greshamchamber.org/Autodiscover/Autodiscover.xml for user josh.williams@greshamchamber.org.
       The Autodiscover XML response was successfully retrieved.
       
      Additional Details
       Autodiscover Account Settings
XML response:
<?xml version="1.0"?>
<Autodiscover xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
<Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a">
<User>
<DisplayName>Josh Williams</DisplayName>
<LegacyDN>/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=Josh.Williams</LegacyDN>
<DeploymentId>4af3e138-15a7-448d-94cb-084cce514a41</DeploymentId>
</User>
<Account>
<AccountType>email</AccountType>
<Action>settings</Action>
<Protocol>
<Type>EXCH</Type>
<Server>GACOC.greshamchamber.local</Server>
<ServerDN>/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=GACOC</ServerDN>
<ServerVersion>720180F0</ServerVersion>
<MdbDN>/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=GACOC/cn=Microsoft Private MDB</MdbDN>
<ASUrl>https://gacoc.greshamchamber.local/Ews/Exchange.asmx</ASUrl>
<OOFUrl>https://gacoc.greshamchamber.local/Ews/Exchange.asmx</OOFUrl>
<OABUrl>https://gacoc.greshamchamber.local/Oab/ec002968-2a22-4808-bb52-c0280ee0e400/</OABUrl>
<UMUrl>https://remote.greshamchamber.org/UnifiedMessaging/Service.asmx</UMUrl>
<Port>0</Port>
<DirectoryPort>0</DirectoryPort>
<ReferralPort>0</ReferralPort>
<PublicFolderServer>GACOC.greshamchamber.local</PublicFolderServer>
<AD>GACOC.greshamchamber.local</AD>
<EwsUrl>https://gacoc.greshamchamber.local/Ews/Exchange.asmx</EwsUrl>
</Protocol>
<Protocol>
<Type>EXPR</Type>
<Server>exchange.greshamchamber.org</Server>
<ASUrl>https://exchange.greshamchamber.org/Ews/Exchange.asmx</ASUrl>
<OOFUrl>https://exchange.greshamchamber.org/Ews/Exchange.asmx</OOFUrl>
<OABUrl>https://exchange.greshamchamber.org/Oab/ec002968-2a22-4808-bb52-c0280ee0e400/</OABUrl>
<UMUrl>https://remote.greshamchamber.org/UnifiedMessaging/Service.asmx</UMUrl>
<Port>0</Port>
<DirectoryPort>0</DirectoryPort>
<ReferralPort>0</ReferralPort>
<SSL>On</SSL>
<AuthPackage>Ntlm</AuthPackage>
<CertPrincipalName>msstd:greshamchamber.org</CertPrincipalName>
<EwsUrl>https://exchange.greshamchamber.org/Ews/Exchange.asmx</EwsUrl>
</Protocol>
<Protocol>
<Type>WEB</Type>
<Port>0</Port>
<DirectoryPort>0</DirectoryPort>
<ReferralPort>0</ReferralPort>
<External>
<OWAUrl AuthenticationMethod="Fba">https://exchange.greshamchamber.org/owa/</OWAUrl>
<Protocol>
<Type>EXPR</Type>
<ASUrl>https://exchange.greshamchamber.org/Ews/Exchange.asmx</ASUrl>
</Protocol>
</External>
<Internal>
<OWAUrl AuthenticationMethod="Basic, Fba">https://gacoc.greshamchamber.local/owa/</OWAUrl>
<Protocol>
<Type>EXCH</Type>
<ASUrl>https://gacoc.greshamchamber.local/Ews/Exchange.asmx</ASUrl>
</Protocol>
</Internal>
</Protocol>
</Account>
</Response>
</Autodiscover>
      Autodiscover settings for Outlook Anywhere are being validated.
       ExRCA validated the Outlook Anywhere Autodiscover settings.
      Attempting to resolve the host name exchange.greshamchamber.org in DNS.
       The host name resolved successfully.
       
      Additional Details
       IP addresses returned: 173.11.26.174
      Testing TCP port 443 on host exchange.greshamchamber.org to ensure it's listening and open.
       The port was opened successfully.
      Testing the SSL certificate to make sure it's valid.
       The certificate passed all validation requirements.
       
      Test Steps
       
      ExRCA is attempting to obtain the SSL certificate from remote server exchange.greshamchamber.org on port 443.
       ExRCA successfully obtained the remote SSL certificate.
       
      Additional Details
       Remote Certificate Subject: CN=greshamchamber.org, OU=Domain Control Validated, O=greshamchamber.org, Issuer: SERIALNUMBER=10688435, CN=Starfield Secure Certification Authority, OU=http://certificates.starfieldtech.com/repository, O="Starfield Technologies, Inc.", L=Scottsdale, S=Arizona, C=US.
      Validating the certificate name.
       The certificate name was validated successfully.
       
      Additional Details
       Host name exchange.greshamchamber.org was found in the Certificate Subject Alternative Name entry.
      Certificate trust is being validated.
       The certificate is trusted and all certificates are present in the chain.
       
      Test Steps
       
      ExRCA is attempting to build certificate chains for certificate CN=greshamchamber.org, OU=Domain Control Validated, O=greshamchamber.org.
       One or more certificate chains were constructed successfully.
       
      Additional Details
       A total of 1 chains were built. The highest quality chain ends in root certificate OU=Starfield Class 2 Certification Authority, O="Starfield Technologies, Inc.", C=US.
      Analyzing the certificate chains for compatibility problems with versions of Windows.
       Potential compatibility problems were identified with some versions of Windows.
       
      Additional Details
       ExRCA can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature isn't enabled.
      Testing the certificate date to confirm the certificate is valid.
       Date validation passed. The certificate hasn't expired.
       
      Additional Details
       The certificate is valid. NotBefore = 8/31/2011 5:29:01 PM, NotAfter = 8/31/2012 5:29:01 PM
      Checking the IIS configuration for client certificate authentication.
       Client certificate authentication wasn't detected.
       
      Additional Details
       Accept/Require Client Certificates isn't configured.
      Testing HTTP Authentication Methods for URL https://exchange.greshamchamber.org/rpc/rpcproxy.dll.
       The HTTP authentication methods are correct.
       
      Additional Details
       ExRCA found all expected authentication methods and no disallowed methods. Methods found: Negotiate, NTLM
      Testing SSL mutual authentication with the RPC proxy server.
       Mutual authentication was verified successfully.
       
      Additional Details
       Certificate common name greshamchamber.org matches msstd:greshamchamber.org.
      Attempting to ping RPC proxy exchange.greshamchamber.org.
       RPC Proxy was pinged successfully.
       
      Additional Details
       Completed with HTTP status 200 - OK
      Attempting to ping RPC endpoint 6001 (Exchange Information Store) on server GACOC.greshamchamber.local.
       The endpoint was pinged successfully.
       
      Additional Details
       RPC Status Ok (0) returned in 215 ms.
      Testing the Name Service Provider Interface (NSPI) on the Exchange Mailbox server.
       The NSPI interface was tested successfully.
       
      Test Steps
       
      Attempting to ping RPC endpoint 6004 (NSPI Proxy Interface) on server GACOC.greshamchamber.local.
       The endpoint was pinged successfully.
       
      Additional Details
       RPC Status Ok (0) returned in 325 ms.
      Testing NSPI "Check Name" for user josh.williams@greshamchamber.org against server GACOC.greshamchamber.local.
       Check Name succeeded.
       
      Additional Details
       DisplayName: Josh Williams, LegDN: /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=Josh.Williams
      Testing the Referral service on the Exchange Mailbox server.
       The Referral service was tested successfully.
       
      Test Steps
       
      Attempting to ping RPC endpoint 6002 (Referral Interface) on server GACOC.greshamchamber.local.
       The endpoint was pinged successfully.
       
      Additional Details
       RPC Status Ok (0) returned in 358 ms.
      Attempting to perform referral for user /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=Josh.Williams on server GACOC.greshamchamber.local.
       ExRCA successfully got the referral.
       
      Additional Details
       The server returned by the Referral service: GACOC.greshamchamber.local
      Testing the Exchange Information Store on the Mailbox server.
       ExRCA successfully tested the Information Store.
       
      Test Steps
       
      Attempting to ping RPC endpoint 6001 (Exchange Information Store) on server GACOC.greshamchamber.local.
       The endpoint was pinged successfully.
       
      Additional Details
       RPC Status Ok (0) returned in 31 ms.
      Attempting to log on to the Exchange Information Store.
       ExRCA successfully logged on to the Information Store.


Thank you for pointing me in the the right direction for this. in-office and out-of-office is now working, it was IIS. the default SBS Web Applications site needs to have SSL Settings unchecked and client certificates on ignore as well as the sub-folder autodiscover.


One last thing the out of office assistant is still not working? dose anyone have a starting place for this?
0
 
Madan SharmaConsultantCommented:
good to know that your one issue is resolved.
To make out of office work you need to setup webservice directory url's

run these command on your exchange server
Get-WebServicesVirtualDirectory | Set-WebServicesVirtualDirectory -ExternalURL "https://exchange.greshamchamber.org/Ews/Exchange.asmx"


Get-WebServicesVirtualDirectory | Set-WebServicesVirtualDirectory -InternalURL "https://gacoc.greshamchamber.local/Ews/Exchange.asmx"

After that restart exchange client access server and check out of office.
0
 
e_aravindCommented:
So your question is:
One last thing the out of office assistant is still not working? -- At remote\location or Oulook-anywhere profile?

yes, for the OOF to work, on that machine we need to confirm that the Autodiscover works fine
Else, OOF would fail.

Note: (from the above results)
Attempting to locate SRV record _autodiscover._tcp.greshamchamber.org in DNS.
       The Autodiscover SRV record was successfully retrieved from DNS.
       
      Additional Details
       The Service Location (SRV) record lookup returned host exchange.greshamchamber.org.
      Attempting to test potential Autodiscover URL https://exchange.greshamchamber.org/Autodiscover/Autodiscover.xml
       Testing of the Autodiscover URL was successful.
       
      Test Steps
       
      Attempting to resolve the host name exchange.greshamchamber.org in DNS.
       The host name resolved successfully.


===> so the Autodiscover is resolving using the SRV record
IMO, the same SRV translation is not happening on the failing computers.
(may be the DNS-server @ the failing time\computers are refering to another DNS which is not SRV record supported?)
0
 
definitivellcAuthor Commented:
[PS] C:\Windows\System32>Get-WebServicesVirtualDirectory | Set-WebServicesVirtua
lDirectory -ExternalURL "https://exchange.greshamchamber.org/Ews/Exchange.asmx"
WARNING: The command completed successfully but no settings of 'GACOC\EWS (SBS
Web Applications)' have been modified.

[PS] C:\Windows\System32>Get-WebServicesVirtualDirectory | Set-WebServicesVirtua
lDirectory -InternalURL "https://gacoc.greshamchamber.local/Ews/Exchange.asmx"
WARNING: The command completed successfully but no settings of 'GACOC\EWS (SBS
Web Applications)' have been modified.
[PS] C:\Windows\System32>

the commands did not change anything?
0
 
Madan SharmaConsultantCommented:
It means that  your availability service is configured already. Can you please post the exact error you are facing while trying to set out of office.
0
 
e_aravindCommented:
Yes, i can also confirm that the "Web services virtual directory" is configured with the expected External-URLs
But, what if the Autodiscover itself is failing?

IMO, the Outlook-anywhere and\also the clients connecting from external-network...need to have additional name-resolution called as "autodiscover.domain.com"

>> My guess is to still concentrate @ the Autodiscover during the time of the issue (At the client machine where the issue is happening!)

-->When we use the "Test email autoconfiguration" window...after the completion of the Autodiscovery...the Above mentioned external-URLs should be presented to this client.
0
 
Madan SharmaConsultantCommented:
Currently you are using SRV Dns method for auto discover which a bit complicated. I always use a redirection method for autodiscover which is easy to setup and works like a charm. So I'll advice you please setup your autodiscover using redirection method.
here is the article how to setup auto discover using redirection method:-

http://www.uclabs.nl/archive/jaapwess/2011/08/28/autodiscover-redirect-and-srv-option/?lang=en
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.