My ical events showing up as "new events" on my ipad and iphone when synced with exchange?

For what it's worth, I also have the same address book problem as openkimono, I just didn't connect the address book problem to the calendar problem. I did not sign up to iCloud, so I'm not sure it's in the mix.

Lion 10.7.2

iCal 5.0.1

Exchange 2010

iOS 5 on iPhone

I have the same issue - does anyone at Apple listen or comment when there is a problem? It is unworkable! Please sort ....

I am running the latest version of ical and lion on a new £2K MacBook - I have a hosted MS Exchange 2007 account - and this issue is driving me nuts. I have spoken to Apple Care (less) who have advised me that this is not really an issue as they have seen very little traffic on it. Apple Care went on to tell me they did not support exchange and that their software was only compatible with Exchange 2010 which rules me out! I notice that some of the posts indicate that they are using 2010 and still experiencing the issue which makes a mockery of their comment. I found them complacent and not that interested. I have used Mac for two years with relatively few issues - but LION is a disaster with issues experienced with printers, iPhoto Themes, iPhoto importing of pictures and on and on.

I have contacted my Hosted Exchange provide (Cobweb in the UK) who reported that they had received no calls on this and that they would not help making any transition to 2010 - not that it appears that would make any difference.

Buying a new MacBook and upgrading my other to LION was a huge mistake ..... if anyone comes across any solution please advise. In the meantime I will have to put the appointment details in the location field and then edit and resave when the event has reverted to New Event ... once you have resaved it, it appears to stick (thank god).

Sort it out Apple and stop launching unstable systems - the whole reason people move to Apple is because they are meant to 'just work' - 2 years ago I think this was true but now I am not so sure. Lose this USP at your peril.

Have the same issue.

Lion 10.7.2

iCal 5.0.1

Exchange 2007

iOS 5 on iPhone

Events created on iCal are retitled "New event." Notes, alarms and free/busy/outofoffice are retained.

Lion 10.7.2

iCal 5.0.1

Exchange 2010

Events created in Outlook, or on my iPhone, are not affected.

Count me in. This is so frustrating because I can't remember what the new event is supposed to be! Gaa!

My workaround for this problem is to initiate the calendar entry using the "+" in the upper left corner of the iCal window. I enter something like "Lunch with Mike at 12 pm Dec 12" and the event shows up in my calendar with the Info window open. I add the rest of my info (e.g., location, alert, etc.) and then hit "Done". So far I have not had any appointments revert back to New Event.

Hey guys, I'm new to this forum - does Apple watch this forum? How do we submit this as a formal issue?

same problem here.

we are all waiting for the FIX this is a huge problem...

I resolved the address book issue finally. In address book in OSX, Preferences -> General, make sure that the default account is selected for the Exchange account so then all address book entries will propogate from OSX to iOS devices correctly.

This does NOT fix the iCal issue extensively documented in this thread however....

The fix a friend helped me with is to just use iCloud to sync iCal and not Exchange. I edited all my events in iCal to be associate with the new iCloud calendar I created and made iCloud my default calendar. I no longer get the problem with appointments reverting to "new event." I also diabled Exchange Calendar on my iPhone.

Unfortunately, for many of us, abandoning Exchange isn't an option. My work IT group is definitely not going to move 14,000 people's Exchange calendars to iCloud....

Hey Apple,

Fix it!

Has anyone gotten a single acknowledgment from Apple that they are aware of the problem and are working on a fix? According to the Radicati Group, more than 300M people use Microsoft Exchange. Seems like a reasonable problem to fix.

From apple in regards to bug filed, everyone on this chain should file a bug with apple to get their attention however...

This is a follow up to Bug ID# xxxxxxx. After further investigation it has been determined that this is a known issue, which is currently being investigated by engineering. This issue has been filed in our bug database under the original Bug ID# 10186938. The original bug number being used to track this duplicate issue can be found in the Related Problem section of your bug report's Problem Detail view.