Signing a macro for use within our domain

[Darren]

Hi All,

We have created a VBA Macro for use in word across all document in our
company. Because the Office XP macro security is set to high, we get
the warning message about our macro not being signed.

I've spent the better half of the day trying to find out how to sign
this thing for use within our domain. We have no intentions on using
it externally. I have read about the use of selfcert.exe and
unfortunately it will not suit our needs because of the numbers of
computers involved. We are wanting to avoid buying a certification
from external CA (like VeriSign) because of the costs involved.

Could anyone please point me in the right direction for instructions
on how we can use it to get around this problem using the features on
our server.

FYI We are running a windows 2000 domain.

TIA, Darren Stahlhut

 

[Jezebel]

Try using a Thawte freemail certificate -- they're free, and are, by some
accounts, sufficient for the purpose. Not tried it myself, but the method
was described to me by a 'usually reliable source'.

 

[Jean-Guy Marcil]

Darren was telling us:
Darren nous racontait que :

Hi All,

We have created a VBA Macro for use in word across all document in our
company. Because the Office XP macro security is set to high, we get
the warning message about our macro not being signed.

I've spent the better half of the day trying to find out how to sign
this thing for use within our domain. We have no intentions on using
it externally. I have read about the use of selfcert.exe and
unfortunately it will not suit our needs because of the numbers of
computers involved. We are wanting to avoid buying a certification
from external CA (like VeriSign) because of the costs involved.

Could anyone please point me in the right direction for instructions
on how we can use it to get around this problem using the features on
our server.

I may be writing something silly here, but I was under the impression that
if you put your macro in a global template (In Word's start up folder) and
that you set the security to high *and* on the trusted publishers tab of the
security dialog, check "trust installed add-ins" and "Trust VBA projects"
that even unsigned macros will be allowed to run. I am not on a domain, but
on my little home network, it does work like that.

--
Salut!
_______________________________________
Jean-Guy Marcil - Word MVP
(e-mail address removed)
Word MVP site: http://www.word.mvps.org

 

[Ikke123]

Hi there,

It should work in a domain also, so try the steps as described by Jean-Guy
Marcil Darren and let us know if it worked.

Good luck,

Emmy

 

[Darren]

Hello again,

I have managed to overcome the issue buy installing Certificate
Services on our Domain Controller. I then requested a "Code Signing
Certificate" through the IIS website "http://servername/certsrv/". I
then logged onto the server went to Administration Tools ->
Certificate Authority -> Pending Requests. Found the certificate I
requested and issued it. Then went back to the website and retreived
and installed the certificate.

Back in word I went into edit macro -> tools -> digital signatures and
installed the new signature on the macro. When someone opens the word
doc I don't that annoying security warning about unsigned macros.

Of course this is the massively trimmed version of the actual events
that lead to acheiving the goal, Microsoft products have a way turning
what seems a simple task into a 2 day event. Thanks for all your
ideas,

Regards,
Darren Stahlhut