Feb 24 2021 02:58 PM
Feb 24 2021 02:58 PM
Originally the option to in Outlook to 'End appointments and meetings early' was a simple on/off option and was reflected in the registry with a DWORD 'endeventsearly' in HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Outlook\Options\Calendar
Now a recent update now allows users to select 'End early' or 'Start Late' and the DWORD has been replaced with String Value ShortenEvents that can have the value 'End_Early', 'Start_Late', or 'None'.
However the Office Cloud Policy Service still only shows the previous settings which applies only the DWORD which now has no effect. Can you please update the Office Policy Service to reflect the new setting in Outlook so we can push this out to our users?
Mar 03 2021 05:25 AM
Mar 03 2021 09:51 AM
@Matt_TheTrust Looks like it was a fairly recent change added to the "Current Channel" release track on Jan 26th.
Version 2101 (Build 13628.20274)
If you can prevent your staff from receiving this update, then you should be able to keep using the old values / GPO settings. If not, then you may need use your GPO to push the reg values more manually. Of course in my case, GPO isn't much help cause no one is coming to the office and connecting to the DCs right now which is why I was hoping to push this out via the Office Cloud Policy Service, but it still hasn't been updated and doesn't have any way of pushing just regedits like GPO
Mar 18 2021 02:33 PM
@Joe SavageI can't thank you enough for posting this. I have been so frustrated trying to resolve this after the update broke our GPO. If you don't mind sharing, how did you come to this conclusion. As in how did you find out a string value "ShortenEvents" needed to be added to HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\Office\16.0\outlook\options\calendar with the values you supplied?
I tried changing it manually in Outlook and comparing the registry before and after, but didn't find this.
Either way thank you!
Mar 18 2021 02:49 PM
Mar 18 2021 03:06 PM
@Joe Savage Well I want you to know you are my hero for the next week at least. We had just rolled this out company wide and made a big announcement about it, only to have it break a few weeks later. I spent hours with Microsoft support to no avail and you just solved it for me.
Thank you for explaining the method behind your troubleshooting! This is the first time I have bothered to post, but this was too helpful to not say thank you.
Mar 19 2021 04:46 AM
@Joe Savage thanks for this post! It has helped restore a bit of sanity after troubleshooting for at few hours and not understanding why Outlook is not reading the registry values I have been setting! As you say, some recent change in Office seems to have broken this.
We are hoping to roll out this feature to the company via GPO but I guess we'll have to wait. I am unable to make it work with GPO at all. Neither via the ADMX template values, nor via registry values via Preferences. Strangely, when setting the feature via Outlook GUI it works fine, despite the fact that the very same registry value is written to registry that I have been deploying via preferences.
Mar 22 2021 03:00 PM
@Joe Savage this is very insightful. I have been trying to set this up for our business but have realized I am really a novice with respect to deploying registry settings via GPO. My hope is MS will fix/unbreak the policy at some point. I will keep trying the registry adjustment with what you have written. Thank you.
Apr 02 2021 09:45 PM
This is a new registry key