Set-CalendarProcessing -MaximumDurationInMinutes

In Easy365Manager, you can enter a set duration in the “Maximum duration (hours)” box to define the maximum duration for meetings that can be scheduled in a specific meeting room.

Watch a quick video guide here.

You can quickly locate the setting by opening up properties for a Room user, selecting the Mailbox tab, and clicking on Room Settings. This opens up the following form, where you find “Maximum duration (hours)” in the Booking Processing section:

In Easy365Manager, the “Maximum duration (hours)” setting corresponds to the ‘MaximumDurationInMinutes’ parameter of the Set-CalendarProcessing PowerShell command; however, Easy365Manager has users set the duration in hours instead of minutes.

The PowerShell command “Set-CalendarProcessing -MaximumDurationInMinutes” is used to restrict long meetings in a certain room:

Set-CalendarProcessing -Identity "Brooklyn-MeetingRoom-6.2" -MaximumDurationInMinutes 120

The advantage of using this command lies in its ability to optimize meeting room utilization. By imposing duration limits, organizations can prevent meeting rooms from being monopolized by lengthy meetings, making the rooms available for more teams to schedule their meetings efficiently. This contributes to better resource management and improved collaboration, as it ensures fair access to meeting spaces and prevents unnecessary booking conflicts.

Please notice that the GUI of Exchange Admin Center insinuates that the “Maximum duration (hours)”-setting (MaximumDurationInMinutes) is ignored if the “Automatically decline meetings outside this limit” setting (EnforceSchedulingHorizon) is disabled:

This is absolutely not the case. Exceeding the maximum duration (hours) limit in a booking request is denied no matter if EnforceSchedulingHorizon is true or false.

It’s interesting that the people implementing the Exchange Admin Center management tool have not read the documentation or tested the settings before designing the user interface.