Forum Discussion
Exchange 2013 KB5008631 eDiscovery Deserialization of type Microsoft.Exchange.Data.PropertyBag+Value
Support had told me it was fixed in the "February update", but it's March now and no update has been released. I'm now working on a migration to Exchange 2019 and am not seeing the same problem there. I suspect that I'll be done with that before support informs me that the Exchange 2013 update is ready.
Support is telling me the fix has been scheduled for "the next CU". Since there are no more CUs planned for Exchange 2013, I guess that means the fix is scheduled for never. This is really poor of the Exchange team. They have the issue diagnosed and a code fix ready, and are choosing not to release it.
I wonder if they used a branch of code that didn't have the fix to create the March SU.
Uninstalling the SU did resolve our issues. It was the mailbox servers and the ecp web.config file specifically since that is the only one that was modified by the update.
Maybe they can get it right the next time. Hoping support meant the next SU and not CU since 2013 isn't getting any more.
- No, support has been very clear of CU vs SU. I even mentioned there are no more CUs and they still insist their documentation says it will be included in the next CU. I'm in the middle of a migration to Exchange 2019 and found the issue is not there. This may be a case of the Exchange team just showing disdain for customers that are on an old version.