By now Windows Phone 7 has been released on all continents to my knowledge. Not necessarily all countries, and in some countries they aren’t “properly launched” with the devices not having been localized yet (and thus miss out on some Zune features). Nonetheless they are generally available, and you can probably import one if it’s not available at your local device pusher. So, you’re probably thinking I’m more than a little bit fashionably late for not actually getting around to playing with an RTM device until now. (Spending an unhealthy amount of time with Cupertino-based products lately being one of the reasons. But that’s a different story.)
The device I’m using for this article is the HTC Trophy running Windows Phone 7 build 7.0.7004.0. Nothing here should be device specific though and should apply to other WP devices as well.
Now, what is the first thing we check with new devices? Why, it’s Exchange ActiveSync of course Read On
Windows Phone 7 reached RTM a couple of weeks ago, but it wasn’t publicly available until yesterday (September 16) when the RTM developer tools were released. The developer tools include an emulator running the RTM build, and I thought I could use it for some testing and write down some of the things learned.
The thing I don’t quite understand is that even now the emulator is locked – you can only access Internet Explorer and the apps you deploy yourself. No chance playing around with all the features.
If you do a little Internet search with the word “unlocked” included you will of course find an emulator image that does not have these restrictions. By default it has a rather neutral theme:
I do not know why, but Microsoft has decided not to include any features requiring accounts so you are not able to test ActiveSync in the emulator (or Facebook, etc). This also goes for the unlocked image, and from what I read over at the Windows Phone MSDN forums you will need a physical device for these features.
Fret not, I have access to a developer device also running RTM, and I did some testing with that to see if I could get it working with Exchange.
The device unsurprisingly has no problems connecting to Exchange 2010 SP1, but it “only” supports EAS version 14.0 (Exchange 2010 RTM) at this time. I’m guessing they didn’t have time to support 14.1 since Service Pack 1 for 2010 just RTMed itself. The rest:
Device type: WP
Device OS: Windows Phone7.0.7003
User agent: MSFT-WP/7.0.7003
Since I want to test out features like IRM OTA (reading RMS-protected mails without cradling) this is a shame, though I must admit I do not need this on a daily basis. (Chicken and egg kind of problem. If I was able to put it into a working infrastructure maybe I would use it…) Still easily a month before we see devices being available for purchase so we might see an update before that if we’re lucky. Windows Phone 7 should support FOTA (firmware over the air) so I’m not really worried so far about this not becoming available when it’s ready.
Not that much more to report on ActiveSync at the moment I guess – on to testing other features 🙂
23. November 2010: Update – I’ve posted an article with some more details on Windows Phone 7 vs Exchange:
While it’s starting to become quite a while since I published DojoCrypt for enabling the built-in encryption on Windows Mobile Professional I’ve had a couple requests along the way to build a version for Windows Mobile Standard as well. So far I haven’t invested much energy in creating that since my experience is that the Standard devices are far less common than the touch-based Professional devices and I didn’t want to invest re-creating the GUI for those devices. (You are free to call me lazy if you will.)
It has certainly taken me some time to get around to it, but I thought “what the heck let’s see how much work it really is”, and so I bring you something to use on WM 6.1/6.5 Standard. It works the same way as the Pro version with a few changes – the most obvious being a slightly different interface since you can’t tap the screen.
I’ve not included the ability to add inclusions/exclusions at the moment. I might add that later if I see it being necessary. It’s not “difficult” to include, but I’m not sure how user-friendly this can get on a Standard device…
Another thing you might notice with this version is that Standard devices are more often than the Pro devices locked-down (so-called Two-tier mode) which would prevent you from using this application as it has not been signed with a trusted privileged certificate. Not much I can do about that really (you would need to unlock your device).
Bugs? You know where to file them 🙂