macro protection problem

[Guest]

What is the preferred method to deal with macro protection? I have just
updated all the machines to office2k3 and now a critical worksheet that
uses benign macros doesn't run because of the protection. Bringing security
to "low" allows it to run but each user has to set that themselves.
I have heard about creating a local CA for trusting the macro and I am
interested in that but isn't there an easier way?

 

[Jezebel]

Setting security to low is very unwise. Stupid even, in a company.

All methods involve making changes on each machine unless you have Group
Policies set up (which presumably you don't or you wouldn't be asking). If
you create a certificate, each machine has to add the certifier to the list
of trusted publishers.

Better than setting each machine to low security is 'Trust access to VBA
Project' (assuming you trust your employees not to write malicious code), or
put the code in an add-in or template and trust that.

 

[Alan]

Setting Macro Security to 'Medium' will give the user the option to Enable
or Disable macros on opening, 'High' will prevent macros from running at
all. Setting to 'Medium' will need to be done on all of the machines
individually, but thankfully only once. Setting security to low is not
advisable, dangerous even as malicious code can easily be written in to XL
files and on that setting they will just open and run,
Regards,
Alan.

 

[Guest]

I agree with you both that security shouldn't be set to low. But it was a
critical file and that is all that would allow it to run. At least that was
all I could sucessfully communicate to them.
How can the macro in question be trusted for everyone? if I set the "VBA
projects" setting to be trusted, isn't that as dangerous?

 

[Alan]

It must run on the Medium setting that gives the user a warning. A file from
an unknown source can then be opened or not at the users discretion,
Regards,
Alan.

 

[Jezebel]

Certify it.

I agree with you both that security shouldn't be set to low. But it was a
critical file and that is all that would allow it to run. At least that was
all I could sucessfully communicate to them.
How can the macro in question be trusted for everyone? if I set the "VBA
projects" setting to be trusted, isn't that as dangerous?