Finally there is an easy way to test Exchange Web Services without pulling your hair out.
It seems like every time I do an Exchange installation, the question arises around how to test remote connectivity. Yes, I could jump on a machine that is external to the network, and test away. But, what about being able to test things while I’m configuring them? Or, ruling out a client that just doesn’t want to work. Or, the often lack of an ActiveSync device to test with… and so on…
In other words, I have been searching for a way to test EWS without worry about collecting various devices to test with.
***BLAM***
It seems my wishes have been answered. I just found this site a couple days ago:
http://www.testexchangeconnectivity.com/
Basically, as the name suggests, you can use this site to test the connectivity to your Exchange environment. Pretty cool!
If you like this, check out some other posts from Tyson:
- When a computer science degree matters, and when it doesn’t
- Since when did cloud computing become/need a manifesto?
- Why would one phish using a Certificate Authority (CA) as bait?
- Would I trust you, if everyone else trusted you?
- Here is a good question: Is scripting programming or just systems administration?
- PowerShell boy and the case of the missing cmdlets!
- Fun with PowerShell 2.0 Eventing!
- Creating a custom 404 page to handle link redirection for ASP.NET web applications
Or if you want, you can also check out some of Tyson’s latest publications:
- Windows PowerShell Unleashed (2ndEdition)
- Windows Server 2008 Unleashed (Yes, I did help on this book)
Lastly, visit the Microsoft Subnet for more news, blogs, and opinions from around the Internet. Or, sign up for the bi-weekly Microsoft newsletter. (Click on News/Microsoft News Alert)
