I've been charged with migrating to exchange 2016.
I've also been charged with securing the existing exchange 2010 platform that exists.
There's 2 front end HUB/CAS servers and 3 backend mailbox servers.
all 2008 r2 with latest updates and cu30.
One of the main lacking security items on this legacy platform is ciphers, ssl/tls versions are way behind and i am not sure the best way to do this to not break client access and cause a problem with exchange itself.
I've found that IIS Crypto tool is an easy way to comply with the latest ciphers and tls/ssl settings.
Is this true? Any issues with 2008 r2/exchange 2010 that I should be aware of?
I'm going to test this in a lab, but that isnt exactly a mirror image of our production env.
https://dirteam.com/dave/2015/06/07/checking-security-protocols-and-ciphers-on-your-exchange-servers/
<style><br _moz_dirty="" /></style>