So, I’ve been ranting about Information Rights Management (IRM) in Exchange 2010 Service Pack 1 for a couple of posts now, and trying to distill some info about how it works with Exchange ActiveSync. After nurturing my unhealthy interest in the ActiveSync protocol for a couple of days following my last post, I did what I felt would be the natural follow-up, (at least for me personally), and added another tab to my EAS MD diagnostic utility.
I’ve added a new tab called “Information Rights Management”:
As you can see there aren’t all that many actions you perform here. You’re not able to read or send IRM-protected emails, but remember – I am not making a fully featured ActiveSync client here. It’s a utility for testing, and as far as I can tell testing that you can pull down the available IRM policies is a good initial indication as to whether your Exchange Server is up to it or not. Above you can see a successful pull-down of policies, but I’ve incorporated catching of the documented status codes that can be returned when IRM fails. (Some of those you aren’t likely to see when getting the policies, and should only occur during other IRM-related actions.)
There’s really only one button to click (if you don’t count the “Clear” button), but remember to fill out the necessary details on the “Main” tab first and do a provision if necessary. IRM requires Exchange 2010 SP1 server side, and will fail if you haven’t got that. It’s also of interest to note that using IRM does not require provisionable devices. Now, I understand that most EAS clients that implement IRM will also implement a minimum of security policies, but technically speaking it’s not required.
There are a few other minor tweaks to this release of EAS MD:
– Able to catch HTTP 451. This is a redirect server side that could occur if you are running EAS clients connecting to Exchange 2007, and then decide to move the mailboxes to Exchange 2010, and use a different external URL. The server will then return the correct URL for that particular mailbox, and EAS MD will attempt to print it out for you. A properly coded full-featured client would use this to change server address without bothering the user.
– “Word Wrap”. Might improve the readability of the wbxml output in some instances by doing a line break when a close tag is hit. I’m not saying it looks perfect yet, but I found it to be more easy reading the IRM policies this way. Up to you if you want to use it
I initially wanted to have as few options as possible in this utility, but I’ve added several buttons and textboxes over the iterations. I’m not sure if it’s becoming bloated or if it makes sense doing it like this. (I’m not entirely unbiased as to be the judge of this.) So, I don’t know… Should I add more features? If so, which features would be relevant to add? Do give me feedback if you have any thoughts.
Hit the downloads section to fetch it: http://mobilitydojo.net/downloads