"..Unnatural work produces too much stress.."

Configure EWS, Autodiscover, OWA, OAB, ECP on Exchange Server 2010

As you all know that the service connectivity for a mail server is the  main concern to all of us. In Exchange server 2010, the connectivity is as same as Exchange server 2007. Once you migrate or install the new version, this should be tested with the proper credentials and certificate..or else, you will end up with your mail server IP going to the blacklist, because of the wrong pointers and configurations. First of all, do the internal test. Go to your computer start bar, right side where Date and time is showing, you will find the Outlook icon, hold Ctrl + right click on the outlook icon and click “Test Email Auto Configuration…”

Select the “Use AutoDiscover” and click Test..

Above one is a success one..If failed, do the below. The Exchange Web Service (EWS) is the web service that allows access to the Out of Office service. If either the internal or external URL for the EWS is missing or incorrect, OOF will fail and other services may not work as expected. Using Exchange Management Shell, check the URLs assigned to the web service virtual directory using the Get-WebServicesVirtualDirectory command

First goto CAS server

Type the following Power Shell command for EWS (Exchange Web Service)

Copy code Get-WebServicesVirtualDirectory |fl identity,internalurl,externalurl

You will get the result like below

Identity    : ECAS1\EWS (Default Web Site)
InternalUrl :
ExternalUrl :

Identity    : ECAS2\EWS (Default Web Site)
InternalUrl :
ExternalUrl :

If this is not correct, you need to fix it.. This has to be done on Powershell command on the CAS server.

To do that…Copy code

[PS]C:\Windows\system32>Set-WebServicesVirtualDirectory -Identity “ECAS1\EWS (Default Web Site)” -InternalUrl -BasicAuthentication:$true

[PS]C:\Windows\system32>Set-WebServicesVirtualDirectory -Identity “ECAS2\EWS (Default Web Site)” -InternalUrl -BasicAuthentication:$true

[PS] C:\Windows\system32>Get-WebServicesVirtualDirectory |fl identity,internalurl,externalurl

Identity    : ECAS1\EWS (Default Web Site)
InternalUrl :
ExternalUrl :

Identity    : ECAS2\EWS (Default Web Site)
InternalUrl :
ExternalUrl :

Now you can see that the URL has been fixed. This is for Web Services.

Now for Autodiscovery….

[PS] C:\Windows\system32>Get-AutodiscoverVirtualDirectory

To see the settings

[PS] C:\Windows\system32>Get-ClientAccessServer |fl identity,autodiscoverserviceinternaluri


[PS] C:\Windows\system32>Get-ClientAccessServer |fl identity,autodiscoverserviceinternaluri
Identity                       : ECAS1
AutoDiscoverServiceInternalUri :

Identity                       : ECAS2
AutoDiscoverServiceInternalUri :

To FIX it..

[PS] C:\Windows\system32>Set-ClientAccessServer -Identity ECAS1 -AutoDiscoverServiceInternalUri
[PS] C:\Windows\system32>Set-ClientAccessServer -Identity ECAS2 -AutoDiscoverServiceInternalUri 

 Now for the Outlook Web Apps, Exchange Control Panel, Exchange ActiveSync, Offline Address book…you have to go to Exchange Management Console (EMC)

  1. Goto one of the CAS server
  2. Open EMC
  3. Goto Server Configuration
  4. Select Client Access
  5. On the Middle top pannel, you can see the CAS server listed.
  6. Select one, on the bottom pannel, you will see like below.

Select each tab and then right click on the object and change the path as required. Once you done with the first CAS servr, do the same for the second as well.

Thats it…you are good to go for production.

July 3, 2010 - Posted by | Active Directory, Active Sync, ECP, EWS, Exchange Management Console, Exchange Management Shell, Exchange server 2010, Internet Information Services (IIS), Microsoft, OAB, Office, Office 2010, Office 2011, Outlook, Outlook Webapps, OWA, Public Folder, Software, Transport architecture, Windows Server 2008 R2 | , , , , , , , ,


  1. This was a tremendous help. For some reason when I set the directory to the URL, I left out the /EWS directory. I wondered why it worked on my other 2 Exchange servers and not the one I goofed on. Thanks again, you saved me many hours of frustration.

    Comment by Greg | November 15, 2010 | Reply

  2. Additionaly, I start seeing some sort of autodiscover issues not using HTTPS, but rather HTTP, which fails of course because Require SSL is set for /autodiscover virtual directory.

    Comment by soder | December 9, 2010 | Reply

  3. Thanks for your post, It is really helpfull


    Comment by Juan Miguel Samano | January 11, 2011 | Reply

  4. Thanks for the was very helpful and informative.

    Comment by lohith | May 31, 2011 | Reply

  5. This article was a great help to me. Thank you!

    Comment by Tim Russell | August 6, 2011 | Reply

  6. Very helpful Post. I was struggling to resolve similar issue. Thanks

    Comment by KJ | October 6, 2011 | Reply

  7. This is great yet simple checklist approach to how Exchange 2007 and 2010 should be configured for co-existence. Thank you for posting this. It really helped me get my EWS working!


    Comment by Marcina | October 18, 2011 | Reply

  8. thank you so much, very informative post
    i was getting complaints from users about a certificate issue
    i had bad pointers and could not locate the problem

    this was my problem and it`s fixed now 🙂

    Identity : ECAS1\EWS (Default Web Site)
    InternalUrl : https://SERVERNAME.domain.LOCAL/EWS/Exchange.asmx

    SERVERNAME.domain.LOCAL instead of the correct address

    Comment by Garen Hagopian | February 23, 2012 | Reply

  9. Thaks a lot……, it is very helpful

    Comment by Anmol Mishra | September 4, 2014 | Reply

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: