Forum Discussion
Rolling back from Exchange 2019
Hello everyone - bit of a long shot, but hoping someone can advise. TL;DR: Is it possible to introduce a Exchange 2016 in a 2013/2019 co-existence and move everything to that to bin off a trouble...
Hi Carlos_2023,
I'm afraid we didn't. We did have a ticket with MS that went back and forth trying various things, but nothing seemed to improve the situation, and no one was really able to put their finger on the root of the problem.
In the end, we migrated everyone to Exchange Online which has shown to be an improvement. After the fun and games with Exchange 2019, we've not touched it since - we've only used 2016 for on-prem, or in most cases migrate to Exchange Online as that seems to be the way things are heading at the moment anyway. We didn't try introducing a 2016 server in the end as we didn't want to complicate things even further.
Sorry I'm not much help with this - although it seems most people seem to run Exchange 2019 without these issues, I can sympathize with you - it is incredibly frustrating. Have you raised a ticket with MS support?
I'm afraid we didn't. We did have a ticket with MS that went back and forth trying various things, but nothing seemed to improve the situation, and no one was really able to put their finger on the root of the problem.
In the end, we migrated everyone to Exchange Online which has shown to be an improvement. After the fun and games with Exchange 2019, we've not touched it since - we've only used 2016 for on-prem, or in most cases migrate to Exchange Online as that seems to be the way things are heading at the moment anyway. We didn't try introducing a 2016 server in the end as we didn't want to complicate things even further.
Sorry I'm not much help with this - although it seems most people seem to run Exchange 2019 without these issues, I can sympathize with you - it is incredibly frustrating. Have you raised a ticket with MS support?
