Re: OWA security question with Exchange 2007

It depends on lots of factors. I'm cheap so I'd exhaust all efforts to use
my own CA, but some things are simply too hard for organizations--especially
large ones--to manage.
--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"

"Sabo, Eric" <sabo_e@xxxxxxx> wrote in message
news:%23VYxu%23FpHHA.3264@xxxxxxxxxxxxxxxxxxxxxxx
Ed,

From what you are saying it is better to go with Verisign instead of
using our own certificates.



"Ed Crowley [MVP]" <curspice@xxxxxxxxxxxxxx> wrote in message
news:%23$LrmT$oHHA.4032@xxxxxxxxxxxxxxxxxxxxxxx
My understanding of the main reason to use a public certificate authority
is that you don't have to configure your remote clients to trust your own
certificate authority. This shouldn't be so troublesome with real PCs,
but I guess it can be a real pain with embedded devices, handheld
devices, smartphones, and the like.
--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"

"Sabo, Eric" <sabo_e@xxxxxxx> wrote in message
news:OGRMb%239oHHA.4544@xxxxxxxxxxxxxxxxxxxxxxx
We are currently in the planning stages of our Exchange 2007. What we
like to do is leverage our certificate server that we currently have to
secure OWA on exchange 2007. With Exchange 2003, we currently use
Verisign certificates, what are the pros and cons in using our own
certificates? We want to load balance our front end OWA Exchange
2007 server. Is there any documentation on this topic?

Any thoughts or suggestions would be appreciated?

Thanks,
Eric Sabo







.

Loading