Category Archives: Updates

EAS-MD Version 1.4 – Autodiscover Support

This time around it was a long release cycle, but I have gotten around to finishing up a new build of the EAS-MD utility and upping the version number to 1.4.

The main addition to this release is that I’ve added support for testing Autodiscover. This can be a tricky point getting to work properly so I thought it could be relevant for of you. This means I’ve also added support in general for redirection and reading it out if you’re hitting a non-optimal Client Access Server. (The modus operandi for Office 365 is apparently that you should configure your device with m.outlook.com and then be redirected to a specific CAS. They might have changed this by now since Android devices have a couple of problems with this approach – I do not know since I haven’t tested the ActiveSync part of Office 365 yet.)

There are a couple of other changes as well:
- Added Client Certificate Password text box (for pfx-files).
- Added ActiveSync Autodiscover tests. (Please note that SRV record support is not added yet, and thus disabled in the UI.)
- Added scrollbars to output windows.
- Added possibility to use both domain\user and user@domain.com (leave “Domain” textbox empty to use the latter).
- Added support for parsing out the redirect on a HTTP 451.
- Added handling of HTTP 302.
- Added explanation for HTTP 502.
- Added explanation for HTTP 504.
- Disabled “Hex” view option on Main tab. (Code still present, but not sure if this is actually useful, so it’s not active in the UI.)
- Re-designed how HTTP status codes are shown in the output view. (Parses out the individual HTTP codes for errors.)
- Changed default protocol version to 12.1 (Exchange 2007 SPx).
- Major code refactoring.
- Fixed minor bugs.
- Minor changes in the UI.
- Added about tab. (Easier to identify the version you’re running.)
(…)
And a description of how Autodiscover works.

EAS-MD – Taking Orders for Feature Requests

Currently I’m in the planning phase for my next release of my EAS-MD diagnostic utility, and I’d be happy to hear what kind of features you, the users, might be missing from this application in it’s current version.
(…)
I have a few features lined up already on my own part:
– Support for pfx certificates (password protected certs).
– Support for CAS redirect (HTTP 451/302).
– Change default protocol version to 12.1 (currently 12.0).
– Support for Exchange 2010 Service Pack 2. This is of course dependent on SP2 being released in Beta in the near future, and the introduction of new ActiveSync features in said release.
– Add tests related to Exchange ActiveSync AutoDiscover.
– “Tweak” the output view. (What info, and in what format, do you need it?)
(…)

Feedback/requests are welcome in the comments section below.

A Beta Taste of Mango

The next release of Windows Phone 7, at the moment versioned as 7.1 and going by the code name Mango, has been hyped up for the past couple of weeks and it was also put into the hands of techno journalists last week who took the upgrade for a spin and in general gave it a thumbs up.

The RTM release hasn’t gotten a set date yet, but late Q3 probably isn’t entirely unlikely. The problem for the not-so-average user is of course that a lot of people want to test it before their users/customers are able to do an update. Last year the only way to do this was to join the slightly exclusive club of people who received a device directly from Microsoft. And it wasn’t really that easy to sign up for it – an amount of luck had to be involved.

Rumors surfaced that developers might get a preview this time, but the details were sketchy. (Let’s be honest – the emulator isn’t thrilling even though it works for most development purposes.) But last night I received an email with an invitation to join the Windows Phone Beta Program on Microsoft Connect and an indication that I’d be able to test Beta 2 on my personal phone.

RSS for Posts RSS for Comments