I have had to package up a ActiveX control. I have successfully set up a per machine deployment, which we will roll out to our student labs

However I also need to create a per user deployment, for our staff. I have published the MSI through policy in the AD but it doesnt seem to recognise it is available when you go to the URL (you just get the box with the red cross and no message).

If I look in add new programs the control is listed and can be installed from there.

I have made sure that the include OLE information is checked in the policy and that the UseCoInstall HKLM registry value is present)

Could anyone provide me with some further info in order to troubleshoot?

Many thanks
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


It can occurr if there is no advertised icons to install it based on user profile. Are you sure this MSI package has advertised icons ? I`m not sure, but so far as I know installing MSI using AD for machine, you can install the package directly, however to install it based on user profile, the package it just advertised to the machine and installed after first user request. I`m not sure if I`m right because I never had worked before using AD without this scenario. I hope it can help you.

Answered 02/27/2007 by: bobcapilontra
Senior Yellow Belt

Please log in to comment
There's a couple of reasons that pop into my head here.

1) you don't have the UseCoInstall registry key on the local machines. There's a kb article that describes this key and it's location but basically, it's there to tell IE to look to AD for advertsed controls when an activex control is encountered.
2) The MSI pacakge doesn't have proper advertising in place for the matching CLSID. I originally started off building these using Visual Studio Installer but that became impossible when i went to VS2005 so I moved to Wise. The problem now is that I have to manually add the CLSID, the TypeLib and the Document Type for the ActiveX Control.

The GUID of the ActiveX control is also the CLSID of the registered file. By pulling from the CLSID section of hte registry for that control, you can then get the document type and hte typelib to verify that everything is setup within the MSI correctly.
Answered 02/28/2007 by: Chipster
Blue Belt

Please log in to comment
That's good trivia, Chipster. Didn't know about UseCoInstall - had to bruteforce installations wrong way...
Answered 02/28/2007 by: revizor
Third Degree Blue Belt

Please log in to comment
Publishing ActiveX controls is something I've not done before but would certainly come in handy! Could you recommend some good reading material?
Answered 04/10/2007 by: lamaslany
Yellow Belt

Please log in to comment