/build/static/layout/Breadcrumb_cap_w.png

Publishing ActiveX control

I am trying to setup activex controls to auto-install on the users pc. Systems are managed and users do not have permissions to install activex controls. I built an msi package, and created a gpo with the published app setup. I can manually install the published app from add / remove program, but when going to the site that requires the control it does not add. I have added the HKLM\Software\Microsoft\Windows\CurrentVersion\Internet Settings\UseCoInstall Key and Dword not totally clear on it. And I used orca to check the clsid, and type library. What other settings are queried to associate the msi package as a fit for the activex control?

0 Comments   [ + ] Show comments

Answers (7)

Posted by: razor0690 13 years ago
Senior Yellow Belt
1
Thanks I will take a look at it. I am trying to build a package for Sql 2005 Reporting Services Print Client. It is a single cab file with the following files included.

gdiplus.dll
RSClientPrint.dll
RSClientPrint.inf
RSClientPrint_1028.rll
RSClientPrint_1031.rll
RSClientPrint_1033.rll
RSClientPrint_1036.rll
RSClientPrint_1040.rll
RSClientPrint_1041.rll
RSClientPrint_1042.rll
RSClientPrint_1043.rll
RSClientPrint_1046.rll
RSClientPrint_1053.rll
RSClientPrint_2052.rll
RSClientPrint_3082.rll
Posted by: Chipster 13 years ago
Blue Belt
0
KB Article Q241163 describes the usage of te UseCoInstall key. The value should be set to 1.

The only other thing that you might need would be the doc type but that's optional. I generally set the CLSID, TypeLib and the doctype in order to get a full successful activation. Also, i haven't used Orca to do that since it doesn't do a terrific job of checking for errors. I use Wise for my other installations so it's just natural to go in there to do it. Originally, i was using Visual Studio Installer but it started becomign a PITA as packages got larger with more files etc.
Posted by: razor0690 13 years ago
Senior Yellow Belt
0
I have read the document Q241163 they state the following:

The following value must be added to the registry on computers that are permitted to download the control:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Internet Settings\UseCoInstall
Note that this can be any type of value and can contain any or no data.

It is a little unclear does I am using this in the registery does it compare to the value you are using?

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\UseCoInstall]
"UseCoInstall"=dword:00000001

Also I am unfamiliar with the document type what is a sample value that this would contain or where can I research the required value? I don't see it in the Clsid data.
Posted by: Chipster 13 years ago
Blue Belt
0
good point. i must have set it to that for my own sanity. :)

If you were to use visual studio installer, here's the article that exlains how to do it.
http://support.microsoft.com/kb/248023

I started off using this and then i figured out how to manually add the advertisements within Wise. I opened up one of my original simple packages (single ocx) in Wise and used the same formatting for what was associated to create a new one and it's worked fine ever since.
Posted by: vvanegmond 13 years ago
Yellow Belt
0
You could take a look at http://www.vinsvision.com

There's an administrative template for UseCoInstall available for download as well as a mini-guide/walkthrough to help you implement it.

Vin
Posted by: razor0690 13 years ago
Senior Yellow Belt
0
I actually figured it out and it works great. I took a look at your site and I really like it. Thanks
Posted by: mrcheeks 12 years ago
Senior Yellow Belt
0
Hey all i'm facing the same dilema explained in this thread. I need to push out the RSClientPrint Active X controller to a selected number of machines.

My problem is i'm not exactly sure how to wrap the cab file? without doing a snapshot, since this is very messy is there a simple way someone can explain how to make this into an msi?
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ