Hi, This is my first post. I have been reading the forums for a couple of days and working on some AutoIT scripts. The app is really cool, but I think I may have run into a problem, not necessarily with AutoIT, but with the way I am deploying the end package.
Summary: Anyone know a way to install an app that doesn't have any kind of "silent switch" without spawning a real window?
Long version:
I am using a configuration management program that deploys software to systems w/o logging in (it works great in Linux environments). The program uses an agent running on the box, and uses a python process to call applications. The program (on the server) communicates with the agent (on the remote system) but never actually logs in. The preferred method for deploying MS applications through this program is with MSI's, so I have packaged the application (Sorenson 3), first using AutoIT to enter the serial key and make choices, and then using MakeMSI to get it into an MSI. This works great locally, and I have made it completely handsfree, and mostly silent other than the AutoIT portion.
When I deploy the MSI that uses AutoIT to install an application the deploy just hangs until it times out. I can only imagine that when the MSI calls sorensoninstall.exe (the exe i created with AutoIT) it attempts to open a window (duh), but where does this window go if there is no login (shell or otherwise)?
I know this post is pretty vague. I am still learning the deploy program at this time, but I am hoping someone finds this and has had a familiar experience. My final goal is to package as many MS applications that we use as possible into the deploy program. My short-term goal is to install 8 applications on 48 servers for video encoding. Some of these I can install silently, and use a combination of NSIS and MakeMSI to package. I know some can't be installed silently, mainly because of the way it was packaged, and this is where I am stuck.
Thanks in advance for any help!