running macro as trusted across many desktops

Per "http://msdn.microsoft.com/en-us/library/aa155754(v=office.10).aspx" I can get the macro trusted by: "The easiest way to prevent the macros security warning from appearing is to change the Outlook macro security setting to Low."  I have quite a few PC's that I would have to go around to do that to individually. Is there a way I can script this so I don't have to do it on each desktop individually/manually. The systems are mostly XP workstations logging into a domain. I don't really want to use certificates if I don't have to.
lineonecorpAsked:
Who is Participating?
 
scifo_dkCommented:
Sorry, misread a bit. Try having a look at the Outlook security administrative tools, I think thats what you need:
http://office.microsoft.com/en-us/office-xp-resource-kit/customizing-the-outlook-security-features-administrative-package-HA001136447.aspx
0
 
scifo_dkCommented:
You can use a bat-file to create a trusted location on the users pc, heres a link for the reg-key:
http://accessjunkie.com/faq_33.aspx
0
 
lineonecorpAuthor Commented:
This is for an Outlook macro not Access.  It's not about a trusted location but about trusting a macro added to Outlook.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
lineonecorpAuthor Commented:
Thanks for the link. I am not sure as to the relationship between com objects and VBA code - that is what we have created the Outlook macro with.  Can I turn the Outlook macro into a com object?  

As well, how does this 'trusting'  compare with a self-signed certificate or a certificate purchased from an outfit like Verisign?
0
 
scifo_dkCommented:
What I wanted you to know by reading from the link, is how you can deploy a trusted location og security settings to more clients from a server.
There is'nt much difference between a certified document, and a document placed in a trusted location. Both things auto-anable macros.
The big difference is, that some people need to verify that a specific document comes from a specific source. So if I were to deliver some specific document to you, I could use my certificate to assure you that I was the creator of this document. If anyone tryed to change my document, or create a fake one, the certificate will be removed.

I don't know anything about the difference between self-signed and purchased certificates though, sorry.
0
 
lineonecorpAuthor Commented:
Thanks for the clarifications.  What about the issue of " Can I turn the Outlook macro into a com object?  "
0
 
scifo_dkCommented:
To be honest... I don't know that much about com objects, so I can't give you a fair answer to that one :(
0
 
lineonecorpAuthor Commented:
Only some of the questions answered.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.