Forwarding Exchange calendar invites from calendar app not working

Question

We have Samsung Windows 8 phones and have discovered a problem with forwarding calendar invitations from within the calendar app on Exchange 2010 / ActiveSync.
User A on Exchange 2010 will create a new meeting request and send it to user B. User B will accept the calendar invitation on their Windows 8 phone. User B will then go into the calendar app on their phone and forwards the calendar item to User C. User
C does not receive anything nor does User A receive a notification that their original meeting invite has been forwarded. No error messages are shown on User B's phone. It's as if the forwarded item simply vanishes.
With the same scenario as above, if User B does NOT initially accept the meeting invite from User A and instead immediately forwards the invite to User C from within the MAIL app on his phone, before accepting the meeting, User C receives the invitation
as per normal and User A receives notification that their meeting request was forwarded, as expected.
If User B does NOT initially accept the meeting invite from User A, but then goes into the calendar app on their phone and attempts to forward the meeting request (showing as tentative as they have not accepted it yet), User C still does not receive anything
and User A does not get notification.
This appears to be a bug within the Calendar application on Windows 8 phones as forwarding meeting invites works fine from within the Mail app (provided the user has not accepted the meeting yet - once the meeting has been accepted in the mail app, the item
"disappears" and is no longer accessible except from within the Calendar app).
This is a pretty major issue with heavy calendar users (e.g. executives) as they will be forwarding accepted meeting requests from their calendars and without receiving any error messages will assume the forwarded invitation has gone through, when in fact
it hasn't.

Answer 1

We have reproduced this issue internally and are filing a bug to get this issue fixed.  As soon as we have an update to this, we will report back on this thread.  Thank you for raising this issue.