Forum Discussion
Marcde
Moderator
Hello VJ,
we are facing this as well with 12.1.1 but with Exchange 2016 CU4.
Did you find a solution for that?
Regards
Marc
vjose79
8 years agoLevel 4
I contacted support and they confirmed that it was an issue with the product 12.1.1 but with a simple fix involving just renaming a value in registry. They informed that it would be fixed in the next release. Please contact support so that they are aware others having this issue as well. For reference my customers ticket number was 21855184.
Related Content
- 3 months ago
- 8 years ago
- 4 years ago