Deploy a SelfCert certificate

Hi there,

is it possible to deploy a certificate created with SelfCert through a
NT-Domain (W2k3 and XP) using policies or whatever?
By now, every user must install and trust the certificate on each first
usage. To trust the certificate manually is ok (otherwise, of what use
would certificates be?), but the installation of the certificate is
something I'd like to automate.

I know SelfCert certificates are not intended to be used in productive
environments, but in my scenario the costs for a trusted certificate
would exceed the benefits.

Thanks for your help,

Tobi

Art
Wed Feb 07 17:03:06 CST 2007

On Feb 6, 8:57 am, Tobias Schr=F6er <tobias-schroeerNOS...@gmx.de>
wrote:
> Hi there,
>
> is it possible to deploy a certificate created with SelfCert through a
> NT-Domain (W2k3 and XP) using policies or whatever?
> By now, every user must install and trust the certificate on each first
> usage. To trust the certificate manually is ok (otherwise, of what use
> would certificates be?), but the installation of the certificate is
> something I'd like to automate.
>
> I know SelfCert certificates are not intended to be used in productive
> environments, but in my scenario the costs for a trusted certificate
> would exceed the benefits.
>
> Thanks for your help,
>
> Tobi

I don't have an answer to your question, but you should know that the
SelfCert feature has been reduced in Word 2003. The user see's the
SelfCert _each_ time he/she uses the template. In Word 2003, which I
now have, help says something about SelfCert intended only for self
use. So, long term, depending if you do migrate to a new version, you
might have to reconsider the use of a trusted certificate.

tobias-schroeerNOSPAM
Thu Feb 08 02:13:58 CST 2007

Art H schrieb:
> On Feb 6, 8:57 am, Tobias Schröer <tobias-schroeerNOS...@gmx.de>
> wrote:
>
>>Hi there,
>>
>>is it possible to deploy a certificate created with SelfCert through a
>>NT-Domain (W2k3 and XP) using policies or whatever?
>>By now, every user must install and trust the certificate on each first
>>usage. To trust the certificate manually is ok (otherwise, of what use
>>would certificates be?), but the installation of the certificate is
>>something I'd like to automate.
>>
>>I know SelfCert certificates are not intended to be used in productive
>>environments, but in my scenario the costs for a trusted certificate
>>would exceed the benefits.
>>
>>Thanks for your help,
>>
>>Tobi
>
>
> I don't have an answer to your question, but you should know that the
> SelfCert feature has been reduced in Word 2003. The user see's the
> SelfCert _each_ time he/she uses the template. In Word 2003, which I
> now have, help says something about SelfCert intended only for self
> use. So, long term, depending if you do migrate to a new version, you
> might have to reconsider the use of a trusted certificate.
>
Hm, I use the certificate for Word and Outlook 2003 macros and after
installing and trusting the certificate at first run, Word or Outlokk
don't bother me again (on that machine). Only if I log on to another
machine I have to reinstall the certificate and trust it again.

Tobi