Outlook Security Template

[Guest]

Since installing Service Pack 3 for Office, our users receive a message
reading "A program is trying to access e-mail addresses you have stored in
Outlook" every time they attempt to attach an iManage document. They are
finding the message annoying since some of them attach numerous documents
throughout the day.

I am trying to use the Outlook security features administrative package to
trust this application. Everything was running smoothly but now I've run
into a snag.
I downloaded and installed the admpack.exe on a Windows 2003 server and
copied the hashctl.dll and comdlg.32.ocx files to the system32 directory
(registered same). I also created a public folder in Exchange (version 2003)
entitled Outlook Security Settings (giving users read rights and admin
owner/full rights). I then went back to my 2003 server and opened
OutlookSecurity.oft and followed Microsoft documentation for modifying the
default security settings (published form successfully). However, when I try
to hit the Close button in this Compose mode, nothing happens (need to click
on the X). When I open the published form in Outlook and go to the Trusted
Code tab and click on Add to browse to the dll that is used to load the COM
add-in, nothing happens (although the Add button shows to be depressed.) What
step am I missing?

 

[Sue Mosher [MVP-Outlook]]

Maybe a dumb question, but are you actually running Outlook in your Win 2003 server? The hashctl.dll and comdlg32.ocx files need to be installed on the machine that you'll use to create and manage items in the Outlook Security Settings folder.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Guest]

Yes -- I'm running Outlook 2002 on this particular Win 2003 server (it is a
terminal server). I copied the dll and ocx files to this server's system32
directory and ran the regsvr32 from Start | Run for both. The terminal server
is also where I opened OutlookSecurity.oft, published the form and then
opened Outlook to open the form and try to set the trusted code. The only
thing I actually did on Exchange was create the public folder. Do I need to
add something within Exchange regarding permissions?

 

[Sue Mosher [MVP-Outlook]]

I'm a little confused. Are you running Outlook from the server's keyboard or as a TS client? If the latter, did you add the .dll needed to make custom forms function in TS -- see http://www.slipstick.com/config/terminalserver.htm#ol2002? Did you create the public folder and set permissions with Exchange System Manager or with Outlook?

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Guest]

That did the trick! Once I copied the Outlvbs.dll to the terminal server, I
was able to add the .dll I needed within the Trusted Code control of my form.
Thanks for your help!