Solved O365 - Room Resource - Calendar Event
-
So this is a normal question, but I want to confirm before I go and try the powershell script commands that say "this is what you do to make X happen"
We have a room resource, that it accepts calendar events (for the sole purpose of tracking team meetings).
But what this calendar does is replaces the subject, with the organizer name. We want the subject and details to stay on the event.
This says to run a powershell command to change the settings, but I wanted to confirm if anyone else has had to do this.
-
No response at all, I guess it's not a normal question...
-
So I've found the solution to this problem.
First start with PowerShell locally (your onsite exchange server or PC)
Get-CalendarProcessing -Identity [email protected] | Fl
This will list the currently set configuration for this room resource - verbose.
Next run
Set-CalendarProcessing -Identity [email protected] -DeleteSubject $False -AddOrganizerToSubject $False -DeleteComments $False
DeleteSubject and AddOrganizerToSubject are pretty straight forward to understand. The DeleteComments actually leaves the body of the calendar event intact.
Which by default for my resource was set to True, meaning we'd have no details on any events scheduled to this room resource.
Hope it helps.
-
Just wondering, why did the calendar replace the subject with the organizer name in the first place?
-
@Dashrender It's a default setting with Office 365 for privacy settings as far as I can tell.
-
@DustinB3403 said:
@Dashrender It's a default setting with Office 365 for privacy settings as far as I can tell.
Interesting. I wonder if that's the case for calendar's where the viewers have full access rights?
In On-premise Exchange, if someone doesn't have at least reviewer rights, then they just see that the space/time is busy - perhaps they can see the owner of the slot. But since our entire staff have editor rights to our shared calendars like these, they can see the subject and any comments.
I wonder if giving them reviewer rights would have solved it.