/bundles/itninjaweb/img/Breadcrumb_cap_w.png
I have done a search to see if this issue has come up before, but I have found nothing.... so I apologize if this has already been answered.

I am pushing out Microstation V8. I have made an ISS file, put it in the same folder as the setup.exe file.

When I run this locally from a command line, it runs successfully and Microstation V8 is installed perfectly. However, as part of the package, when I push it out... the program starts, then a mere few seconds later it says it ran successfully. When I go look at the computer though, it isn't anywhere to be found and hasn't installed at all. I am a bit perplexed as to why it runs fine locally but not with the package since I am using the same command line.

I also tried running a simple little cmd file to run the setup.exe file with the iss after reading some on the issues SCCM can have. The script basically said:

@echo off
:: Installs required software
"%~dp0Setup.exe" /s /f1"%~dp0setup.iss"
REM Return exit code to SCCM
exit /B %EXIT_CODE%

Neither worked.

Any ideas?
0 Comments   [ - ] Hide 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.
Answer this question or Comment on this question for clarity

Answers

0
Try to use -S -F1
Answered 12/19/2011 by: showitself
Senior Purple Belt

Please log in to comment
0
Also try using /f2 <path to logfile> to get a log for your setup. Might help you identify the problem better.
Answered 12/19/2011 by: pjgeutjens
Red Belt

Please log in to comment