Originally Posted by AppleInsider
However, Apple plans to discontinue the use of Mac OS X Sync Services with its subscription MobileMe service on May 5 for all users. The change is already in place for users who moved their account to the new version of MobileMe calendar, which came out of beta last October.
Originally Posted by solipsism
Even if they do I don’t know if discontinuing the sync makes sense. I can kind of see discontinuing support for it, but even then I’d think that some support would be needed. Seems premature to be doing this as I use this feature often so I don’t have to physically sync my devices to get the new calendar, bookmark and contract info, not to mention all the great things it backs up to restore your desktop.
Why does everyone keep repeating this falsehood? Yes, iCal syncing to MobileMe is moving off Sync Services on May 5th and swithcing to calDAV. But why does everyone (MS, AI, even MacWorld) keep stating it as if all Sync Services are going away May 5th. If you aren't on MobileMe, iCal will still sync to your devices via Sync Services. And all of your other data (contacts, key chains, bookmarks, etc) are still synced to MobileMe via Sync Services.
Can anyone point to an Apple document that states otherwise? I have read that iSync is going away in Lion, but I am unclear if it's just the iSync application or all of Sync Services? And that will be long after the May 5th deadline.
To solipsism's point, there are a lot of uses for Sync Services besides syncing to MobileMe, including many of Apple's own functionality:
- Syncing contacts and calendars to a non-iOS iPod with a screen (except the latest, crippled, generation of nano).
- Using Apple's iSync to put contacts and calendars on a non-Apple phone (because Apple uses iTunes to sync the iPhone)
- FileMaker's (Apple's) Bento application which accesses the database Sync Services maintains.
- And worst of all, iCal itself won't get event and alarm updates unless you have it open. Prior to the calDAV move, if I set and alarm on another Mac, the Mac I'm working on will get the calendar update in the background and the alarm will go off like it's supposed to. With the move to calDAV, you need to keep iCal open all the time to get those updates. Otherwise your alarm will never go off.
Apple's mistake isn't in moving calendar data syncing to calDAV. That's a good thing. It's in putting the calDAV syncing into iCal, requiring iCal to always be open for any of the above functions to work. If they had implemented the calDAV syncing into the MobileMe System Preference so that it syncs continuously in the background, that would ensure your sync databases were always current and your iPod, phone, and Bento applications always had the most recent data.
I'm hoping that on May 5th Apple will release an updated MobileMe System Preference which will include putting the calendar syncing back where it belongs. I don't need Address Book, or Keychain, or Safari open to have those databases kept current with the data in the cloud. Why do I need iCal to stay open just so my alarms will go off when they are supposed to?
Originally Posted by HeavyD
--"For Outlook for Mac 2011 users who sync their iOS device with Sync Services via iTunes, calendars will remain up to date. But users who sync their iPhone or iPad calendars with MobileMe will not have them synced to Outlook 2011 with SP1."--
This is not clicking in my brain. I'm not getting it. Could someone please explain this to me? If, I have MobileMe and I connect Outlook Calendar via Sync Services and my iPhone syncs directly with MobileMe, what is the issue? If someone is using actual Exchange their Calendar would sync directly with their iPhone. What am I missing?
MS did a very poor job of explaining that part...
If you have MobileMe and your iPhone syncs directly with the cloud (ie, not via the USB connection to iTunes), your iPhone will not get the calendar updates from Outlook.
There are hidden sync databases that house your contacts, calendars, etc. In the past, Sync Services kept all this in sync with the MobileMe cloud. But on May 5th (sooner if you manually switch now to the new calendar), your calendar data will no longer be syned by Sync Services (aka, the MobileMe System Preference). It is synced by the specific application, in this case iCal, not in the background by the system (see above why I think this is a bad design). Since you are using Outlook, not iCal, your local calendar information is no longer syncing with the cloud because Sync Services isn't doing it anymore. So, if your iPhone is syncing with the cloud, no Outlook updates for you. And your iPhone updates won't make it back to Outlook either, because there is nothing syncing the cloud to that hidden sync database on your Mac.
But if you sync your iPhone via iTunes (with the dock connector), iTunes will sync it to those hidden databases where Outlook can then retrive the updates. Likewise, Outlook changes can sync back to your iPhone via the sync database and iTunes. If you don't have MobileMe, then all is good. But if you do have MovileMe, you still have issues if you make calendar updates on the web version of iCal because there is no way for those updates to get back to your Mac...or is there?
Sync Services won't sync your calendar to the cloud after May 5th. Neither will Outlook. But iCal will. So what if I leave iCal open all the time? I'd love for someone to test this (I don't have OFfice 2011). It works for my non-iOS iPods. If iCal isn't running, the hidden databases aren't updated with any calendar updates made elsewhere, and my iPods don't get event and alarm changes. But if I leave iCal open (or open it right before syncing my iPod) then iCal will update the hiddle database and iTunes can use Sync Services to retrieve the updated info and put it on my iPod.
Would a similar technique of simply leaving iCal open all the time also fill the gap between the cloud and Outlook, the gap Apple created when they moved calendar syncing from an OS operation to an application operation? Can someone test it?