I'm looking for a way to deploy ActiveX controls to a terminal server farm. I know I can repackage the controls, or copy and register the files one by one, but I think there must be a better way.
All ActiveX packages contain an INF file the IE component download uses to see what should be done to install the control. Is there any way to trigger this, without having to go to the download site? I've been experimenting with the following syntax:
%SYSTEMROOT%\system32\rundll32.exe advpack.dll,LaunchINFSectionEx Crviewer.INF,,activexviewer.cab,4

which does not do the job. Tried specifiying that the Add.Code section of the .INF should be run, still no luck.

Does anybody have the killer tip for doing this?

0 Comments   [ - ] Hide Comments


Please log in to comment

There are no answers at this time
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