Hi all!
I'm creating a package that adds 4 Excel add-ins.
It's done by a vbs script, and works ok.
The only issue I've found is that needs user intervention to allow one Add-in to be registered. this message appears :
"This application is about to initialize Activex controls that might be unsafe. If you trust the source of this file, select OK and the controls will be initialized using your current workspace settings"
So the user must click OK, twice.

Does anybody knows how to avoid this message to appear?

Using this msi with active setup fails due the lack of interaction...

Help Please!!

0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


I take it that this vbscript for registering these add-ins is a per-user function?
Wouldn't the user be present to respond to these prompts?

Anyway, since you're already using a vbscript to install these add-ins, you could probably add some logic to bring the dialogs to into focus and poke some keystrokes (SendKeys) to dismiss them. Not perfect, but it does the job.

Another (less likely) option would be to find a way to trust the ActiveX control ahead of time so that the prompt doesn't appear in the first place.

A third option would be to lower the security level of Excel, but I wouldn't recommend this.

Answered 02/18/2007 by: mazessj
Blue Belt

Please log in to comment
Hi Josh,
Yes, it must be a per-user function, Excel Add-ins register per-user, and is that user presence what I must avoid.
At first I tried to change the security settings, it didn't work.
Then I tried to sendkeys, it didn't work
Finally a mate found a key to allow ActiveX for these issues, and it worked!

This is the key :

Thanks anyway, maybe it helps someone else :)

Answered 02/19/2007 by: KrisBcn
Purple Belt

Please log in to comment