Re: Ditching inhouse CA for 3rd party cert
- From: "Herb Martin" <news@xxxxxxxxxxxxxx>
- Date: Tue, 6 Feb 2007 18:41:52 -0600
"Don Murphy" <DonMurphy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:11F6507F-008F-4DF3-9DC2-061800D0B1EC@xxxxxxxxxxxxxxxx
Is there any issue ditching a selfsigned CA for a third party cert?
You mean you won't run your own CA?
Then you have to deal with cost and cert distribution differently.
If you mean you will have the public CA sign your CA to allow the
certs to be trusted by the outside world then that is a GOOD thing.
I am hoping I can simply do this:
http://support.microsoft.com/kb/295281
The certificate is used to support OWA. I also hope to use Instantssl
Email certs can be automatically issues and renewed using Win2003.
If you have lots of users this could become obnoxious to manage with
externally ISSUED certs.
I have a 3 server environment supporting about 100 workstations.
servers are all 2003 SP1 (2 dc's one member server)
workstations all xp SP2
--
Herb Martin, MCSE, MVP
http://www.LearnQuick.Com
(phone on web site)
.
- Follow-Ups:
- Re: Ditching inhouse CA for 3rd party cert
- From: Don Murphy
- Re: Ditching inhouse CA for 3rd party cert
- Prev by Date: Re: reporting permissions on folders
- Next by Date: Re: Setting up roaming profiles
- Previous by thread: reporting permissions on folders
- Next by thread: Re: Ditching inhouse CA for 3rd party cert
- Index(es):
Relevant Pages
|