You can specify in the whitelist that anything that comes from here has been given authority to run.įor the installation of the OCX files, there is a seperate workaround that I was able to do. It doesn't match w/ the real world expectations since MOST enterprises do NOT allow user's admin rights to their machines.Įssentially, the white list will work perfect if you have add-ins for IE that are being hosted on a domain/webserver.
This is the SINGLEMOST PAINFUL aspects of using ActiveX components in IE. If anyone has any different experience, please let us know.
Webrec control software install#
(The Active Directory push and SMS solutions don't get around this, they just require an Admin to push the install to the user's machine before the component is required.) That means you MUST have admin rights to install an ActiveX. (the script ActiveXObject() only takes a classid.) I've tried it myself using the documentation from the walk through, and using the User Specific Redirection overrides putting ProgId info in the Current User hive, and I can't get it to work.įrom what I've seen, I believe you MUST register the ActiveX in HKLM before IE can see the classid. ActiveX components are instantiated by ClassID not ProgId. I've scowered for information about this and none is forthcoming. I've never seen any documentation from MS that Reg-Free COM works with IE. The other problem is an arbitrary application may not be designed to recognize isolated components, as it probably doesn't have a way to reference your component through a manifest." Such components typically require some kind of registration scheme defined by the hosting environment that is beyond the scope of the manifest itself. The component is intended for use as an add-in or a snap-in, such as an Office add-in or a control in a Web browser.
0 kommentar(er)
