Windows Installer .msi http://www.vinsvision.com/Articles/tabid/66/BlogId/11/Default.aspx en-US vvanegmond@hotmail.com vvanegmond@hotmail.com Tue, 19 Aug 2008 23:18:00 GMT Tue, 19 Aug 2008 23:18:00 GMT http://backend.userland.com/rss Blog RSS Generator Version 3.2.0.29758 Installing legacy software with group policies in the Active Directory can cause some challenges. The first is machine assigned software. Machine assigned software can only be installed using a Windows Installer msi file. The second is allowing users to install software by publishing it to the user. Publishing software to the user can be done using .zap files, but the software will run in the user’s security context and this is a problem when local administrator permissions are required. Publishing the software using a Windows Installer msi file can remedy this problem because, by default, published msi software is installed with elevated privileges. With WIWW you can create msi files that will execute any command you specify and gives system administrators additional flexibility to remedy these challenges. http://www.vinsvision.com/Articles/tabid/66/EntryID/15/Default.aspx vvanegmond@hotmail.com http://www.vinsvision.com/Articles/tabid/66/EntryID/15/Default.aspx#Comments http://www.vinsvision.com/Default.aspx?tabid=66&EntryID=15 Fri, 06 Jul 2007 22:00:00 GMT 10 http://www.vinsvision.com/DesktopModules/Blog/Trackback.aspx?id=15 Since Windows XP SP2 was released, Microsoft introduced a major improvement in supporting and detecting Bluetooth devices. Now, a few years down the road, there are more and more problems in finding Bluetooth drivers that will work with Microsoft's native Bluetooth stack. This article explains a way around this issue and includes a Windows Installer msi file with 116 additional Bluetooth drivers. http://www.vinsvision.com/Articles/tabid/66/EntryID/13/Default.aspx vvanegmond@hotmail.com http://www.vinsvision.com/Articles/tabid/66/EntryID/13/Default.aspx#Comments http://www.vinsvision.com/Default.aspx?tabid=66&EntryID=13 Mon, 25 Jun 2007 22:00:00 GMT 67 http://www.vinsvision.com/DesktopModules/Blog/Trackback.aspx?id=13 If you want to install an ActiveX component to your users for install on-demand, you can publish the ActiveX component in the Active Directory. As an example we will publish the Terminal Services Client 6.0 ActiveX, but you can use the same method described here to publish other ActiveX components. An example Windows Installer msi file is included. http://www.vinsvision.com/Articles/tabid/66/EntryID/11/Default.aspx vvanegmond@hotmail.com http://www.vinsvision.com/Articles/tabid/66/EntryID/11/Default.aspx#Comments http://www.vinsvision.com/Default.aspx?tabid=66&EntryID=11 Sun, 17 Jun 2007 22:00:00 GMT 0 http://www.vinsvision.com/DesktopModules/Blog/Trackback.aspx?id=11