Wouldn't another option be using a purchased one for the Exchange CA
(instead of one each for the clients)? I know the one that would handle
other functions, such as OWA and RWW, runs about $20 or so.
"Steve Foster" <steve.foster@newsgroup> wrote in message
> Those would be perfectly applicable. However, you should realise that this
> really only works for internal mail. If you set up your own CA, no-one
> outside your organisation will recognise it, and therefore they get lots
> of dire security warnings about your secure messages.
> If you want to do secure email with third-parties, the large organisation
> solution is corporate PKI, but this is quite expensive to set up, and is
> generally beyond the scope of an SBS-sized organisation.
> In SBS environments, my general advice is therefore to simply buy
> individual certificates for email from the likes of Verisign and others.
> And for personal use, there are several free certificate suppliers (I'm
> using Comodo, having previously been a Thawte notary for their
> [now-defunct] free community certificate offering).
> Steve Foster
> Please reply only to the newsgroups.
> For SSL Certificates, Domains, etc, visit.:
>Thanks, that helps a lot.
>Wouldn't another option be using a purchased one for the Exchange CA
>(instead of one each for the clients)? I know the one that would handle
>other functions, such as OWA and RWW, runs about $20 or so.
That's the enterprise PKI I was referring to. It's *expensive*, and cannot
use the cheapie "validate the server identity" certificates used for
securing HTTPS traffic.
Windows Vista Forums is an independent web site and has not been authorized,
sponsored, or otherwise approved by Microsoft Corporation.
"Windows 10" and related materials are trademarks of Microsoft Corp.