activesync
Latest
Microsoft explains Outlook.com outage, provides long-term fixes
It may have taken three days, but Microsoft has officially resolved its Outlook.com outage -- and it has both explanations and long-term solutions for affected email users. Trouble began with the failure of a caching service for Exchange ActiveSync. The resulting deluge of reconnection attempts promptly overwhelmed company servers; a slow recovery was necessary to avoid another meltdown, Microsoft says. To prevent repeat incidents, the tech giant is both upgrading its network capacity and implementing a more elegant error handling system. While the fixes likely come too late for some users, they suggest that Microsoft has learned a hard lesson about the fragility of online services.
Google to continue offering Exchange ActiveSync support on Windows Phones through July 31st
Today is the day that Google has been planning to shut off its support for Exchange ActiveSync, but it appears that the company has had a slight change of heart. Google has confirmed that it will allow Windows Phones to access Google Sync services for an additional six months, ending on July 31st. This move will allow Microsoft a little extra breathing room, giving the company more time to determine how to best resolve the concern that will affect countless Gmail fans that currently use Windows Phone as their primary driver; according to a blog post (linked below), Microsoft has indeed confirmed that it's working on building CalDAV and CardDAV support into Windows Phone. We reached out to Google and received this confirmation: "As announced last year, our plan is to end support for new device connections using Google Sync starting January 30, 2013. With the launch of CardDAV, it's now possible to build a seamless sync experience using open protocols (IMAP, CalDAV and CardDAV) for Gmail, Google Calendar and Contacts. We'll start rolling out this change as planned across all platforms but will continue to support Google Sync for Windows Phone until July 31, 2013."
Google will end mainstream support for ActiveSync in January
Google has announced that, as part of its "Winter Cleaning" initiative, it will be ending support for Exchange ActiveSync outside of Google Apps for Business, Government and Education on January 30, 2013. ActiveSync will continue to work past that date for those who already have it set up, but won't be available for new accounts. Going forward, Google is suggesting that its users turn to open protocols such as IMAP, CalDAV and the more recent CardDAV for their mail, calendar and contact syncing needs. In fact, we have a guide to using CardDAV to sync your Google contacts to your iOS device. In addition to dropping ActiveSync for non-Apps users, Google also intends to do away with some lesser-used Google Calendar features such as Smart Rescheduler and Add gadget by URL. You can find a FAQ covering the Winter Cleaning on the Google Sync end of life support page. [Via The Verge]
Exchange/iOS "meeting hijack" history goes back well before iOS 6
Yesterday, in discussing the new reports of meeting invitation issues between Microsoft Exchange and iOS 6 devices using ActiveSync, I mentioned that I recall having seen these sorts of problems in prior versions of iOS and OS X, albeit infrequently. The issue manifests as one recipient declining an invitation which mistakenly cancels the meeting for everyone, "hijacking" the meeting out from under the original organizer. My recollection was probably accurate, given the report below from a TUAW reader who prefers not to identify his former employer. The full rundown is worth reading, but here's the summary: iOS's implementation of ActiveSync, in iOS 6 and well before, may be doing some things (asserting ownership of meetings that in fact do not "belong" to the Exchange account on the iPhone) that theoretically should not be allowed under the protocol specification. Exchange, in turn, is not enforcing the spec and refusing these inappropriate requests as it ought; it's taking them at face value. The end result: meetings get dropped but neither vendor is apparently willing to take point on the issue. Our reader's story: The problem with iOS and Exchange is something that we discovered at my previous place of employment. It's a nasty bug and I'm sad to see that it persists. Before I sat down to write you, [I checked with] those folks to see if iOS 6.0 had made it better at all. They reported it was worse. With that in mind... We had a term for the problem. It was "meeting hijacking." It describes a scenario in which an iOS device could "hijack" a Microsoft Exchange meeting. The hijacking would make an attendee the organizer of the meeting and if they declined or deleted the meeting, Exchange would then send a decline to [all the other invitees] and cause fairly major issues. We first witnessed this problem around iOS 4.3, if I remember correctly. We were running Exchange 2007 for tens of thousands of users. We had the latest service packs and cumulative updates installed. (The problem also occurred in iOS 5.0 and higher, and apparently it's not fixed in iOS 6.0 either. It has also been verified against Exchange 2010, but more on that in a minute). To reproduce the issue, here's what we did: Using Outlook for Windows, create a meeting and add attendees. Make one of the attendees an email list that is EXTERNAL to the Exchange organization. That means it cannot be a distribution group in Active Directory. It needs to be a Mailman or majordomo list that is outside the Exchange org. The members of the external email list receive the invitation and accept it. The acceptance is written back to Exchange and put on the calendar. The iOS device owned by a member of the email list picks up the meeting and places it on the calendar. All is happy. At some point, the iOS device syncs the calendar via ActiveSync and suddenly becomes confused about who the owner of the meeting should be (the organizer, in Exchange-speak). The iPhone decides that its owner should become the organizer, since it has no idea who the real owner is, and syncs this property change back to the Exchange server. Exchange 2007 now has a disconnected copy of the meeting with a different owner. Exchange is agnostic about this. Now the iPhone owner declines the meeting for whatever reason. Exchange automatically generates a cancellation or decline notice and sends it out to everyone since the disconnected copy of the meeting has a different owner. This results in mass confusion and sometimes will delete the meeting from the other calendars. We verified this problem against iOS 4, 5 and 6 with Exchange 2007 and 2010. In Exchange 2010, Microsoft introduced a "calendar repair agent" that is supposed to detect this problem and resolve it. This calendar repair agent is a daily timer job. Microsoft did release patches on Exchange 2007 SP2 and up to correct some of the issues that are similar to this, but this particular problem was never resolved. Now for the dirty laundry. We worked for about two years with Microsoft and Apple on this issue. It may have been longer, I don't recall. We had a major support contract with Microsoft and reported this issue to them. I'll spare you the gory details. But the end result was this: The root cause is that iOS is able to convince ActiveSync to manipulate properties on meetings that it should not be able to manipulate (namely, the organizer of the meeting). Sometimes, it will make these decisions because for whatever reason it believes [these changes are] in the best interest of the user. Microsoft has an ActiveSync specification that calls out what properties should and should not be used during EAS communication. In our troubleshooting it was determined that Apple's manipulation of the organizer field is against the ActiveSync specification. However, ActiveSync will not stop iOS from doing this regardless of the fact that it is "against the specification." ActiveSync will happily accept the change and write the properties from the mobile device even if the ActiveSync spec says that Exchange explicitly should not do this. The end result: Apple claims that it's Microsoft's bug because ActiveSync lets it happen. Microsoft claims it's Apple's bug because they wrote code that makes it happen. Microsoft says they "told Apple not to do this but they did it anyway." Ultimately, we were of the opinion that it was Microsoft's bug to fix since the specification laid down rules of this nature yet is unwilling to enforce them. We pointed out to them that this seemed to be a security issue. They disagreed. Like I said, I spoke to my old colleagues and they confirmed that the problem still exists and with iOS 6, the meeting hijacks appear to have worsened. They are still in the planning stages of Exchange 2010 so I cannot comment on whether or not the calendar repair agent helps this issue in that particular environment. Thanks to our reader for contributing his experience. If you've got specific details on troubleshooting this issue or have run into it yourself, please let us know.
Exchange calendar oddity in iOS 6 may trigger meeting cancellations [Updated]
The iPhone's support for Microsoft's dominant email and calendaring Exchange platform is an essential part of iOS's appeal to business users. Integrating MS's ActiveSync mobile device connectivity into Apple's gear, which started back with iPhone OS 2.0 in 2008, helped make the upstart smartphone into a viable alternative to the dominant BlackBerry ecosystem (and look how that worked out). Update: See Thursday's post for more firsthand information on how Exchange and iOS have a history of not playing nicely. Unfortunately, ActiveSync has always been a mite quirky on iOS. While the core email sending and receiving functionality usually does as it should (with sustained support for push email a sometime exception), calendaring doesn't always fare as well. Delegation of calendar rights, access to third-party calendars and meeting invitation handling are among the sore spots that may cause issues for power users. It now looks like iOS 6 may be exacerbating some of these challenges. MacRumors highlights an internal memo from a "very large company" asking employees specifically not to upgrade their devices, as there may be some situations where declining a meeting invitation inadvertently sends a full cancellation notice to all the other attendees. In fact, I've seen this behavior before, only very rarely -- it came up once or twice on both iOS 5.1 and from iCal under OS X Lion over the course of a few months, while working with Exchange 2007 meeting invites -- but the current instantiation seems to be easier to trigger. Meetings with large numbers of attendees may be more problematic, and/or meetings where the organizer and the recipient are not part of the same Exchange organization. What can make this sort of issue more frustrating for both IT and device users is that these issues are usually intermittent, hard to reproduce and may hinge on very particular combinations of circumstances and Exchange microversions. There's a reason Microsoft sells expensive service and support contracts with its infrastructure products, and also plenty of reasons why hosted Exchange and alternatives like Google Apps are gaining ground on traditional in-house installations. You may be eager to try out the latest and greatest version of iOS, but if you're depending on your company's IT department to support your connectivity to the enterprise calendar system (to say nothing of VPN, file services, email and all the rest) then please do yourself a solid and check with your local gaggle of geeks before you upgrade -- not afterward.
Early iOS 6 adopters report problems getting Exchange push email: are you affected?
We all know about the central issue surrounding iOS 6. For the suits and ties among us, however, there's a potentially more glaring problem with Exchange support. Some users quick to upgrade to Apple's latest mobile OS report losing automatic push delivery of their email, requiring that they check for themselves to get any fresh messages. The issue isn't carrier- or device-specific, and attempts to reboot, reconfigure or restore devices are at best temporary fixes: what flows smoothly at first runs dry several hours later. Apple technicians are aware that the flaw exists, but it's tough to know if and when engineers will have a fix -- the company typically waits until it has a solution in hand before it goes on the record. We've reached out to Apple for a possible comment all the same. In the meantime, let us know if your Exchange access (or push data as a whole) is going awry. [Thanks, Daniel] %Poll-78044%
How your company will control your Windows RT Tablet
Windows on ARM really opens up the world of Windows to some great hardware. So great in fact that you'll probably have to buy one yourself if you want one to use at work. But a time will come where you'll want to get your work email and maybe even an app or two. You might already realize that by adding an ActiveSync email account to your tablet opens your new device up to restrictions by your system administrator -- like requiring a lock screen password or the ability to remotely wipe it – and in the Windows x86 world, your company uses things like an Active Directory (AD) Domain and its Group Policies to lock things down. But, AD isn't an option for Windows RT. According to the Building Windows 8 blog, Microsoft has instead built in the ability to connect to the company network to access apps, while at the same time, gives the admin the ability to control all the familiar AD security settings like bad password attempts, complexity requirements and can even verify your anti-malware software status. Of course if you leave the company or just want to use your tablet without entering a password, you can always break the tie and regain control of the security.
Samsung announces Galaxy Note 10.1 at MWC (update: hands-on photos!)
Samsung's announced another 10.1-inch tablet to join its burgeoning collection of slates. The Galaxy Note 10.1 is an S-Pen toting variant of the similarly sized-and-named Galaxy Tab. It's running Touchwiz-infused ICS on a 1.4GHz dual-core CPU with 1GB of RAM, but here's the answer to the question on everyone's lips: nope, you can't use it as a phone. Sadly you'll only have access to HSPA+, WiFi and Bluetooth 3.0, dashing our hopes of using this as our primary cellphone to annoy people on the train. The 10.1-inch WXGA (1280 x 800) display is nestled opposite a 3-megapixel rear-facing camera and beside a 2-megapixel one for video conferencing. S-Pen specific features include S Note for scrawling text, Shape Match and Formula Match (to digitize images and mathematical formulae) -- but more importantly is the ability to use Adobe's new Photoshop Touch and Ideas, which will both come pre-installed.If you'd rather use the slate as one of the world's largest sat-navs, you'll be relieved to know it's packing both GPS and Glonass. For the businesspersons of you out there, there's Exchange ActiveSync, on-device encryption, Juniper Junos Pulse and Cisco VPNs. It'll come in 16, 32 and 64GB variations, with a microSD slot for you to add up to a further 32GBs into the mix. It's clear that Samsung's bisecting its tablet business: purely touch-driven devices will now be branded as a "Tab" and anything with a stylus S-Pen will be suffixed with "Note." Pricing and availability are currently unspecified, but we'll do our best to shanghai that information out of a passing company rep when we see one.Update: We've added a gallery of hands-on photos just below.%Gallery-148870%Brad Molen contributed to this report.
BlackBerry Colt may be RIM's first QNX smartphone, will lack BES support out-of-box?
To many, a colt is a representation of rebirth and a symbol for youthfulness. Research in Motion appears to be in desperate need for exactly that -- a regeneration. It seems appropriate, then, that RIM may be launching the BlackBerry Colt, its first QNX-based "superphone," in the first quarter of 2012. This timeline will ensure the device launches at the expected time, according to rumors by BGR, but there's likely to be a few compromises to ensure it gets pushed out to market faster. The Colt is said to be undergoing internal testing with a single-core chip, contrary to promises of including dual-core CPUs. Additionally, the maiden voyage of the smartphone platform may be completely devoid of BES at the device's launch; it's taken longer than expected to rewrite the proper code to support QNX, and more time's necessary to bring it up to par with RIM's standards. What would the Enterprise customers do in the meantime? The alternative to BES is almost unthinkable: Exchange emails would be accessed by a preloaded version of Microsoft ActiveSync. Will the gamble yield greater returns in the long run, or will it remove the glue that still holds the company together?
Droid Pro update gets rolling, features microSD encryption and improvements galore
Motorola is now pushing out another update for its business Droid, replete with enhancements for the corporate-types and average joes alike. Among the most significant changes are AES256 encryption for internal storage and microSD cards, plus additional ActiveSync policies and VPN enhancements -- all certain to make your IT admins smile. Improvements don't stop there, with Moto refining voice call quality, stability, performance, and updating the Google apps. Hungry yet? The company says it's rolling out the update in phases, so check your eligibility often, because you may just be among the lucky first wave. Hey, there's nothing like a firmware update to get your week started on a positive note. Follow the source link for a full list of the new goodies. [Thanks, Tim]
Peek 9 is nine times faster than Pronto, adds PeekMaps, weather, Twitter, and Facebook
It's official. The latest Peek -- dubbed the Peek 9 -- is up and dancing with a full list of features. The hubbub boils down to speed improvements thanks to revamped software that claims to reduce lag and sluggishness experienced when connecting to newly enhanced Peek servers. While the hardware appears unchanged, it's still said to offer better reception and be 9 times faster (hence the name) than the Peek Pronto. The 9 comes pre-loaded with native Twitter and Facebook apps with ActiveSync support tossed in for Exchange. They've also added PeekMaps and weather apps to give you an idea of where you are in Google Maps and what the weather forecast is for that location. Rounding things out is the Streams RSS reader; the ability to view Word, PDF, and spreadsheet attachments; and a new Peektop Apps feature that lets you transform Peek into a "tailor-made mobile productivity machine," whatever that means. Peak 9 is priced at $69.99 or $99.99 plus two months of contract-free service (sorry, no lifetime service offering at the moment). After that, the Peek service will cost you $19.95/mth or as little as $9.95/mth for 24 months. Of course, with the 9's broader communications focus beyond just Twitter or eMail, we really have to wonder why anyone would buy this instead of a much smarter featurephone -- a Nokia C3, for example, can be had in the US unlocked for just $129.%Gallery-102788%
Exchange users on iOS 4 need an updated config profile
The path to ActiveSync nirvana for iPhone 4/iOS 4 users has not run all that smooth over the past couple of weeks. There were dramatic slowdowns for Google Apps and Exchange users who tried to synchronize calendar and mail data, although matters improved after the first day or two. Worse, some Exchange administrators noticed a drag on their servers associated with the influx of iOS 4 devices. Not so hot. Good news, though: Apple has a suggested solution for these issues, and all it requires is downloading a new Exchange/ActiveSync configuration profile to your device (or, in the case of corporate deployments, scores of devices) and installing it. The new profile doesn't do much except extend the timeouts for contacting Exchange servers, but in this case that should get the job done. If you've experienced this issue (or tried the fixed profile), let us know. [hat tips to Engadget, Macworld]
Google Apps phone-lock issues with iOS 4
In a strange twist with what appears to be a security issue, users of Google Apps who set up their accounts using the Microsoft Exchange settings (aka ActiveSync) may find that their iPhones have been set to auto-lock in one minute. I confirmed this after reading a comment from TUAW reader BigB who mentioned it in another post. Apparently this is due to the security certificates that Google uses with its Exchange servers. The servers can force security options on compatible devices, which your iPhone becomes once it is running iOS 4. To be clear: if you have a regular Gmail account and set it up using Exchange, this auto-lock requirement will not be triggered. But if you use Google Apps for your personal domain, it may. Also: Google Apps users have also reported problems setting up their iOS 4 devices. Mine kept telling me that the server (m.google.com) was unable to be verified even if you followed the instructions. Since I knew my information was correct, I went ahead and saved it. Email began syncing not long afterwards, but apparently the issue is still cropping up intermittently for some users.
I've upgraded to iOS 4: Now what?
You've upgraded your iPhone to iOS 4, and you're anxious to play with all sorts of new and wonderful features. Before you do that, take a few minutes to make sure everything is working as expected. Here's a list of things to confirm. They aren't in any particular order, and not all of them will apply to everyone, but some of them will, especially if you have "restored" your iPhone. 1. Launch the phone app and go to the voicemail tab. Make sure that it isn't asking for your PIN. If you're really cautious, you might even call your iPhone and leave yourself a voicemail just to make sure it's working as expected. Six more easy and necessary steps after the break.
iPhone OS 3.1 now enforces Exchange encryption policy, may block pre-3GS iPhones
The Apple Support forums are a'buzz with reports of several users upgrading to iPhone OS 3.1 and discovering a new "feature" which was not available previously. As mentioned in our comments, after upgrading to 3.1, some original iPhone and iPhone 3G owners with Exchange accounts are having trouble accessing their email. Apparently the server-side encryption policy option for mobile devices (only available as of Exchange 2007 SP1) is now being appropriately enforced. This is not affecting owners of the iPhone 3GS, due to the newer device's support for Exchange encryption. Prior to iPhone OS 3.1 the encryption policy was ignored for all models. Now that 3.1 is available, users are seeing this policy being correctly enforced and older iPhones without encryption support are left without access to Exchange services. I have yet to find any reports of issues with the iPod touch, but I suspect that it will also be affected by this software change. We're awaiting confirmation from Apple on whether this will impact the newly announced iPod touch models as well. While many are reacting to this issue as though it's a bug, and are reporting it as such, the reality is that the Exchange encryption requirement is a feature and the fact that it was not being correctly enforced was actually a security hole. IT administrators with Exchange 2007 SP1 servers and iPhone clients are probably going to be fielding an above-average level of incoming questions, but at least they can rest easy knowing that Exchange encryption is now working correctly. Cold comfort for their users, though. If you are running into this issue, the straightforward (though pricey) solution is to upgrade to the iPhone 3GS; or consider bribing your IT guy with Red Bull so he will disable the encryption requirement for mobile devices. But we want to hear from you; are you using an Exchange account? Can you still access it following the upgrade to 3.1? Which device are you using, iPhone or iPod touch; 3G or 3GS? Is this a little thing that means a lot to you from a security perspective or have you been left high and dry without access to critical email? Update: MacRumors points out that Apple has now covered this situation in a new KB article. [Via Broadband Reports]
Google: we're cool with Exchange on Google-branded Android phones
Okay, this gets a bit confusing, so bear with us. Back when HTC first unveiled the Magic, the company said that any Android device with a customized build -- and that includes adding support for Microsoft Exchange -- has to drop the "with Google" logo as per Google's rules. Indeed, that notion seemed to be validated by the all the international Android phones that have Exchange but no branding. Cut to present day and the T-Mobile's myTouch 3G, which looks to have both the "with Google" backing and Exchange support, contrary to previous assertions. Did the search engine giant soften its policy? We spoke with a company representative who told us, surprisingly, that it has "never been Google's policy" to deprive its branded devices of Exchange support, and that if another phone maker wants to add it and keep that logo plastered on the phone, that's A-OK. In all honesty, we never really put too much stock into the Google logo on the phone, but if it's really just been one huge misunderstanding that's prevented our G1 from having Exchange, well, we're gonna be quite nonplussed for many weeks to come.
DataViz brings Documents To Go to the App Store
Editing documents? On a phone? We're sure most iPhone users are a little taken aback by this prospect, but we assure you it's completely safe and devoid of artificial preservatives. DataViz just launched its Documents To Go suite for the iPhone, which lets you edit and create Word documents, sync work files with a desktop over WiFi, and view other Office documents with the iPhone's existing viewer -- it's not the first app to offer some of these functions for the device, but it's the first with this level of street cred. An optional version of the app also includes a Exchange mail client with ActiveSync for accessing and editing Word documents from email, which seemingly flies in the face of Apple's vague "don't mess with Mail or any of our other built-in apps" policy. The basic Documents To Go app retails for a limited time at $4.99, while the Exchange version goes for $9.99 -- and anyone who picks up the 1.0 version will get a free update to include Excel editing once it becomes available.
Rogers' HTC Dream and Magic aren't "Google phones," have Exchange support
Remember how we found out that there's a difference between the Google-branded Android firmware and its HTC-modified equivalent, and the latter isn't allowed to feature the silkscreened Google logo? The HTC version is way cooler on account of its Exchange ActiveSync support and the much-improved camera app; the only downside is that you can't flaunt that logo on the case, which -- let's be honest -- is totally meaningless to an end user (unless you're some raving Google fanboy / fangirl, and in that case, no amount of awesome customization is going to sway you). Anyhow, it's up to individual carriers to decide which versions of the devices they wish to launch, and Rogers customers will be excited to know that they're getting the logo-free HTC builds. That makes Canadian Dreams and Magics a whole hell of a lot more useful to business users than the G1s down in the States, and going forward, this is an issue T-Mobile probably wants to think about -- as long as the base Android code doesn't license ActiveSync, anyway.
Exchange-enabled HTC Magic explained: it's not a "with Google" phone
We've gotten the lowdown on that HTC Magic seen sporting Exchange support over in CNET Asia's capable hands, and as many readers opined, it's indeed a custom solution rolled by HTC without any Google involvement. Of course, HTC is no stranger to customizing OS builds loaded onto its devices; it already does this with every single Windows Mobile phone it sells, so we shouldn't be surprised to see some tweaks on its Android wares, either. Here's where it gets juicy, though: it turns out that Google forbids user of the "with Google" branding (as seen on the back of the G1, for example) when the build is customized, so the particular Magic that was being tested here lacked the Google name. Not all Magics are sold this way -- it's a carrier decision. Vodafone's version is Google-branded, for example, but in order to score the Google name they've got to comply to Google's standards for the software load.Some unlocked Magics (like CNET Asia's) are being sold in this sans-Google configuration, but if you like your Google apps, don't sweat it -- these devices still have GMail, Maps, and the like installed -- it's strictly a marketing and branding issue we're talking about here. In addition to Exchange support, the HTC-customized Magics include a reworked Smart Dialer with better contacts integration, a "much more responsive and full featured" camera app, and additional home screen widgets not found on the Google-ified Magics. We know which version we'd choose.
HTC Magic supports Exchange, Google says Android doesn't
A lack of Exchange ActiveSync support has largely relegated Android to the enterprise sidelines since its commercial launch last year in the G1, and while third-party apps have attempted to come to the rescue, there's nothing quite like a little first-party love to instill confidence in the world's IT managers. Strangely, CNET Asia noticed that its Magic seems to support Exchange -- indeed, it's listed right there in the mail setup and the reviewer reports that it works like a champ -- but a check with Google would have you believing otherwise. CNET's US bureau dropped Google a line to get the straight dope on the current Exchange situation and was greeted with an unhelpful response of "Android does not currently include support for Microsoft Exchange," going on to say that third-party devs are filling in the gap. Yo, Google, Magics in the field would have us believing otherwise, so do you want to clarify what's up here? [Via CNET]
