Forum Discussion
Network_center1
May 24, 2017Nimbostratus
Hi, we have the same problem, since we migrate to Exchange 2016. A case is open with F5, that's difficult to reproduce the error because it's very random.
Thank's to update, if you solved it.