[EWS] How to test an Exchange autodiscover library RRS feed

  • Question

  • I am trying to develop a robust open sourced Exchange auto-discovery package in Python. I signed up for a paid Exchange Online account for development purposes. Then I started reading this document: http://msdn.microsoft.com/en-us/library/ee332364.aspx and soon realised that my paid Exchange Online account will not help me test my solution for all the scenarios listed there. For e.g. the Active Directory based lookup.

    I was wondering if there are any resources available that will allow me to validate my library against all or most prevalent Exchange deployment scenarios. 


    Saturday, March 15, 2014 9:53 AM

All replies

  • Generally the best way is to setup your own lab using virtual machines, there is TechNet labs which have hosted VM's http://social.technet.microsoft.com/wiki/contents/articles/3894.exchange-server-virtual-labs.aspx but these really aren't meant to be used by developers. There are also VHD's downloads of 2007 and 2010 http://www.microsoft.com/en-us/download/search.aspx?q=msvhds (but these are getting quite old now).

    In the real world the way in which DNS and Autodiscover is configured (or missconfigued) can vary greatly. https://testconnectivity.microsoft.com/ is probably the best implementation of DNS Autodiscover around.


    Monday, March 17, 2014 3:04 AM
  •  Hello Sriram,

    1 option is buy virtual vm's at AWS.  You need following stuff in general :-

    - 1 vm which will act as a domain controller,DNS. [ Windows 2008 R2 or Windows 2008 ENT edition with SP2 ]
    - 1 vm with Exchange 2010 STD edition or ENT edition.
    - 1 public IP from AWS [ to bind with external domain name, to add PTR record i.e. reverse DNS lookup ]
    - internal DNS to resolve autodiscover URL internally.

    Alternatives are "Microsoft Azure" , "RackSpace" . Pricing wise I think "RackSpace" would be more cheaper in cost.

    Eager to read about your ongoing development for autodiscover package in python.

    Saturday, April 12, 2014 3:54 AM
  • Hey, is the source code for the testconnectivity.microsoft.com available publicly?
    Thursday, April 17, 2014 2:36 PM