This 2-day spanning behavior of single-day events is a known Microsoft issue, as per the Microsoft forum: https://answers.microsoft.com/en-us/office/forum/office_2016-outlook/all-day-events-span-two-days-in-outlook-2016/240e0d84-2d0b-4dce-9747-cbbf6539a32c. At the root of the issue is the definition of an “All Day” event. Historically, Microsoft has tended to define an “All Day” event as an event that starts at 12:00am and ends at 11:59pm. By this definition, an “All Day” event created in the EST time zone would need to be recalculated when viewed by someone in the PST time zone by subtracting three hours from both the start time and end time. So, an “All Day” event for 11/1/2018 (12:00am to 11:59pm) in the EST time zone would be viewed by a user with Microsoft Outlook in the PST time zone as 10/31/2018 9:00PM to 11/1/2018 8:59AM. This time window essentially turns an “All Day” event into a 24hr period that spans two days.
Option 1 - Reassignment of attorney to an office with matching Outlook time zone
In eDockets, each attorney has a profile. One of the parameters in the profile is the Office to which the attorney is assigned. The Office itself belongs to a time zone. Thus, by assigning an attorney to an office, that attorney inherits his assigned office’s time zone.
The 2-day event spanning problem occurs when the time zone of the attorney’s assigned office differs from the attorney’s Outlook time zone. Therefore, a viable workaround to the 2-day event issue is to reassign the attorney to an office with a time zone that matches his/her Outlook time zone. Matching the time zones between the assigned office and Outlook mitigates the Microsoft issue.
Option 2 - Adopting Microsoft Office 2016 C2R install for attorneys with issue
The feasibility of deploying the Click-to-Run (C2R) install of MS Office 2016 to attorneys experiencing this Microsoft issue is something that can only be assessed for the firm’s IT department, as there are several variables to be considered, such as Microsoft licensing models, third-party application compatibility and deployment logistics.