Hi Everyone,
We have an application which sits between potentially multiple 100's of Room Scheduling devices and Exchange Server. All of the Room Schedulers will communicate with this single application which in turn communicates with Exchange on their behalf.
The application ran fine with Exchange 2007, but as we have moved to Exchange 2013, it is now having frequent 9646 Errors.
What changes in Exchange 2013 are likely to be introducing this condition?
Can the configuration of Exchange 2013 be changed in an acceptable (MS Supported) way to address this issue?
Are changes required on our application side to live with Exchange 2013 (and 2016 and future)? If so, can anyone recommend a discussion on how best to architect such an application?
Let's start high level on this, but if you need further information about how the application is architected we can discuss that later.
Thanks for any information you can give us.
Dan