I refer of course to Double-Booked Meeting Rooms in Office 365 (and how to avoid them).
In the space-time-convenience continuum which is always a struggle with different views of how to optimize your Microsoft Exchange calendaring experience, Outlook and Exchange 2016 do a good job of warning you at booking time of future conflicts with resources and recurring meetings.
But 1.) time management is a very dynamic entity so conflicts creep in at awkward times and 2.) it's easy to procrastinate and then lose track of future conflicts.
The best summary of the problem was here:
We are not happy; our users are not happy.
This brought us down a path of looking at simple means to accomplish checking for double bookings and (more importantly!) to make fixing double bookings actionable on the part of end users!
We found a serviceable script (from the author of the above quote) at Auditing Exchange Rooms for Double Bookings.
This has a few problems: it's very good at saying "yes there are double bookings in your resources, Mr. Administrator." And then what the heck is supposed to happen?
We thought it best to let the Exchange Administrator do what they're good at (managing Exchange, installing and maintaining software, handling permissions) and to create a mechanism to get the information where it is most needed -- into the hands of he affected meeting organizers.
To this end we've created Sumatra DBA: Double Booking Alert.
Sumatra DBA: Double Booking Alert
We see the following advantages of our approach:
- Installs and runs Server-side (no Outlook add-ins to distribute / manage)
- Pro-active instead of reactive
- No user training involved (notices come to the inbox of meeting organizers)
- Admin configurable
- Notifications configurable by site
Want in on early testing? Contact us.
1 comment:
We're not calling it DBA anymore -- we just call it the Sumatra Double Book cmdlet.
Post a Comment