<?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</title>
	<atom:link href="http://mobilitydojo.net/feed/" rel="self" type="application/rss+xml" />
	<link>http://mobilitydojo.net</link>
	<description>place of the mobility way</description>
	<lastBuildDate>Tue, 31 Jan 2012 21:59:00 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>/CertSrv vs Mobile Devices</title>
		<link>http://mobilitydojo.net/2012/01/31/certsrv-vs-mobile-devices/</link>
		<comments>http://mobilitydojo.net/2012/01/31/certsrv-vs-mobile-devices/#comments</comments>
		<pubDate>Tue, 31 Jan 2012 21:59:00 +0000</pubDate>
		<dc:creator>Andreas</dc:creator>
				<category><![CDATA[Android]]></category>
		<category><![CDATA[Device Management]]></category>
		<category><![CDATA[How-to's]]></category>
		<category><![CDATA[iOS]]></category>
		<category><![CDATA[iPad]]></category>
		<category><![CDATA[iPhone]]></category>
		<category><![CDATA[Windows Phone]]></category>

		<guid isPermaLink="false">http://mobilitydojo.net/?p=1717</guid>
		<description><![CDATA[I mentioned in my last blog about Android Ice Cream Sandwich that it is now possible, (actually from Android 3.x Honeycomb), to enroll certificates directly from the /CertSrv web site onto your mobile device. (If you're running a Microsoft CA of course.)

This is all nice and dandy, but it's not like Android devices are the only devices you're likely to be supporting. With the tablet varieties the split is something like 90/10 iPad vs "the rest". However if you ever tried loading up /CertSrv on your iOS device or your Windows Phone you'll have noticed that it's not working.

I find this slightly annoying, and decided to look into this further. Those pesky ActiveX controls can't be the only reason right? :)

There's two things to sort out here really; is it anything with the web pages themselves and the server, or something on the browser side. Turns out there's a bit of both involved actually.
(...)
I go through how it works and how it doesn't work - and some of the why's.]]></description>
		<wfw:commentRss>http://mobilitydojo.net/2012/01/31/certsrv-vs-mobile-devices/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Client Certificates in Android Ice Cream Sandwich</title>
		<link>http://mobilitydojo.net/2011/12/31/client-certificates-in-android-ice-cream-sandwich/</link>
		<comments>http://mobilitydojo.net/2011/12/31/client-certificates-in-android-ice-cream-sandwich/#comments</comments>
		<pubDate>Sat, 31 Dec 2011 20:00:00 +0000</pubDate>
		<dc:creator>Andreas</dc:creator>
				<category><![CDATA[Android]]></category>
		<category><![CDATA[Device Management]]></category>

		<guid isPermaLink="false">http://mobilitydojo.net/?p=1703</guid>
		<description><![CDATA[I touched upon the release of Android 4.0, also known as Ice Cream Sandwich, back in October: 
http://mobilitydojo.net/2011/10/19/ice-cream-sandwiches-for-the-kids/

That was based upon the official docs and emulator, but about a week ago I finally got an actual device in my hands in the form of the Galaxy Nexus, and I find it a lot easier to test on real hardware so I thought I’d revisit the OS to test out some client certificate related features. (The eye candy factor is greatly improved, but it’s not like you can’t find tests of that all over the web.)

I said that certificate support was improved – for instance the support of client certificates with the Google-supplied Exchange ActiveSync client. This implied there might have been some improvements for the browser as well, and the short answer would be yes 
]]></description>
		<wfw:commentRss>http://mobilitydojo.net/2011/12/31/client-certificates-in-android-ice-cream-sandwich/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>System Center Configuration Manager 2012&#8211;Release Candidate Comes Along</title>
		<link>http://mobilitydojo.net/2011/11/09/system-center-configuration-manager-2012release-candidate-comes-along/</link>
		<comments>http://mobilitydojo.net/2011/11/09/system-center-configuration-manager-2012release-candidate-comes-along/#comments</comments>
		<pubDate>Tue, 08 Nov 2011 22:00:00 +0000</pubDate>
		<dc:creator>Andreas</dc:creator>
				<category><![CDATA[Device Management]]></category>
		<category><![CDATA[SCMDM]]></category>
		<category><![CDATA[Updates]]></category>

		<guid isPermaLink="false">http://mobilitydojo.net/?p=1689</guid>
		<description><![CDATA[We’re fond of dabbling with Microsoft products at this site, and System Center is no exception (without Virtual Machine Manager my lab would have been less manageable). I’ve done a lot of articles on System Center Mobile Device Manager, and have also taken quick looks at the successor; System Center Configuration Manager 2012 and the Beta releases: 
System Center Configuration Manager 2012 Beta 2 Available 
SCCM v.Next hits Beta 1

It only seemed natural to at least do an install of the Release Candidate of said product. Now, I have no doubt I can manage my desktop systems and servers with Configuration Manager, but the mobility features…so far they haven’t been causing manic episodes. I have tried to look through the console to see what is available now, assuming that the RC should be pretty much feature complete.
(...)
This time around we get support for more devices, but perhaps not the way we would have wanted to. Read on to see what I mean.]]></description>
		<wfw:commentRss>http://mobilitydojo.net/2011/11/09/system-center-configuration-manager-2012release-candidate-comes-along/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>iOS 5 &#8211; Changes to MDM Usage Policies</title>
		<link>http://mobilitydojo.net/2011/10/20/ios-5-changes-to-mdm-usage-policies/</link>
		<comments>http://mobilitydojo.net/2011/10/20/ios-5-changes-to-mdm-usage-policies/#comments</comments>
		<pubDate>Thu, 20 Oct 2011 20:00:00 +0000</pubDate>
		<dc:creator>Andreas</dc:creator>
				<category><![CDATA[Device Management]]></category>
		<category><![CDATA[iOS]]></category>
		<category><![CDATA[iPad]]></category>
		<category><![CDATA[iPhone]]></category>

		<guid isPermaLink="false">http://mobilitydojo.net/?p=1678</guid>
		<description><![CDATA[I have already covered the new (enterprise relevant) features in iOS 5: 
http://mobilitydojo.net/2011/10/04/ios-5-anything-in-it-for-the-enterprise-conclusion/

Right after releasing that post Apple just launched a couple of changes to how these features work, or rather the policies relating to the usage of them. (The features themselves are still on – don’t worry.)
(...)
A couple of minor things regarding availability of MDM API and Apple Push Notification Service.]]></description>
		<wfw:commentRss>http://mobilitydojo.net/2011/10/20/ios-5-changes-to-mdm-usage-policies/feed/</wfw:commentRss>
		<slash:comments>3</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>iOS 5 &#8211; Anything In It For The Enterprise &#8211; Conclusion</title>
		<link>http://mobilitydojo.net/2011/10/04/ios-5-anything-in-it-for-the-enterprise-conclusion/</link>
		<comments>http://mobilitydojo.net/2011/10/04/ios-5-anything-in-it-for-the-enterprise-conclusion/#comments</comments>
		<pubDate>Tue, 04 Oct 2011 21:00:00 +0000</pubDate>
		<dc:creator>Andreas</dc:creator>
				<category><![CDATA[Device Management]]></category>
		<category><![CDATA[iPhone]]></category>

		<guid isPermaLink="false">http://mobilitydojo.net/?p=1566</guid>
		<description><![CDATA[Drumroll, please… 
iOS 5 is finally here! Pack your sleeping bags, and get ready to stand in line around the block of your neighborhood Apple Store. (We don’t have any where I live so I’ll just wait it out…)

Ok, it’s not shocking really given that it has been around in various betas for months, and this is the season for launching new iGadgets. (Technically iOS 5 was soft launched when the first beta arrived, but RTM is after all the hard launch.)
(...)
I finalize and make a launch day conclusion as to enterprise features in iOS 5 partly based on my previous two posts/rants on the topic.]]></description>
		<wfw:commentRss>http://mobilitydojo.net/2011/10/04/ios-5-anything-in-it-for-the-enterprise-conclusion/feed/</wfw:commentRss>
		<slash:comments>10</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>0</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>4</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>
	</channel>
</rss>

<!-- Dynamic page generated in 1.066 seconds. -->
<!-- Cached page generated by WP-Super-Cache on 2012-02-06 07:02:49 -->

