I have an application that is going to be very difficult to deploy.

It uses MSDE, and according to the publisher, it cannot be put into a Ghost image, since MSDE looks at the computer name during the installation process. The same reason prevents me from using the Ghost AutoInstall program to create a snapshot.

The program uses InstallShield. I tried using the record (/r), and then the silent install option (/s), but it didn't work. I kept getting an error code of -3. I call the application publisher, and they said that they were going to add the feature to a future update, but it isn't ready yet.

They told me that there was no way to deploy the application, and that I would need to do it manually on each workstation (at least 200).

My question: Does anyone know of another program that I could use the record the installer options? Each machine will have the exact same options installed. I just don't want to have to click through the installer 200 times, I want it done automatically. Thanks for your replies.

-Chris
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
What application?
Answered 05/20/2005 by: Bladerun
Green Belt

Please log in to comment
0
It's a program called ProsystemFX ENGAGEMENT, version 3.7, by a company named CCH. It's a workpaper management-type software, used by accountants.
Answered 05/20/2005 by: ckloote
Yellow Belt

Please log in to comment
0
If it isn't already in MSI format, you could repackage it.

Whatever the existing installation routine does with the computer name may be feasible using your own package - it may simply write it to the registry or an "ini" file somewhere.

The first step is to create a snapshot, then look for hard-coded, machine-specific (or user-specific) data such as the computer name. If you find hard-coded entries, you can replace them with properties populated using the appsearch action.

If you can't find anything hard-coded, try your package on another PC. If it doesn't work you can troubleshoot it, if it does work you don't have an issue.

As a last resort, you could use vbscript and the sendkeys method (but that's nasty).
Answered 05/21/2005 by: WiseUser
Fourth Degree Brown Belt

Please log in to comment
0
We've been repackaging Pro Systems FX and it's various versions since 2002 without a problem. I don't see anything that points to ComputerName in our snapshot of this, and last I checked we had it on 50+ PCs. The vendor's an idiot from what I remember, and I had an argument about how I had to unlock HKCU (I kept telling him we didn't lock it down, and he kept saying if I didn't give all users write access, it would fail, and eventually I asked him if he'd ever known of anyone who did lock it down and he shut up).
Answered 05/23/2005 by: Ipstenu
Senior Yellow Belt

Please log in to comment
0
Ipstenu, which version of Engagement are you using? Version 3.0 and about use MSDE, but version 2 and below did not. I was able to install it fine in a Ghost image with version 2.

I've been using Google to search around the internet, and for other software that uses MSDE, it has the same problem. If you change the computer name, you need to reinstall MSDE.

I did some more searching on this message board, and I found a program named AutoIt. (http://www.autoitscript.com/autoit3/index.php) It's a scripting program that lets you send keystrokes to any window, among other things. I've been testing it for most of the morning, and it's not too hard to use. I almost have the entire installation running automatically, without user intervention.

I'm probably going to suggest this program to their technical support. I think it's a joke that they told me to install it manually on each machine. If it was up to me, I wouldn't use the program.
Answered 05/23/2005 by: ckloote
Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity