Forum Discussion
msosupport
Sep 02, 2018Copper Contributor
Outlook 2016 defaults to an end date on recurring appointments now - need "no end date" fix
I have just found out - the hard way - that the update from 25th June has changed the way recurring appointments work in Outlook 2016. They all used to default to "No end date" which suited me ju...
wroot
Sep 03, 2018Silver Contributor
You speak like you know the internal workings of Exchange/Outlook. What you describe is very inefficient from a programming standpoint.
Personally i don't remember what the default setting was. Currently it defaults to some date indeed. There is probably a reason for this change, but i can't think of one realistic. Other than some users complaining that they didn't want their events to go forever.
Craigmlew1981
Feb 18, 2019Copper Contributor
You're right. Really, in cached mode, as a user scrolls through their outlook calendar it fetches that info from the exchange server only when they keep scrolling past the point that their client is set to cache (30 days, 60 days, 1 year, ect). This would be rare and still, not a big deal at all. Exchange Server can handle this easily. It's actually nothing to even talk about. I suspect Microsoft introduced this due to many large organizations migrating to O365. I wouldn't doubt that Microsoft has found that many custom internally programmed apps at various orgs are fetching the calendar data inefficiently and this is creating a burden on the O365 exchange servers. (that "could" be the cause. Various apps endlessly pulling this info via EWS calls). But yeah, under normal scenarios, this is NOT a problem. I'd put my money on O365 and various orgs taxing Microsoft's Exchange servers with inefficient programming. That's my guess.
Craig
Microsoft Certified Systems Engineer (Exchange 2010 and 2013)
Microsoft Certified Systems Engineer (O365)
Craig
Microsoft Certified Systems Engineer (Exchange 2010 and 2013)
Microsoft Certified Systems Engineer (O365)