<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>MobilityDojo.net &#187; Exchange</title>
	<atom:link href="http://mobilitydojo.net/category/exchange/feed/" rel="self" type="application/rss+xml" />
	<link>http://mobilitydojo.net</link>
	<description>place of the mobility way</description>
	<lastBuildDate>Mon, 14 May 2012 21:00:00 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>EAS MD &#8211; Spring 2012 Updates</title>
		<link>http://mobilitydojo.net/2012/04/23/eas-md-spring-2012-updates/</link>
		<comments>http://mobilitydojo.net/2012/04/23/eas-md-spring-2012-updates/#comments</comments>
		<pubDate>Mon, 23 Apr 2012 21:00:00 +0000</pubDate>
		<dc:creator>Andreas</dc:creator>
				<category><![CDATA[ActiveSync]]></category>
		<category><![CDATA[Exchange]]></category>
		<category><![CDATA[Updates]]></category>
		<category><![CDATA[Utilities]]></category>

		<guid isPermaLink="false">http://mobilitydojo.net/?p=1777</guid>
		<description><![CDATA[Short description of, and a few screenshots, of the latest updates to the EAS MD utilities.
Now with support for WBXML output in both versions, and WBXML encoding and decoding in the desktop client.]]></description>
		<wfw:commentRss>http://mobilitydojo.net/2012/04/23/eas-md-spring-2012-updates/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Exchange ActiveSync Building Blocks &#8211; GAL Search</title>
		<link>http://mobilitydojo.net/2012/03/13/exchange-activesync-building-blocks-gal-search/</link>
		<comments>http://mobilitydojo.net/2012/03/13/exchange-activesync-building-blocks-gal-search/#comments</comments>
		<pubDate>Tue, 13 Mar 2012 21:30:23 +0000</pubDate>
		<dc:creator>Andreas</dc:creator>
				<category><![CDATA[ActiveSync]]></category>
		<category><![CDATA[Coding]]></category>
		<category><![CDATA[Exchange]]></category>
		<category><![CDATA[How-to's]]></category>

		<guid isPermaLink="false">http://mobilitydojo.net/?p=1757</guid>
		<description><![CDATA[Based on the developer-friendly implementation of an encoder and decoder for AS-WBXML I just build it with a small sample implementing GAL search.]]></description>
		<wfw:commentRss>http://mobilitydojo.net/2012/03/13/exchange-activesync-building-blocks-gal-search/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Exchange ActiveSync Building Blocks&#8211;Encode &amp; Decode</title>
		<link>http://mobilitydojo.net/2012/03/07/exchange-activesync-building-blocksencode-decode/</link>
		<comments>http://mobilitydojo.net/2012/03/07/exchange-activesync-building-blocksencode-decode/#comments</comments>
		<pubDate>Tue, 06 Mar 2012 22:00:00 +0000</pubDate>
		<dc:creator>Andreas</dc:creator>
				<category><![CDATA[ActiveSync]]></category>
		<category><![CDATA[Coding]]></category>
		<category><![CDATA[Exchange]]></category>
		<category><![CDATA[How-to's]]></category>

		<guid isPermaLink="false">http://mobilitydojo.net/?p=1746</guid>
		<description><![CDATA[If you have followed the "building blocks" series you will have noticed that I have done the AS-WBXML by hand. This approach clearly doesn't scale, and will not work outside these constrained snippets intended for learning. And it makes for sample apps that are only able to serve up a very specific purpose. (Now, the sample code is meant for copying and pasting so that's pretty much by design anyways.) Not to mention it has made me look lazy for not doing things properly 

Clearly we would be a significant step further if we didn't have to create the web requests by looking up values in code pages and type in each individual byte. So, how about we take it to that very next level of Exchange ActiveSync "hacking"?
(...)
We go through how we can build a utility for encoding and decoding ASWBXML so you can copy &#038; paste XML samples from the MSDN library and test against your Exchange Server.]]></description>
		<wfw:commentRss>http://mobilitydojo.net/2012/03/07/exchange-activesync-building-blocksencode-decode/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Exchange ActiveSync Building Blocks &#8211; DocumentLibrary</title>
		<link>http://mobilitydojo.net/2012/02/20/exchange-activesync-building-blocks-documentlibrary/</link>
		<comments>http://mobilitydojo.net/2012/02/20/exchange-activesync-building-blocks-documentlibrary/#comments</comments>
		<pubDate>Mon, 20 Feb 2012 15:00:00 +0000</pubDate>
		<dc:creator>Andreas</dc:creator>
				<category><![CDATA[ActiveSync]]></category>
		<category><![CDATA[Coding]]></category>
		<category><![CDATA[Exchange]]></category>
		<category><![CDATA[How-to's]]></category>

		<guid isPermaLink="false">http://mobilitydojo.net/?p=1732</guid>
		<description><![CDATA[So, it's been a couple of months since I've been digging through the Exchange ActiveSync protocol and creating "building blocks", but the series is not abandoned yet. Sure, it went on a hiatus after covering a lot of ground in a comparably small time frame, but I will return to the topic whenever there's something I find worthwhile. (Replicating every bit of info already in MSDN is obviously not worthwhile.)

Today I thought I'd take a closer look at a feature many probably don't consider as an ActiveSync feature; file browsing :)
]]></description>
		<wfw:commentRss>http://mobilitydojo.net/2012/02/20/exchange-activesync-building-blocks-documentlibrary/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Ice Cream Sandwiches For The Kids!</title>
		<link>http://mobilitydojo.net/2011/10/19/ice-cream-sandwiches-for-the-kids/</link>
		<comments>http://mobilitydojo.net/2011/10/19/ice-cream-sandwiches-for-the-kids/#comments</comments>
		<pubDate>Wed, 19 Oct 2011 21:30:00 +0000</pubDate>
		<dc:creator>Andreas</dc:creator>
				<category><![CDATA[Android]]></category>
		<category><![CDATA[Device Management]]></category>
		<category><![CDATA[Exchange]]></category>

		<guid isPermaLink="false">http://mobilitydojo.net/?p=1674</guid>
		<description><![CDATA[I was thinking about a pun about it being for grown-ups, but that might have been interpreted as me saying Android is all grown up. And I haven’t decided on that yet 

After a slight delay Android version 4.0, code name Ice Cream Sandwich has now been launched. This is the next major iteration of the operating system, and this time it should work both on tablets and regular phone form factors. As the number indicates it is not a mix of the 2.x and 3.x branch, but the next branch. All APIs and features from 3.x is included in 4.0.

The main focus of the release is on user interface improvements, as well as general updates of the apps and polishing the OS further. You can find screenshots all over the Internet of course of this.

As usual I don’t care about these things. Well, of course, as a user of devices I care about the interface, but this blog does not concern itself with such matters. A perhaps important feature for people reading this blog is that since Honeycomb features are supported this means that you now get full device encryption on the phone devices and just not the tablets.
(...)
A couple of paragraphs of what I have found so far.]]></description>
		<wfw:commentRss>http://mobilitydojo.net/2011/10/19/ice-cream-sandwiches-for-the-kids/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>EAS MD &#8211; Looking to The Clouds</title>
		<link>http://mobilitydojo.net/2011/10/12/eas-md-looking-to-the-clouds/</link>
		<comments>http://mobilitydojo.net/2011/10/12/eas-md-looking-to-the-clouds/#comments</comments>
		<pubDate>Wed, 12 Oct 2011 21:30:44 +0000</pubDate>
		<dc:creator>Andreas</dc:creator>
				<category><![CDATA[ActiveSync]]></category>
		<category><![CDATA[Exchange]]></category>
		<category><![CDATA[Updates]]></category>
		<category><![CDATA[Utilities]]></category>

		<guid isPermaLink="false">http://mobilitydojo.net/?p=1660</guid>
		<description><![CDATA[I've grown quite fond of my EAS MD utility, and it's also been great fun sharing the code powering it for the past weeks/months. When I originally started out coding it I was fueled by what I felt were shortcomings in the official diagnostic utility provided by Microsoft; http://testexchangeconnectivity.com. It only supported Exchange 2003 protocol level, had no means of dealing with security policies, and in general didn't provide a whole lot of options. It worked OK, but not for the scenarios I wanted to test.

When you're a programmer at heart this means there might come a moment when you get a feeling of "why not build what I want myself instead of accepting the tools available as is". Not to mention that other people aren't going to accept your "whining" either and will eventually challenge you to do better. (I wasn't pressured by anyone else than myself when it came to this issue though.)

(...)

Today I have come full circle, returning to where we started, and present a web version of EAS MD to you :)]]></description>
		<wfw:commentRss>http://mobilitydojo.net/2011/10/12/eas-md-looking-to-the-clouds/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Exchange ActiveSync Building Blocks &#8211; Remote Wipe</title>
		<link>http://mobilitydojo.net/2011/09/28/exchange-activesync-building-blocks-remote-wipe/</link>
		<comments>http://mobilitydojo.net/2011/09/28/exchange-activesync-building-blocks-remote-wipe/#comments</comments>
		<pubDate>Wed, 28 Sep 2011 21:00:04 +0000</pubDate>
		<dc:creator>Andreas</dc:creator>
				<category><![CDATA[ActiveSync]]></category>
		<category><![CDATA[Coding]]></category>
		<category><![CDATA[Exchange]]></category>
		<category><![CDATA[How-to's]]></category>

		<guid isPermaLink="false">http://mobilitydojo.net/?p=1627</guid>
		<description><![CDATA[In the previous installment in this series we looked at how security policies are pushed down to our Exchange ActiveSync clients, and how to deal with them, or for that matter circumvent them. Thus I thought that it would be suitable to cover a topic highly related to implementation of security policies – how to handle remote wipe  

When dealing with the "wipe" concept there are two kinds of wipes we need to be aware of; local wipe and remote wipe. 
(...)
I take a look at the low level details of the remote wipe process, along with some sample C# code that will get you started on your own.]]></description>
		<wfw:commentRss>http://mobilitydojo.net/2011/09/28/exchange-activesync-building-blocks-remote-wipe/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Exchange ActiveSync Building Blocks &#8211; Provisioning</title>
		<link>http://mobilitydojo.net/2011/09/20/exchange-activesync-building-blocks-provisioning/</link>
		<comments>http://mobilitydojo.net/2011/09/20/exchange-activesync-building-blocks-provisioning/#comments</comments>
		<pubDate>Tue, 20 Sep 2011 21:00:00 +0000</pubDate>
		<dc:creator>Andreas</dc:creator>
				<category><![CDATA[ActiveSync]]></category>
		<category><![CDATA[Coding]]></category>
		<category><![CDATA[Exchange]]></category>
		<category><![CDATA[How-to's]]></category>

		<guid isPermaLink="false">http://mobilitydojo.net/?p=1564</guid>
		<description><![CDATA[I hope you've all been following along and gained a deeper understanding of the Exchange ActiveSync protocol, and possibly had time to play with coding something yourself if you are so inclined. We should at this time be able to do the initial FolderSync with Exchange, and handle most errors thrown at us. 

There are of course tons of things ActiveSync I haven't covered yet, and it is a "one step at a time" journey. 

If you're testing against an Exchange Server where you do not have direct access to the admin console, and it is under the control of an Exchange admin who doesn't permit just about anyone to sync you might have run into issues related to provisioning already, so the next step for us is to cover this very topic.

Provisioning is the mechanism which ensures that ActiveSync clients implement a given set of security policies. If necessary; Exchange Server will block devices that don't implement the policy set.

(...)

Follow along as I show in code how to perform the provisioning process, or bypass it for that matter :)]]></description>
		<wfw:commentRss>http://mobilitydojo.net/2011/09/20/exchange-activesync-building-blocks-provisioning/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Exchange ActiveSync Building Blocks &#8211; AS-WBXML</title>
		<link>http://mobilitydojo.net/2011/09/07/exchange-activesync-building-blocks-as-wbxml/</link>
		<comments>http://mobilitydojo.net/2011/09/07/exchange-activesync-building-blocks-as-wbxml/#comments</comments>
		<pubDate>Wed, 07 Sep 2011 20:00:00 +0000</pubDate>
		<dc:creator>Andreas</dc:creator>
				<category><![CDATA[ActiveSync]]></category>
		<category><![CDATA[Coding]]></category>
		<category><![CDATA[Exchange]]></category>
		<category><![CDATA[How-to's]]></category>

		<guid isPermaLink="false">http://mobilitydojo.net/?p=1562</guid>
		<description><![CDATA[I have referred to WBXML a couple of times in this series, but so far not going into any detail other than generically describing it as "ActiveSync language". I'm not attempting to make this seem like "magic" or anything, but when I started hacking around with the Exchange ActiveSync protocol myself I felt that I had to get comfortable with the basic concepts before going into this. 

If you recall when we made our first sync attempt with the FolderSync command in a POST I included the following variable as the content of the POST: 
(...)
I have no idea why I thought it logical to define the bytes with their decimal value rather than the hexadecimal value (which I have used in later WBXMLs). Still; this is a rather short and sweet snippet of WBXML so we should be able to decode it manually by using a lookup table. I've converted the values to hex, and "translated" each byte to the plain xml representation. 

Read on for more fun with binary xml.]]></description>
		<wfw:commentRss>http://mobilitydojo.net/2011/09/07/exchange-activesync-building-blocks-as-wbxml/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Exchange ActiveSync Building Blocks &#8211; Error Handling</title>
		<link>http://mobilitydojo.net/2011/09/01/exchange-activesync-building-blocks-error-handling/</link>
		<comments>http://mobilitydojo.net/2011/09/01/exchange-activesync-building-blocks-error-handling/#comments</comments>
		<pubDate>Thu, 01 Sep 2011 20:00:00 +0000</pubDate>
		<dc:creator>Andreas</dc:creator>
				<category><![CDATA[ActiveSync]]></category>
		<category><![CDATA[Coding]]></category>
		<category><![CDATA[Exchange]]></category>
		<category><![CDATA[How-to's]]></category>

		<guid isPermaLink="false">http://mobilitydojo.net/?p=1560</guid>
		<description><![CDATA[If you've followed the past couple of articles you'll no doubt have noticed I haven't gone out of my way to handle exceptions and errors gracefully. If you run into a problem when running the sample code against an Exchange that for some reason is configured differently than mine, (also known as entirely wrong by definition), you might run into the very helpful "Something happened" message without further explanation.

One might be tempted to ask if it's because I'm lazy, or simply do not know how to handle it. Well, ask no more, because I now intend to do something about it :)
(..)
Listing two methods for handling exceptions and errors]]></description>
		<wfw:commentRss>http://mobilitydojo.net/2011/09/01/exchange-activesync-building-blocks-error-handling/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

