certificate authority

Archived from groups: microsoft.public.win2000.security (More info?)

You need Verisign if you want your servers to be externally trusted on a
broad basis. If you are using internal only, you can configure the internal
trust yourself.

Best Practices for implementing Windows Server 2003 PKI:
http://www.microsoft.com/technet/prodtechnol/windowsser...


--
David B. Cross [MS]
--
This posting is provided "AS IS" with no warranties, and confers no rights.


Top Whitepapers:

Auto-enrollment whitepaper:
http://www.microsoft.com/technet/prodtechnol/windowsser...

Best Practices for implementing Windows Server 2003 PKI:
http://www.microsoft.com/technet/prodtechnol/windowsser...

Troubleshooting Certificate Status and Revocation whitepaper:
http://www.microsoft.com/technet/security/topics/crypto...

Windows Server 2003 web enrollment and troubleshooting guide:
http://www.microsoft.com/technet/prodtechnol/windowsser...
"rodchar" <rodchar@discussions.microsoft.com> wrote in message
news:96B466BF-AF6A-4C54-A759-018C29ED4A1C@microsoft.com...
> hey all,
>
> i was wondering what the difference was between getting Verisign as an ssl
> provider and setting up certificate services on a win 2000 server within
> an
> enterprise?
>
> thanks,
> rodchar

Archived from groups: microsoft.public.win2000.security (More info?)

thank you.

"David Cross [MS]" wrote:

> You need Verisign if you want your servers to be externally trusted on a
> broad basis. If you are using internal only, you can configure the internal
> trust yourself.
>
> Best Practices for implementing Windows Server 2003 PKI:
> http://www.microsoft.com/technet/prodtechnol/windowsser...
>
>
> --
> David B. Cross [MS]
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
> Top Whitepapers:
>
> Auto-enrollment whitepaper:
> http://www.microsoft.com/technet/prodtechnol/windowsser...
>
> Best Practices for implementing Windows Server 2003 PKI:
> http://www.microsoft.com/technet/prodtechnol/windowsser...
>
> Troubleshooting Certificate Status and Revocation whitepaper:
> http://www.microsoft.com/technet/security/topics/crypto...
>
> Windows Server 2003 web enrollment and troubleshooting guide:
> http://www.microsoft.com/technet/prodtechnol/windowsser...
> "rodchar" <rodchar@discussions.microsoft.com> wrote in message
> news:96B466BF-AF6A-4C54-A759-018C29ED4A1C@microsoft.com...
> > hey all,
> >
> > i was wondering what the difference was between getting Verisign as an ssl
> > provider and setting up certificate services on a win 2000 server within
> > an
> > enterprise?
> >
> > thanks,
> > rodchar
>
>
>

Archived from groups: microsoft.public.win2000.security (More info?)

So basically VeriSign sets up there servers the way we would setup our own
CA? Is that correct?

"David Cross [MS]" wrote:

> You need Verisign if you want your servers to be externally trusted on a
> broad basis. If you are using internal only, you can configure the internal
> trust yourself.
>
> Best Practices for implementing Windows Server 2003 PKI:
> http://www.microsoft.com/technet/prodtechnol/windowsser...
>
>
> --
> David B. Cross [MS]
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
> Top Whitepapers:
>
> Auto-enrollment whitepaper:
> http://www.microsoft.com/technet/prodtechnol/windowsser...
>
> Best Practices for implementing Windows Server 2003 PKI:
> http://www.microsoft.com/technet/prodtechnol/windowsser...
>
> Troubleshooting Certificate Status and Revocation whitepaper:
> http://www.microsoft.com/technet/security/topics/crypto...
>
> Windows Server 2003 web enrollment and troubleshooting guide:
> http://www.microsoft.com/technet/prodtechnol/windowsser...
> "rodchar" <rodchar@discussions.microsoft.com> wrote in message
> news:96B466BF-AF6A-4C54-A759-018C29ED4A1C@microsoft.com...
> > hey all,
> >
> > i was wondering what the difference was between getting Verisign as an ssl
> > provider and setting up certificate services on a win 2000 server within
> > an
> > enterprise?
> >
> > thanks,
> > rodchar
>
>
>