Outlook 2003 addin deployment problem

[Roger Wang]

Hi,

I have encountered a problem with Outlook 2003 addin installation, on which
I have been stuck for days.

The problem is:
I have created a very simple addin for Outlook using VB6. The addin is as
simple as just showing a message box when outlook starts up. I register this
addin using regsvr32, or Visual Studio Installer, or Visual Studio .NET
Setup Project (have tried everything). The program runs fine on the same
account. But if I log off and log back on to the same machine using a
different account, say a normal user account (no admin rights), then the
addin just disappears. I cannot even find it in the COM Addin list within
Outlook, nor can I manually add it from within Outlook.

From what I've heard, this may be just to do with Outlook 2003? Or is the
solution moving from VB6 to .NET?

Thanks
Regards
Robert

 

[Michael Bauer]

Am Mon, 1 Aug 2005 11:55:59 +1200 schrieb Roger Wang:

Robert, obviously your Add-In is installed for the current user only.
Every user needs to install it himself. Please see also "Problem
deploying OL 2002 addin to non-Admin users" in this group.

 

[Helmut Obertanner]

Hello Roger,

you could patch the .msi file.
use the "orca" tool from Windows SDK and add the Property
"ALLUSERS=1" to the .msi file.
Then install your AddIn as Administrator.
(or deploy with SMS or AD)

Also use a policy to deploy the security settings and the registry key for
that.
(CheckAdminSettings)

I don't know if it helps for a VB created setup solution,
but for a .Net this does the trick.

Hope this helps,

regards
--
Helmut Obertanner
Technical Consultant
Softwaredevelopment
DATALOG Software AG | Zschokkestr. 36 | D-80687 Munich

.... and IT works!

 

[joel]

Would it be correct to say that you have to implement an Outlook Security
Settings public folder and install the Outlook Security template to use
CheckAdminSettings registry key?

 

[Helmut Obertanner]

Yes, exactly.

--
Helmut Obertanner
Technical Consultant
Softwaredevelopment
DATALOG Software AG | Zschokkestr. 36 | D-80687 Munich

.... and IT works!

 

[Roger Wang]

Halmut,
I am VERY foggy on what you have suggested. I have tried creating an MSI for
my program but within Orca, under properties I cannot find the ALLUSERS
field. Also, can you give me some links to articles that talk about how to
deploy the security settings and registry key for outlook?

Thanks in advance.
Roger

 

[Helmut Obertanner]

Hello Roger,

you must add this property by yourself.

Maybe this article give you a starting point for .adm files and AD
http://www.sparnaaij.net/howto/policies.htm


--
Helmut Obertanner
Technical Consultant
Softwaredevelopment
DATALOG Software AG | Zschokkestr. 36 | D-80687 Munich

.... and IT works!

 

[Roger Wang]

Helmut,
2 questions:
- does this security issue ONLY apply to Outlook 2003?
- is it possible to deploy an add-in to a computer (local or in a domain)
that is available to ALL users programatically? is manually configuring the
Outlook security template the only way??

Roger

 

[Helmut Obertanner]

Hello Rodger,

Security Issue:
If you programm an AddIN and want to use CDO or access some Properties like
Address or Body of Outlook Items and you are in an Exchange environment -
you have 3 options:

1. Use Security Settings Form (Wich is Recomended in an Exchange environment)
Add your .dll to trusted AddIns and allow CDO to access secured properties

2. Use the Redemtion library (or other libraries like ExMapi33).

3. Use Extended Mapi directly

Otherwise the Securitywarnings pops up.

2. Deploy Programmatically ? You can Create a msi and apply the ALLUSERS = 1
property. Thats all.

You can install it manually or e.g. create a Group Policy in your AD and
assign this software.

The .adm template is only to avoid this security popup.


--
Helmut Obertanner
Technical Consultant
Softwaredevelopment
DATALOG Software AG | Zschokkestr. 36 | D-80687 Munich

.... and IT works!

 

[Roger Wang]

Helmut,
I am doing:
-Use the Redemtion library
-Have Created a msi and apply the ALLUSERS = 1 property

But once the install is complete, I have to manually add the addin in
outllook by browsing to the DLL i have deployed. It doesn't load by itself.
Do you now why it behaves like that?

Btw, thanks for all the helpful responses.

Roger

 

[Helmut Obertanner]

Hello Roger,

this should work when you set the AddIN Registry Settings under HKLM not
under HKCU.
I do it the same way.

regards,

--
Helmut Obertanner
Technical Consultant
Softwaredevelopment
DATALOG Software AG | Zschokkestr. 36 | D-80687 Munich

.... and IT works!