Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3177
  • Last Modified:

Resource mailbox's calendar shows the organizer's name instead of the subject in an Exchange Server environment (BUT SOMETIMES NOT)

Environment: Exchange 2010
Client: Outlook 2010 or Webmail


I am aware whenever we have a Resource Mailbox set to AutoAccept, the default Behaviour is to DeleteSubject and AddOrganizerToSubject when a meeting is sent. However some of my users managed to have the "real subject" displayed on the Calendar of the Resource mailbox. It means 99% on the Calendar is showing the organizer's name. But 1% of my users managed to have the real subject displayed.

All of my users have the same permission on the resource mailbox.

Please see >> http://support.microsoft.com/kb/2842288

Here is the meeting room settings >>

[PS] Microsoft.PowerShell.Core\FileSystem::\\domain>Get-CalendarProcessing -identity "My Meeting Room" | FL

RunspaceId                          : 0bb49036-b292-407d-9706-66f6e4b54aa7
AutomateProcessing                  : AutoAccept
AllowConflicts                      : False
BookingWindowInDays                 : 180
MaximumDurationInMinutes            : 1440
AllowRecurringMeetings              : True
EnforceSchedulingHorizon            : True
ScheduleOnlyDuringWorkHours         : False
ConflictPercentageAllowed           : 40
MaximumConflictInstances            : 100
ForwardRequestsToDelegates          : True
DeleteAttachments                   : True
DeleteComments                      : True
RemovePrivateProperty               : True
DeleteSubject                       : True
AddOrganizerToSubject               : True
DeleteNonCalendarItems              : True
TentativePendingApproval            : True
EnableResponseDetails               : True
OrganizerInfo                       : True
ResourceDelegates                   : {}
RequestOutOfPolicy                  : {}
AllRequestOutOfPolicy               : False
BookInPolicy                        : {}
AllBookInPolicy                     : True
RequestInPolicy                     : {}
AllRequestInPolicy                  : False
AddAdditionalResponse               : False
AdditionalResponse                  :
RemoveOldMeetingMessages            : True
AddNewRequestsTentatively           : True
ProcessExternalMeetingMessages      : False
RemoveForwardedMeetingNotifications : False
MailboxOwnerId                      : domain.com/My Meeting Room
Identity                            : domain.com/My Meeting Room
IsValid                             : True

So, How on earth some users managed to have the "real Subject" showing on the Resource Mailbox Calendar?
I thought once is set to AutoAccept, these fiels would be replaced to everyone.
Nobody is a Delegate of this Resource Mailbox. This is happening with several meeting rooms. Not just one.

Any ideas?
  • 4
  • 3
1 Solution
You're dealing with calendar event corruption and you need to set up recurring calendar maintenance.  I have no idea why MS doesn't enable this by default.

For the items you'll be reviewing, start by running this PowerShell command:
Get-MailboxServer | fl *calendar*

Depending on how frequently you want to run the mailbox repair, I have outlined two schedules (first two lines provided below). Choose one of those two and run the command.  First one runs checks/repairs daily at 10pm, The second one just runs it on Sundays.  If I have a server with problems, I run it daily.  If I'm just doing preventive maintenance, I run the weekly schedule.
Set-MailboxServer -Identity {Server-Name} -CalendarRepairSchedule 1.22:00-1.23:00, 2.22:00-2.23:00, 3.22:00-3.23:00, 4.22:00-4.23:00, 5.22:00-5.23:00, 6.22:00-6.23:00, 7.22:00-7.23:00 -CalendarRepairWorkCycle 1.00:00:00 -CalendarRepairWorkCycleCheckpoint 12:00:00
Set-MailboxServer –Identity {Server-Name} –CalendarRepairSchedule Sunday.19:00-Sunday.22:00

-Then run these two commands below-
Set-MailboxServer –Identity {Server-Name} –CalendarRepairMissingItemFixDisabled $true
Set-MailboxServer –Identity {Server-Name} –CalendarRepairIntervalEndWindow 120

Open in new window

You can optionally configure log file paths if you're curious to see what it is finding and fixing.  Those commands are:
Set-MailboxServer CalendarRepairLogPath {Path to log file folder}
Set-MailboxServer CalendarRepairLogEnabled $true
Set-MailboxServer CalendarRepairLogSubjectLoggingEnabled $true

Open in new window

The issue may be resolved after a single run, or it make several runs to get completely through and correct the issues.  I typically do the daily repair for customers having problems. I use the weekly schedule in order to prevent issues.
osagaranaAuthor Commented:
Hi jrhelgeson,

Thanks for your feedback.

I had a look at this and I was trying to figure out where in "Conflict Detection and Resolution" this issue would be:


It no one ever had this issue, I might try to see if this will improve things on my Calendars anyway.
osagaranaAuthor Commented:
Hi jrhelgeson,

Here is an important find >>

•CRA does not run against resource mailboxes.
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Here is an important find >>

•CRA does not run against resource mailboxes.
This makes sense. It would seem that the resource mailbox is the 'victim' of problems caused by dysfunctional user mailboxes.  i.e. 'The child is fine, it's the parents that are screwed up.'

Resource mailboxes do not schedule events, invite attendees, change times or cancel events.  Therefore it stands to reason that the problem wouldn't be with the resource object, but with the organizer.

I have had calendar repair fix oddball problems with calendar permissions (people losing permissions) that MS claims are never touched by the CRA,  This is why any time there are problems with calendars and scheduling, my first step is to enable maintenance.

As I stated earlier, I cannot fathom why MS wouldn't have calendar repair enabled by default, but no matter.  I enable it on every Exchange server I touch.
osagaranaAuthor Commented:
Yes. Thanks for your update.
I disabled

DeleteSubject : True
AddOrganizerToSubject : True

and then I enabled them again.
I am not confident this will fix.
Although the job of the Resource Mailbox with AutoAccept is Delete the subject and add the organiser on the subject. And the Resource mailbox is doing this 99% of the time.

I do not understand why during the AutoAccept the Resource mailbox failed to do its job.  
As you said could be the organiser's mailbox....anyway....

I am just a little bit concerned turning the CRA ON and having my users missing meetings and other people blaming me it was the CRA.
Is CRA really reliable? Does not make things worse?

I know meetings with CRA enabled follow exactly what the organiser's meeting says. If it is different in the attendee, the CRA will "fix" it. I am just unsure if CRA will make other big changes.

I have enabled CRA to solve numerous problems, and it has done so quite well.  In my experience, it is quite reliable and I've never heard of anyone complaining that it has created any issues.

What I can say is that every time I encounter calendar related problems, the first step I take is to enable calendar repair.  Once I know we are dealing with a stable platform (there are no serious problems with calendars) then I can start troubleshooting other issues with confidence that we're not overlooking anything.  In 90% of the cases, calendar repair fixes it.

Calendar repair doesn't make 'big changes' it checks for problems and fixes them.
osagaranaAuthor Commented:
I have not tested. However I will accept as the solution as I have nothing else to do.

Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now