Trusting the Adobe Acrobat 6 add-in

[tdog]

Hello,
We have some Office 2002 SP3 users who get the "A program is attempting to
access your address book" message when composing/replying/forwarding messages
if they have Acrobat 6 loaded. I saw the Slipstick article about having to
trust add-ins like SpamNet via the Outlook Security Template. We have set up
a template to trust PDFMOutlook.dll but it doesn't seem to resolve the issue
unless you go the the Programmatic Settings tab on the template and set the
"When accessing address information via Outlook object model" radio button
to "Automatically approve."

However, this setting makes it unnecessary to trust specific add-ins; if we
then go back and remove PDFMOutlook.dll from the Trusted Code tab, the users
still do not get the pop-up.
In these cases, what is the point of trying to trust specific add-ins? Or is
there something of which I am not aware regarding the security template?

Thanks for your help!

 

[Sue Mosher [MVP-Outlook]]

It sounds like that particular add-in is not constructed properly in such a
way that it can be trusted. There are very specific guidelines for this,
published on Microsoft's web site and elsewhere ever since trusted COM
add-ins became available in the Outlook 2002 timeframe.

 

[tdog]

Sue,
Thanks. We can live with setting the "When accessing address information via
Outlook object model" radio button to "Automatically approve."

However, most of our users are Power Users and do not have rights to write
to HKEY_CURRENT_USER\Software\Policies\Microsoft\Security, which is where the
CheckAdminSettings value needs to go so Outlook knows to check for the
Security Template updates we are making. Is there a way to elevate privileges
so we can drop that Registry value in for them without producing an error?

Thanks!

 

[Sue Mosher [MVP-Outlook]]

The best way to roll out the registry change with a group policy object.

Keep in mind that using the Outlook Security Settings folder to manage the
"object model guard" prompts leaves you environment open to malicious
programs that want to silently harvest addresses. I'd recommend instead that
you remove the Outlook PDFMaker add-in as described
http://www.slipstick.com/outlook/ol2002sp3.htm#problems. It will still work
fine in Word.

 

[tdog]

Sue,

Thanks. We have looked at the GPO rollout but there does not appear to be a
Registry item under User Configuration-Windows Settings-Security Settings, so
we cannot add the value we need to and have it populate for current user. Any
ideas on this? Thanks.

 

[Sue Mosher [MVP-Outlook]]

That's not the right place to look. Did you add the .adm administrative
template for your version of Outlook? It sounds like maybe you haven't.

--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[tdog]

Sue,
I'll have to check - I'm coordinating with the guy who does all our GP
elements as I do not have the requisite privileges. My apologies for my
ignorance, but that would be added via AD to provide the necessary options,
correct? If we indeed have that .adm loaded, do you know which setting would
be appropriate for this sort of a modification?

Thanks so much for all your time and assistance.

 

[tdog]

Ah, never mind - this article explains it:
http://www.mcpmag.com/columns/article.asp?EditorialsID=793

Looks like we're now on the right track - thanks for all your help!