Surface Hub calendar question

%3CLINGO-SUB%20id%3D%22lingo-sub-278548%22%20slang%3D%22en-US%22%3ESurface%20Hub%20calendar%20question%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-278548%22%20slang%3D%22en-US%22%3E%3CP%3ECurrent%20the%20Surface%20Hub%20calendar%20shows%20free%2Fbusy%20in%20scheduling%20assistant%20for%20any%20user%20looking%20to%20check%20the%20schedule%20and%20book%20the%20hub.%20I've%20had%20some%20requests%20to%20make%20the%20calendar%20public%20(essentially%20give%20read%20permissions%20to%20all%20users)%20so%20they%20can%20see%20who%20has%20reserved%20the%20device.%26nbsp%3B%20I%20can%20see%20this%20being%20helpful%20but%20also%20can%20see%20loss%20of%20meeting%20privacy.%26nbsp%3B%20I%20am%20also%20unsure%20if%20it%20can%20be%20done%20and%20free%2Fbusy%20is%20the%20only%20option.%3C%2FP%3E%3CP%3ESo%20my%20question%20is%20how%20are%20others%20handling%20the%20Surface%20Hub%20calendar%20and%20support%20of%20meeting%20visibility%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-282161%22%20slang%3D%22en-US%22%3ERe%3A%20Surface%20Hub%20calendar%20question%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-282161%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20Rick%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20calendar%20information%20can%20be%20configured%20with%20the%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2Fexchange%2Fmailboxes%2Fset-calendarprocessing%3Fview%3Dexchange-ps%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3ESet-CalendarProcessing%3C%2FA%3Ecmdlet.%20You%20can%20use%20the%20-RemovePrivateProperty%20and%20set%20it%20to%20%24false%20and%20have%20the%20users%20mark%20their%20meetings%20as%20private.%20Other%20useful%20switches%20are%3A%20-AddOrganizerToSubject%20%24false%2C%20-DeleteSubject%20%24true%2C%20-DeleteComments%20%24true%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks.%3CBR%20%2F%3ECezar%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-279556%22%20slang%3D%22en-US%22%3ERe%3A%20Surface%20Hub%20calendar%20question%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-279556%22%20slang%3D%22en-US%22%3EHi%20Rick%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20use%20a%20third%20party%20tool%20to%20supplement%20Outlook%20when%20booking%20meeting%20rooms%2C%20and%20this%20tool%20does%20tell%20us%20who%20has%20booked%20the%20room.%20So%20our%20default%20configuration%20in%20Exchange%20only%20shows%20free%2Fbusy%2C%20and%20the%20tool%20then%20tells%20us%20who%20has%20it%20booked.%3CBR%20%2F%3E%3CBR%20%2F%3EAssuming%20that%20you%20aren't%20hiding%20meeting%20information%20on%20the%20Surface%20Hub%20itself%20(unless%20of%20course%20someone%20books%20it%20as%20a%20private%20meeting)%20then%20giving%20the%20organisation%20read%20permissions%20to%20the%20Surface%20Hub%20calendar%20is%20no%20different%20from%20them%20going%20into%20the%20room%20to%20check%20the%20Welcome%20Screen%20and%20the%20meeting%20carousel%20on%20the%20Surface%20Hub%20itself.%3CBR%20%2F%3E%3CBR%20%2F%3ESo%20long%20as%20it's%20only%20the%20meeting%20subject%20and%20organiser%20that%20is%20made%20read%20only%20and%20not%20the%20content%20of%20the%20meeting%20invite%20itself%2C%20then%20personally%20I'd%20see%20no%20problem%20with%20this.%3CBR%20%2F%3E%3CBR%20%2F%3EAfter%20all%2C%20if%20the%20meeting%20is%20private%20they%20can%20mark%20it%20as%20such%20and%20it'll%20still%20hide%20the%20meeting%20details.%3C%2FLINGO-BODY%3E
Deleted
Not applicable

Current the Surface Hub calendar shows free/busy in scheduling assistant for any user looking to check the schedule and book the hub. I've had some requests to make the calendar public (essentially give read permissions to all users) so they can see who has reserved the device.  I can see this being helpful but also can see loss of meeting privacy.  I am also unsure if it can be done and free/busy is the only option.

So my question is how are others handling the Surface Hub calendar and support of meeting visibility?

2 Replies
Hi Rick

We use a third party tool to supplement Outlook when booking meeting rooms, and this tool does tell us who has booked the room. So our default configuration in Exchange only shows free/busy, and the tool then tells us who has it booked.

Assuming that you aren't hiding meeting information on the Surface Hub itself (unless of course someone books it as a private meeting) then giving the organisation read permissions to the Surface Hub calendar is no different from them going into the room to check the Welcome Screen and the meeting carousel on the Surface Hub itself.

So long as it's only the meeting subject and organiser that is made read only and not the content of the meeting invite itself, then personally I'd see no problem with this.

After all, if the meeting is private they can mark it as such and it'll still hide the meeting details.

Hello Rick,

 

The calendar information can be configured with the Set-CalendarProcessing cmdlet. You can use the -RemovePrivateProperty and set it to $false and have the users mark their meetings as private. Other useful switches are: -AddOrganizerToSubject $false, -DeleteSubject $true, -DeleteComments $true

 

Thanks.
Cezar