<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Restricting Exchange ActiveSync Access</title>
	<atom:link href="http://mobilitydojo.net/2009/09/28/restricting-exchange-activesync-access/feed/" rel="self" type="application/rss+xml" />
	<link>http://mobilitydojo.net/2009/09/28/restricting-exchange-activesync-access/</link>
	<description>place of the mobility way</description>
	<lastBuildDate>Thu, 09 Sep 2010 18:06:18 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Andreas</title>
		<link>http://mobilitydojo.net/2009/09/28/restricting-exchange-activesync-access/comment-page-1/#comment-15636</link>
		<dc:creator>Andreas</dc:creator>
		<pubDate>Sun, 18 Jul 2010 09:45:35 +0000</pubDate>
		<guid isPermaLink="false">http://mobilitydojo.net/?p=856#comment-15636</guid>
		<description>This setting only controls what is synced down by default when a new mail arrives. For instance the default is 3kb which means only 3kb will be downloaded if you receive a 10kb mail. But you can open the mail and select that you want to download the rest as well. The theory behind the setting behind that if you receive a large html-formatted mail you will not bother to download it all, and thus save on the data traffic. So while you can save on the data download for your users you still can&#039;t prevent them from reading emails in general.</description>
		<content:encoded><![CDATA[<p>This setting only controls what is synced down by default when a new mail arrives. For instance the default is 3kb which means only 3kb will be downloaded if you receive a 10kb mail. But you can open the mail and select that you want to download the rest as well. The theory behind the setting behind that if you receive a large html-formatted mail you will not bother to download it all, and thus save on the data traffic. So while you can save on the data download for your users you still can&#8217;t prevent them from reading emails in general.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: V detta</title>
		<link>http://mobilitydojo.net/2009/09/28/restricting-exchange-activesync-access/comment-page-1/#comment-15378</link>
		<dc:creator>V detta</dc:creator>
		<pubDate>Wed, 14 Jul 2010 14:32:03 +0000</pubDate>
		<guid isPermaLink="false">http://mobilitydojo.net/?p=856#comment-15378</guid>
		<description>Hi there,

great post!

To answer Swift question about limiting to calendar and contacts only during allowed device active sync, I was wondering (since I didn&#039;t test it) as a workaround, to set the value of this Exchange 2010 ActiveSync policy &quot;Maximum e-mail body truncation size&quot; to 0 (it is in kb).  It would allow you to sync emails but maybe only subjects which is closer to what we want there.

So, Andreas, if you have tested this, can you please share the results?

thanks!!

V</description>
		<content:encoded><![CDATA[<p>Hi there,</p>
<p>great post!</p>
<p>To answer Swift question about limiting to calendar and contacts only during allowed device active sync, I was wondering (since I didn&#8217;t test it) as a workaround, to set the value of this Exchange 2010 ActiveSync policy &#8220;Maximum e-mail body truncation size&#8221; to 0 (it is in kb).  It would allow you to sync emails but maybe only subjects which is closer to what we want there.</p>
<p>So, Andreas, if you have tested this, can you please share the results?</p>
<p>thanks!!</p>
<p>V</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonas</title>
		<link>http://mobilitydojo.net/2009/09/28/restricting-exchange-activesync-access/comment-page-1/#comment-14207</link>
		<dc:creator>Jonas</dc:creator>
		<pubDate>Wed, 30 Jun 2010 21:31:48 +0000</pubDate>
		<guid isPermaLink="false">http://mobilitydojo.net/?p=856#comment-14207</guid>
		<description>I still come back to this article now and then to refresh my memory. I upgraded my iPhone to 4.0 and wanted to try if anything happened to ActiveSync policies supported. So I went through them all and tested what worked and not. Here&#039;s the post: http://www.sysadminlab.net/activesync/iphone-os-4-and-exchange-activesync-policies-what-really-works</description>
		<content:encoded><![CDATA[<p>I still come back to this article now and then to refresh my memory. I upgraded my iPhone to 4.0 and wanted to try if anything happened to ActiveSync policies supported. So I went through them all and tested what worked and not. Here&#8217;s the post: <a href="http://www.sysadminlab.net/activesync/iphone-os-4-and-exchange-activesync-policies-what-really-works" rel="nofollow">http://www.sysadminlab.net/activesync/iphone-os-4-and-exchange-activesync-policies-what-really-works</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andreas</title>
		<link>http://mobilitydojo.net/2009/09/28/restricting-exchange-activesync-access/comment-page-1/#comment-10582</link>
		<dc:creator>Andreas</dc:creator>
		<pubDate>Thu, 22 Apr 2010 16:32:47 +0000</pubDate>
		<guid isPermaLink="false">http://mobilitydojo.net/?p=856#comment-10582</guid>
		<description>I don&#039;t know what I was thinking when I wrote that. Because I just tested the cmdlet, and it will only accept DeviceModel and DeviceType as characteristics. Maybe I had something else in mind while typing it all down.

So it seems TechNet is correct :)

Thanks for letting me know! I will correct the article.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t know what I was thinking when I wrote that. Because I just tested the cmdlet, and it will only accept DeviceModel and DeviceType as characteristics. Maybe I had something else in mind while typing it all down.</p>
<p>So it seems TechNet is correct <img src='http://mobilitydojo.net/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Thanks for letting me know! I will correct the article.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hans</title>
		<link>http://mobilitydojo.net/2009/09/28/restricting-exchange-activesync-access/comment-page-1/#comment-10574</link>
		<dc:creator>Hans</dc:creator>
		<pubDate>Thu, 22 Apr 2010 11:46:21 +0000</pubDate>
		<guid isPermaLink="false">http://mobilitydojo.net/?p=856#comment-10574</guid>
		<description>Hi,

Great post. Are you sure though the access rules support all four named categories (Device Model, Device Type, Device OS, Device User Agent) to set restrictions?

As per Technet apparently they only do Device Model and Device Type: http://technet.microsoft.com/en-us/library/dd876923.aspx</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>Great post. Are you sure though the access rules support all four named categories (Device Model, Device Type, Device OS, Device User Agent) to set restrictions?</p>
<p>As per Technet apparently they only do Device Model and Device Type: <a href="http://technet.microsoft.com/en-us/library/dd876923.aspx" rel="nofollow">http://technet.microsoft.com/en-us/library/dd876923.aspx</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andreas</title>
		<link>http://mobilitydojo.net/2009/09/28/restricting-exchange-activesync-access/comment-page-1/#comment-7987</link>
		<dc:creator>Andreas</dc:creator>
		<pubDate>Sat, 26 Dec 2009 12:47:11 +0000</pubDate>
		<guid isPermaLink="false">http://mobilitydojo.net/?p=856#comment-7987</guid>
		<description>I just tested with an HTC HD2 and it synced fine with the non-provisionable setting checked and unchecked.

I have however seen the same issue on an HTC Touch Pro running WM 6.1. It wasn&#039;t with my user account, and I do not know if it is reproducible on the same device with another user account. I have however seen other strange effects regarding the EAS policies, (encryption being enforced even though it&#039;s not checked for instance), so I believe there might be a bug or two. If the bugs are server side or client side I do not know.</description>
		<content:encoded><![CDATA[<p>I just tested with an HTC HD2 and it synced fine with the non-provisionable setting checked and unchecked.</p>
<p>I have however seen the same issue on an HTC Touch Pro running WM 6.1. It wasn&#8217;t with my user account, and I do not know if it is reproducible on the same device with another user account. I have however seen other strange effects regarding the EAS policies, (encryption being enforced even though it&#8217;s not checked for instance), so I believe there might be a bug or two. If the bugs are server side or client side I do not know.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ratish</title>
		<link>http://mobilitydojo.net/2009/09/28/restricting-exchange-activesync-access/comment-page-1/#comment-7942</link>
		<dc:creator>Ratish</dc:creator>
		<pubDate>Wed, 23 Dec 2009 10:30:19 +0000</pubDate>
		<guid isPermaLink="false">http://mobilitydojo.net/?p=856#comment-7942</guid>
		<description>Hi,

This is indeed a great post.
Are you aware of the compatibility issues with Win mobile 6.5 and the setting &quot;Allow non-provisionable devices&quot; ??

If we check that box - Allow non-provisionable devices, Mobile will sync fine... wont if we dont...</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>This is indeed a great post.<br />
Are you aware of the compatibility issues with Win mobile 6.5 and the setting &#8220;Allow non-provisionable devices&#8221; ??</p>
<p>If we check that box &#8211; Allow non-provisionable devices, Mobile will sync fine&#8230; wont if we dont&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andreas</title>
		<link>http://mobilitydojo.net/2009/09/28/restricting-exchange-activesync-access/comment-page-1/#comment-6610</link>
		<dc:creator>Andreas</dc:creator>
		<pubDate>Tue, 03 Nov 2009 19:34:57 +0000</pubDate>
		<guid isPermaLink="false">http://mobilitydojo.net/?p=856#comment-6610</guid>
		<description>There isn&#039;t really an Exchange feature to control which mailbox elements will be synced. You can make some workarounds device side if you provision the settings by other means than the user typing them in. I don&#039;t know if you are familiar with xml provisioning, but building on this xml example: 
http://msdn.microsoft.com/en-us/library/bb737364.aspx
By removing the &quot;mail&quot; characteristic it is not an option to synchronize mail. Keep in mind though that this will only work on Windows Mobile devices so unless you block other devices by some means there&#039;s nothing preventing a user from picking up an iPhone and sync their mail.

If you&#039;ve got a tech savvy user they might be able to work around this limitation as well, so it&#039;s not &quot;hackproof&quot;.

The only &quot;easy&quot; solution I can think of is implementing a third-party middleware solution for syncing (will work on more than Windows Mobile devices too), or getting out your Visual Studio and coding. Well, actually, a variation of third-party software is to use middleware for Mobile Device Management - you can then enforce policies on the devices, and implement mechanisms that will not let devices sync if they are not compliant. Either way it involves some work.</description>
		<content:encoded><![CDATA[<p>There isn&#8217;t really an Exchange feature to control which mailbox elements will be synced. You can make some workarounds device side if you provision the settings by other means than the user typing them in. I don&#8217;t know if you are familiar with xml provisioning, but building on this xml example:<br />
<a href="http://msdn.microsoft.com/en-us/library/bb737364.aspx" rel="nofollow">http://msdn.microsoft.com/en-us/library/bb737364.aspx</a><br />
By removing the &#8220;mail&#8221; characteristic it is not an option to synchronize mail. Keep in mind though that this will only work on Windows Mobile devices so unless you block other devices by some means there&#8217;s nothing preventing a user from picking up an iPhone and sync their mail.</p>
<p>If you&#8217;ve got a tech savvy user they might be able to work around this limitation as well, so it&#8217;s not &#8220;hackproof&#8221;.</p>
<p>The only &#8220;easy&#8221; solution I can think of is implementing a third-party middleware solution for syncing (will work on more than Windows Mobile devices too), or getting out your Visual Studio and coding. Well, actually, a variation of third-party software is to use middleware for Mobile Device Management &#8211; you can then enforce policies on the devices, and implement mechanisms that will not let devices sync if they are not compliant. Either way it involves some work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Swift</title>
		<link>http://mobilitydojo.net/2009/09/28/restricting-exchange-activesync-access/comment-page-1/#comment-6606</link>
		<dc:creator>Swift</dc:creator>
		<pubDate>Tue, 03 Nov 2009 16:34:18 +0000</pubDate>
		<guid isPermaLink="false">http://mobilitydojo.net/?p=856#comment-6606</guid>
		<description>Hi there,

our corporate policy doesnt allow unauthorized phones from syncing email per activesync. 

Is there a method to enable only Calendar and
contacts?

Thanx for your help.</description>
		<content:encoded><![CDATA[<p>Hi there,</p>
<p>our corporate policy doesnt allow unauthorized phones from syncing email per activesync. </p>
<p>Is there a method to enable only Calendar and<br />
contacts?</p>
<p>Thanx for your help.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andreas</title>
		<link>http://mobilitydojo.net/2009/09/28/restricting-exchange-activesync-access/comment-page-1/#comment-6043</link>
		<dc:creator>Andreas</dc:creator>
		<pubDate>Tue, 06 Oct 2009 21:48:07 +0000</pubDate>
		<guid isPermaLink="false">http://mobilitydojo.net/?p=856#comment-6043</guid>
		<description>I never could quite figure out why ISA server could only provide blacklisting as an option. It is sort of a hassle to maintain a blacklist.

The RC of ForeFront TMG will be out soon, so I&#039;ll have to research that option closer, as well as some other ideas I have on the block. I hope to make some progress on the next article - I sort of want it to be practical advice and not just a lot of theory on how it could be done.</description>
		<content:encoded><![CDATA[<p>I never could quite figure out why ISA server could only provide blacklisting as an option. It is sort of a hassle to maintain a blacklist.</p>
<p>The RC of ForeFront TMG will be out soon, so I&#8217;ll have to research that option closer, as well as some other ideas I have on the block. I hope to make some progress on the next article &#8211; I sort of want it to be practical advice and not just a lot of theory on how it could be done.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
