Solved

Unattended Install eHealth SystemEDGE client on servers

Posted on 2010-11-08
13
1,634 Views
Last Modified: 2012-05-10
I need to install CA eHealth SystemEDGE (CASysedge_4_3_SP4_win_x86.exe) on a few hundred servers.  I want to build something I can deploy via SCCM that will install and at least partially configure the servers.

I was able to extract the msi from the setup file, but I can not install it, as a message comes up saying:
"This installation can not be run by directly launching the MSI package; you must run setup.exe."

I've looked around online but can not seem to find a way to get around this.  Does anyone have an ideas on how to deploy this?
0
Comment
Question by:ednetman
  • 7
  • 4
  • 2
13 Comments
 
LVL 35

Expert Comment

by:Joseph Daly
ID: 34085578
Using SCCM you should be able to just use the exe file along with any command line options that are available for it. This will vary for every program so you should start by running a CASysedge_4_3_SP4_win_x86.exe /? from the command line. This will tell you what you have to work with.

This program migh also support an XML or other type of answer file. If that is the case you can simply use that proper command from within SCCM and it should work.
0
 
LVL 7

Author Comment

by:ednetman
ID: 34087334
Yeah, I tried to create an answer file and the installer just errors out.  I was really hoping to see if someone had already done this and could share their command lines and answer files (with the sensitive info made generic).
0
 
LVL 35

Expert Comment

by:Joseph Daly
ID: 34094009
Most answer files are pretty picky about their setup/formatting even a single error would cause it to fail out usually.

That product seems like a pretty obscure product that many people probably wont have available to them. If I had the install file im sure I could figure something out but without it is kinda difficult. This isnt like MS office where everyone and their mother has it you know.

Good luck.
0
 
LVL 10

Expert Comment

by:Kezzi
ID: 34094233
What error does the installer give you?  are you able to post the answer file?
0
 
LVL 7

Author Comment

by:ednetman
ID: 34128955
It never creates the answer file, the installer just runs for a few seconds then it goes away.  No on-screen info, etc.  I was really looking for someone who has been able to get this to work so I didn't have to start from scratch.  Maybe even someone who figured out how to make the MSI work without the setup file.  That way i could use a transforms file.
0
 
LVL 10

Expert Comment

by:Kezzi
ID: 34135581
Have you tried passing MSI command line properties with the Setup.exe?  some exe's that launch msi's allow you to use MSI command line properties.
0
Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

 
LVL 7

Author Comment

by:ednetman
ID: 34136893
I have been able to record the answer file, but the MAIN THING  needed to cpature wasn't recorded.  That's the change in installation directories.  I tried to add it on the fly, but I think the install DIR must be passed to the MSI from the Setup.exe.

My files are all in D:\temp and the command lines I have tried are:
CASysedge_4_3_SP4_win_x86.exe /s /f1"D:\Temp\Setup.iss" /v"/qn INSTALLDIR=D:\SysEdge"
CASysedge_4_3_SP4_win_x86.exe /s /f1"D:\Temp\Setup.iss" /v"/qn INSTALLDIR=\D:\SysEdge"
CASysedge_4_3_SP4_win_x86.exe /s /v"/qn INSTALLDIR=D:\SysEdge" /f1"D:\Temp\Setup.iss"
CASysedge_4_3_SP4_win_x86.exe /s /v"/qn INSTALLDIR=\D:\SysEdge" /f1"D:\Temp\Setup.iss"

Also tried to add the entries to the answer file:

[InstallShield Silent]
Version=v5.00.000
File=Response File
Name=SystemEDGE
Version=4.3.4
Company=CA
[SdAskDestPath-0]
szINSTALLDIR=D:\
Result=1

No luck, any ideas?

0
 
LVL 10

Expert Comment

by:Kezzi
ID: 34137192
/v"/qn INSTALLDIR=D:\SysEdge"

doesnt look right to me.  Not sure if its just a typo from you adding it site, but change it to look like this instead.

/v /qn INSTALLDIR="D:\SysEdge"

also not sure about szINSTALLDIR=D:\
0
 
LVL 7

Author Comment

by:ednetman
ID: 34137600
/v"  -  Is the command to pass commands to the MSI

Everything being passed to the MSI has to be in the quotes: /v"qn INSTALLDIR=D:\SysEdge"

grrrrrr, this is driving me nuts!
0
 
LVL 10

Expert Comment

by:Kezzi
ID: 34137953
OK try this, use the MSI just how you want to, but add ISSETUPDRIVEN=1 to the command line.  This will trick the MSI into thinking it was launched by setup.exe

0
 
LVL 7

Author Comment

by:ednetman
ID: 34138517
I tried that before, but it doesn't work because the MSI is looking for a lot of things that the setup file is passing as variables, as well as a lot of dll files that the setup registers during setup.  Even if I register all the dll files from the command line first, it still ends up crashing the installer with an error: Type Mismatch and then a long string of numbers.
0
 
LVL 7

Accepted Solution

by:
ednetman earned 0 total points
ID: 34291773
Looks like the only option was to repackage.  However, that's what I was trying to avoid as the only thing I have the ability to do is a snapshot / compare type of install.  This won't cover the multiple OS types and hardware configs.  Once working I was going to adjust the answer file so that different hard drives could be used as some servers have D: as the DVD-ROM and would need to be installed to E: or F:.

We ended up having an "Install Party" where several of us stayed late one night, split up the list, ordered a pizza, and installed the software by hand.
0
 
LVL 7

Author Closing Comment

by:ednetman
ID: 34328484
Experts ran out of solutions, none actually worked.  :-(  Fixed myself.
0

Featured Post

Zoho SalesIQ

Hassle-free live chat software re-imagined for business growth. 2 users, always free.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

As a long-time IT Professional, the most important skill I have developed and consider to be my most valuable tool is Effective Troubleshooting. Step through my problem-solving procedure in this 10-step guide adapted from The Universal Troubleshooti…
When we talk about DevOps toolchains, I sometimes wonder how many people really get what we’re talking about. I don’t know if it’s just semantics or tone or something else, but sometimes I think it just sounds like buzzword sausage. So it’s always …
Here's a very brief overview of the methods PRTG Network Monitor (https://www.paessler.com/prtg) offers for monitoring bandwidth, to help you decide which methods you´d like to investigate in more detail.  The methods are covered in more detail in o…
This video gives you a great overview about bandwidth monitoring with SNMP and WMI with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're looking for how to monitor bandwidth using netflow or packet s…

914 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

19 Experts available now in Live!

Get 1:1 Help Now