Currently Being ModeratedSep 27, 2012 4:14 AM (in response to BishopTJ)
Ok, looks very similar to an issue we have at the moment.
What's your impression is Microsoft the right addressee for this?
We did EAS with IOS Devices since a long time quite flawlessly...until IOS 6 came.
Does anyone know if Apple is aware of this issue?
By the way, from what I have found the thing goes like this:
User creates an appointment and invites a number of colleagues.
A change occurs (maybe a delegate has accepted the appointment or the room has changed) and the iPhone offers in the calendar app the option to approve or accept the change by clicking an "OK" Button.
This results in two new messages to be transfered, one is the cancellation and the other the invitation with the poor guy that used the iPhone as owner of the appointment.
That's my impression at the moment.
Currently Being ModeratedSep 28, 2012 2:04 AM (in response to Buddha_ac)
Ok, to clarify: So far I am not able to reproduce this with my own device. That leeds to the impression, that it could be connected to user behaviour (...holding the device wrong - Thanks Paul ) or the installation or configuration of the mobile device...!?
Currently Being ModeratedSep 29, 2012 7:30 PM (in response to Buddha_ac)
We have another thread going over here as well: https://discussions.apple.com/thread/4368289?start=0&tstart=0
Currently Being ModeratedOct 1, 2012 11:01 AM (in response to BishopTJ)
Our Microsoft TAM has acknowledged that iOS 6 has caused this issue that is being seen by many of their customers. No details on the exact cause and no ETA for resolution
Currently Being ModeratedOct 1, 2012 4:40 PM (in response to BishopTJ)
We are seeing it with Exchange 2007 SP3 RU6. So far, no joy with Microsoft Premier Support. They are directing us to Apple.
Currently Being ModeratedOct 2, 2012 12:08 AM (in response to BishopTJ)
Thought so, thus I postponed triggering our TAM.
Thanks for the update.
Currently Being ModeratedOct 2, 2012 3:33 AM (in response to BishopTJ)
I am going contact Enterprise AppleCare. Does anyone know how to reliably reproduce the issue?
Currently Being ModeratedOct 2, 2012 3:51 AM (in response to CaptainJK2020)
Not really, I didn't succeed in trying to reproduce this with my devices.
Seems to be connected to an "infected" device. Maybe this could be a result of the update process.
I did mine over the air and the colleague who is able to reproduce this issue has done it by using itunes with the inevitable multiple download-tries of the image...
Just to re-emphasise, this is only my impression and I am far from beeing fully convinced about that.
Cross my fingers.
Currently Being ModeratedOct 2, 2012 6:16 AM (in response to CaptainJK2020)
For us, this is only happening on meetings that contain a large number of attendees (50+). Our internal testing within IT that has contained 15 attendees does not generate the issue. We have been able to witness this issue while Microsoft was performing detailed logging so Microsoft has all of the details that we can provide them. Our TAM has advised us that they are engaged with Apple support on this issue. Many VIP Microsoft customers are affected.
Currently Being ModeratedOct 2, 2012 7:29 AM (in response to BishopTJ)
@BishopTJ: That's promising that you were able to reproduce the issue while detailed logging was running. We are pursuing this with MS and Apple too, but you are ahead of us. Beyond sending the invitation to a DL with 50+ members, what other steps did you need to take to trigger the reproduction? Did people have to accept the meeting in OL or on their iDevice? Did a person need to do something to the meeting on their calendar to trigger the cancellation message?
Thanks for any details you can provide. I think the more of us who are reporting this issue and can reproduce it, the better.
Currently Being ModeratedOct 2, 2012 3:06 PM (in response to CaptainJK2020)
Actually, the people that are running iOS 6 are seeing another calendar oddity. They are receiving multiple alerts to confirm calendar appointments and are able to confirm the same appointment twice or three times. We haven't been able to narrow down the exact action that the user takes that generates the cancellation. A couple of users have even reported that they didn't even access the appointment through their device (cannot confirm and seems unlikely).
We did witness yet another issue today, someone outside of our organization running iOS 6 was able to generate a cancellation for an appointment that was created by someone within our organization and the cancellation notice was received by people inside and outside of our organization. We captured that in logging and sent to Microsoft as well. Still no direction yet, but as soon as we get more information I will post it here.
Currently Being ModeratedOct 2, 2012 3:53 PM (in response to BishopTJ)
Similarly in my company, the invitee who improperly issued the cancellation to all other invitees said that she didn't touch the meeting in question. Upon further discussion, she said she may have scheduled an overlapping meeting, but still insisted that she did not touch the meeting that she improperly canceled.
I have a Premier ticket open with Microsoft and an Enterprise AppleCare ticket open with Apple. I'm still on the ground floor with both of them. I will also continue to post updates to this thread.
Currently Being ModeratedOct 3, 2012 7:46 PM (in response to CaptainJK2020)
I haven't seen the issue, but my question would be why is Echange allowing an invitee to cancel a meeting for everyone?
Currently Being ModeratedOct 3, 2012 9:59 PM (in response to NetMage)
In this case the exchange actually just transports messages. These messages are interpreted by a Client (Outlook...), processed and transmitted to the Database.
The mobile device creates somehow malformed messages (I assume...) to the other invitees, where the respective invitee appears in the Organisation field. Together with the ID of the element is this what allows him to cancel the appointment. Strangely I could observe, that the invitee with the trouble causing device and the original Organizer still find the element in their calendar.