Exchange Server 2013 CU22 | Meeting issue

Nitin Bhutani 1 Reputation point

Hello Expert,

We have a user A who has a delegated permission on mailbox B.

When User A sends a meeting from mailbox B's calendar to Mailbox C.

It shows Organizer name as Mailbox C for same meeting where mailbox is only attendee. It should have been shown as organizer name as Mailbox B.

It happens randomly.

Any help would be appreciated

Exchange Server Development
Exchange Server Development
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Development: The process of researching, productizing, and refining new or existing technologies.
506 questions
Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,338 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Lucas Liu-MSFT 6,161 Reputation points

    Hi @Nitin Bhutani ,
    Will this issue occur when user B sends a meeting invitation directly?

    1. Please try to log in to your mailbox on OWA and check whether the organizer of the meeting is displayed properly.
    2. Does user C use a mobile device to synchronize calendars through Exchange ActiveSync?
      According to the known issues released by Microsoft, when a user synchronize their iOS or Android device by using Exchange ActiveSync, they may unexpectedly become the organizer for a meeting to which they were invited.
      You can find the description of the issue in issue 1.2 in the article:Current issues with Microsoft Exchange ActiveSync and third-party devices


    If the response is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

  2. Nitin Bhutani 1 Reputation point

    Can we diagnose how active sync could create this issue?