<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Activex-Installer-Service on Anything About IT</title><link>https://www.verboon.info/tags/activex-installer-service/</link><description>Recent content in Activex-Installer-Service on Anything About IT</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 04 Apr 2010 21:55:01 +0000</lastBuildDate><atom:link href="https://www.verboon.info/tags/activex-installer-service/index.xml" rel="self" type="application/rss+xml"/><item><title>Windows ActiveX Installer Service</title><link>https://www.verboon.info/2010/04/windows-activex-installer-service/</link><pubDate>Sun, 04 Apr 2010 21:55:01 +0000</pubDate><guid>https://www.verboon.info/2010/04/windows-activex-installer-service/</guid><description>&lt;p&gt;Managing ActiveX Components within an enterprise sometimes can be a pain. Users with standard user privileges by default can’t install ActiveX components, hence whenever a larger group of users require an ActiveX component you usually end up creating a software package and distribute it via Software Distribution or you provide them with temporary Administrative rights. But if the clients are running Windows Vista or Windows 7 there is another solution available I noticed many people aren’t aware of, hence that’s why I am writing this article.&lt;/p&gt;</description></item></channel></rss>