I've inherited my exchange server and it's always operated un-secured but if I use https in owa instead I can continue with an invalid cert. (so the firewall is already open)
I was wondering apart from the cost what world of not so nice stuff am I about to fall into if I decided it's worth securing. I can see from the event logs the server has been complaining about unsecured transports and fdqn issues but as it performs fine I've not to dared poke it. (like my life dung free)
I see that I have to wrestle in the cmd line for a while. (why btw why, when adding an ssl cert for 99.9% of exchange admins is a must do they make it so unfriendly)
<edit> Removed Inappropriate Word </edit>
Last edited by EduTech; 26th January 2010 at 04:00 PM.
changing the cert on exchange 2007 has always been a simple process for me, all you would have to do is add an ssl cert. into IIS7 and then change the website to use the new cert. If you have issues it would only be a two second job to change it back.
You also siad that you have errors regarding to unsecured transports and fqdn issues, these are seperate from you main point and shouldn't be effected by placing a cert. on OWA
Last edited by fawkers; 26th January 2010 at 05:21 PM.
There are currently 1 users browsing this thread. (0 members and 1 guests)