Exchange - Conference Room Not Accepting Meetings

Issue:

Our main conference room has stopped accepting / declining meeting requests.

Other rooms are still behaving normally.

No deliberate changes have been made.

No tenant config changes have been made.

• Working room: [e-mail]
• Broken room: [e-mail]

Compared the Exchange settings for both rooms and they are the same (except for access / delegation).

Analysis:

1. To understand your issue better, please share some more information:

- Is your organization using Hybrid Exchange or Exchange Online.

- Please share the output of following command:

Get-CalendarProcessing <Identity> | fl AutomateProcessing

Result from the customer:  AutomateProcessing : AutoAccept

1. Please refer the below article and provide me with the output of the commands mentioned:

https://support.microsoft.com/en-in/help/2005631/resources-in-exchange-don-t-respond-to-meeting-requests

1.) Please connect to Exchange online PowerShell using below commands:

Set-ExecutionPolicy RemoteSigned

$UserCredential = Get-Credential

$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $UserCredential -Authentication Basic -AllowRedirection

Import-PSSession $Session

2.) Please run the below command

Start-Transcript

3.) Run the commands mentioned in the article:

get-mailbox <Identity>| fl ResourceType,RecipientType,RecipientTypeDetails,IsLinked,LinkedMasterAccount,IsShared

Get-CalendarProcessing <Identity> | fl AutomateProcessing

Get-CalendarProcessing <Identity> | fl *policy*,ResourceDelegates, ForwardRequestsToDelegates

4.) Run the below command:

Stop-transcript

5.) After running the command in step 4, please collect the transcript file from the specific location and send us as an attachment.

Resolution:

Checked the Calendar Processing for room mailbox: [e-mail] and found no discrepancies.

2: Tried to toggle the -Automate Processing to 'None' and back to 'AutoAccept'

3: After performing the New-MoveRequest -Identity [e-mail], we were able to resolve the issue.