<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Exchange ActiveSync client connectivity in Office 365</title><link>http://blogs.technet.com/b/exchange/archive/2012/02/07/cross-site-redirection-exchange-activesync-clients-in-office-365.aspx</link><description>Update: 4/23/2012: Microsoft has completed deployment of the interim solution that should eliminate the need for manual server reconfiguration of the affected devices when your Office 365 server location changes. We continue to work with device manufacturers</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Exchange ActiveSync client connectivity in Office 365</title><link>http://blogs.technet.com/b/exchange/archive/2012/02/07/cross-site-redirection-exchange-activesync-clients-in-office-365.aspx#3495731</link><pubDate>Wed, 02 May 2012 22:26:22 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3495731</guid><dc:creator>Chief Scientist</dc:creator><description>&lt;p&gt;@up to old tricks again: &amp;nbsp;I fail to see how this is a &amp;quot;trick&amp;quot;. &amp;nbsp;Microsoft upgraded its service to give a better experience to &amp;quot;Everyone&amp;quot;, but 1% of users had a problem connecting after the upgrade, and it was &amp;quot;their&amp;quot; fault, because their clients had a legacy defect which was not detected until now.&lt;/p&gt;
&lt;p&gt;BTW, the defect in Android is fixed in 4.0.4, according to the Android support site. &amp;nbsp; &lt;/p&gt;
&lt;p&gt;And in the meantime, Microsoft even decided to use a &amp;quot;non-standard&amp;quot; solution to please as many users as possible.&lt;/p&gt;
&lt;p&gt;that&amp;#39;s good customer service, not tricks!&lt;/p&gt;
&lt;p&gt;-e&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3495731" width="1" height="1"&gt;</description></item><item><title>re: Exchange ActiveSync client connectivity in Office 365</title><link>http://blogs.technet.com/b/exchange/archive/2012/02/07/cross-site-redirection-exchange-activesync-clients-in-office-365.aspx#3495722</link><pubDate>Wed, 02 May 2012 21:31:48 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3495722</guid><dc:creator>Amir Haque [MSFT]</dc:creator><description>&lt;p&gt;James: Nope, you don&amp;#39;t need to do anything on client side. On server side, when your mobile device connects and if your mailbox has moved to another server, the requests from your device will be passed on to that new server. You can connect to any server name in Office 365 (i.e. m.outlook.com, &amp;#39;pod&amp;#39; or host based names as mentioned in the blog post above), the new mechanism will work for you in all three cases.&lt;/p&gt;
&lt;p&gt;Solko: Read &amp;#39;Update&amp;#39; from 4/23/2012 posted at the top of this blog post. The fix has been fully deployed in Office 365.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3495722" width="1" height="1"&gt;</description></item><item><title>re: Exchange ActiveSync client connectivity in Office 365</title><link>http://blogs.technet.com/b/exchange/archive/2012/02/07/cross-site-redirection-exchange-activesync-clients-in-office-365.aspx#3495593</link><pubDate>Wed, 02 May 2012 07:04:15 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3495593</guid><dc:creator>solko</dc:creator><description>&lt;p&gt;What is the status of this fix?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3495593" width="1" height="1"&gt;</description></item><item><title>re: Exchange ActiveSync client connectivity in Office 365</title><link>http://blogs.technet.com/b/exchange/archive/2012/02/07/cross-site-redirection-exchange-activesync-clients-in-office-365.aspx#3494063</link><pubDate>Tue, 24 Apr 2012 13:31:24 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3494063</guid><dc:creator>James________</dc:creator><description>&lt;p&gt;How does the 4/23 fix work? Anything need to be done on the client end? Should we be connecting to m.outlook.com, the POP server, or the Exchange Client Access server? &lt;/p&gt;
&lt;p&gt;How was it fixed? Is it now using a more sensical redirection than the HTTP 451 error code it was sending before?&lt;/p&gt;
&lt;p&gt;Will the autodiscover now work better?&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3494063" width="1" height="1"&gt;</description></item><item><title>re: Exchange ActiveSync client connectivity in Office 365</title><link>http://blogs.technet.com/b/exchange/archive/2012/02/07/cross-site-redirection-exchange-activesync-clients-in-office-365.aspx#3491441</link><pubDate>Wed, 11 Apr 2012 07:58:20 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3491441</guid><dc:creator>Sebastian Magnusson</dc:creator><description>&lt;p&gt;Regarding the april 30th fix, will it be a &amp;quot;complete&amp;quot; fix?&lt;/p&gt;
&lt;p&gt;In other words, will the devices then be able to connect to m.outlook.com or - for instance - will it just fix so the mail configuration keeps working after failover/load balancing but you still have to connect initially with podxxxxx.outlook.com?&lt;/p&gt;
&lt;p&gt;We&amp;#39;re in the process of migrating our entire mail structure to Live and this could be a potential showstopper if we have to phase out all the incompatible devices first, so it would be very helpful to know the extent of the upcoming fix.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3491441" width="1" height="1"&gt;</description></item><item><title>re: Exchange ActiveSync client connectivity in Office 365</title><link>http://blogs.technet.com/b/exchange/archive/2012/02/07/cross-site-redirection-exchange-activesync-clients-in-office-365.aspx#3489191</link><pubDate>Thu, 29 Mar 2012 15:26:58 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3489191</guid><dc:creator>Dan</dc:creator><description>&lt;p&gt;have Galaxy SII and had a great deal of difficulty getting it sync with Exchange online - now that it is working -for email - it is sporadic with calendar entriees - does not always sync them... this is a major problem for me - what can i do?&lt;/p&gt;
&lt;p&gt;Buy Touchdown from NitroDesk to use instead of the built in email client on the phone&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3489191" width="1" height="1"&gt;</description></item><item><title>re: Exchange ActiveSync client connectivity in Office 365</title><link>http://blogs.technet.com/b/exchange/archive/2012/02/07/cross-site-redirection-exchange-activesync-clients-in-office-365.aspx#3487070</link><pubDate>Fri, 16 Mar 2012 12:44:05 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3487070</guid><dc:creator>Joanne</dc:creator><description>&lt;p&gt;I have Galaxy SII and had a great deal of difficulty getting it sync with Exchange online - now that it is working -for email - it is sporadic with calendar entriees - does not always sync them... this is a major problem for me - what can i do?&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3487070" width="1" height="1"&gt;</description></item><item><title>re: Exchange ActiveSync client connectivity in Office 365</title><link>http://blogs.technet.com/b/exchange/archive/2012/02/07/cross-site-redirection-exchange-activesync-clients-in-office-365.aspx#3484214</link><pubDate>Fri, 02 Mar 2012 03:28:23 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3484214</guid><dc:creator>Wayne Smith</dc:creator><description>&lt;p&gt;I&amp;#39;m trialling Office365 with a Samsung Galaxy 10.1 and my mailbox is changing each and every day. Worst still, the tablet doesn&amp;#39;t give an error message, it just doesn&amp;#39;t receive mail. I certainly won&amp;#39;t be converting the trial to a paid subscription, even though the issue appears to be with the tablet. I have it now and can&amp;#39;t return it...&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3484214" width="1" height="1"&gt;</description></item><item><title>re: Exchange ActiveSync client connectivity in Office 365</title><link>http://blogs.technet.com/b/exchange/archive/2012/02/07/cross-site-redirection-exchange-activesync-clients-in-office-365.aspx#3483838</link><pubDate>Wed, 29 Feb 2012 16:34:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3483838</guid><dc:creator>James</dc:creator><description>&lt;p&gt;This needs to be fixed asap. &amp;nbsp;I can&amp;#39;t have 300+ users come to me everytime you guys move their mailbox to a new server. &amp;nbsp;The only way to get some android devices to work is to put the host server address in. &amp;nbsp;Everytime that changes the sync breaks and like effing zombies people start heading over to my desk. &amp;nbsp;This is a wide spread problem that needs to be addressed by Microsoft. &amp;nbsp;&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3483838" width="1" height="1"&gt;</description></item><item><title>re: Exchange ActiveSync client connectivity in Office 365</title><link>http://blogs.technet.com/b/exchange/archive/2012/02/07/cross-site-redirection-exchange-activesync-clients-in-office-365.aspx#3483693</link><pubDate>Wed, 29 Feb 2012 05:11:06 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3483693</guid><dc:creator>tnawab</dc:creator><description>&lt;p&gt;This is pretty strange. I mean, you (MS) didnt warn anyone that these issues will happen. Did &amp;nbsp;you do your verification properly before transitioning everyone over to Office365 etc? &lt;/p&gt;
&lt;p&gt;or did you not see a reason to inform people of these issues? &lt;/p&gt;
&lt;p&gt;We pay for a service, that was once working, and now broken. &lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3483693" width="1" height="1"&gt;</description></item></channel></rss>