Guest StMiller Posted May 27, 2005 Share Posted May 27, 2005 I have a task of creating MSI packages of third party installers so that the software can be deploy via group policy. I have one installer program that cannot be repackaged because MSI repacking does not support driver installations. So I had hoped I could create an MSI that started an autoit that would drive the responses to the vendors installation windows. Problem is that I want to do a machine install which means that autoit would be running under a service using the "local system" credential during the reboot process prior to any logons. I suspect that this is not possible. However, I am aware that multiple desktops are possible and perhaps Autoit can do some magic to get around this like defining a window interactive desktop invoking the setup code and working with windows in that desktop. It certainly would be cool if this were possible and it would allow MSI wrappers to third party setups and thereby extend the power of group policy machine installs. Can Autoit manage this? Thanks for any replies in advance. Link to comment Share on other sites More sharing options...
jftuga Posted May 27, 2005 Share Posted May 27, 2005 Instead of creating an MSI, create an AutoIt .exe executable that starts by running the Installer and will then go through all of the Installer's options for you. You can compile a AutoIt .au3 script to a .exe. The .exe files are usually less than 200k. -John Admin_Popup, show computer info or launch shellRemote Manager, facilitates connecting to RDP / VNCProc_Watch, reprioritize cpu intensive processesUDF: _ini_to_dict, transforms ini file entries into variablesUDF: monitor_resolutions, returns resolutions of multiple monitorsReport Computer Problem, for your IT help deskProfile Fixer, fixes a 'missing' AD user profile Link to comment Share on other sites More sharing options...
DaveF Posted May 28, 2005 Share Posted May 28, 2005 Have a look at Appdeploy. Nearly any EXE-based setup can be silenced with command line options so that a user can't disrupt the install. You can then call the setup from an MSI created with the Windows Installer Wrapper Wizard for your distribution.A caveat, MSIs created with WIWW have a bad entry in the properties table for language, I don't remember the actual property name, but it has a comma or semicolon that shouldn't be there... Yes yes yes, there it was. Youth must go, ah yes. But youth is only being in a way like it might be an animal. No, it is not just being an animal so much as being like one of these malenky toys you viddy being sold in the streets, like little chellovecks made out of tin and with a spring inside and then a winding handle on the outside and you wind it up grrr grrr grrr and off it itties, like walking, O my brothers. But it itties in a straight line and bangs straight into things bang bang and it cannot help what it is doing. Being young is like being like one of these malenky machines. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now