Managed Distribution with a ZIP file
I've been struggling with a managed installation of a SAP GUI client. Since there is quite a bit of data we packaged all of the files a ZIP file and attached that to the software title.
I've turned of pre-pend msi.exe and changed the command line entry to the following.
.\SAP\Setup\NwSapSetup.exe /package:"SAPGUI_KHRIS_710" /silent
This continues to fail with the following error:
Error executing: '.\SAP\Setup\NwSapSetup.exe /package:"SAPGUI_KHRIS_710" /silent': System.ComponentModel.Win32Exception: The system cannot find the file specified
The file is there and the command can be executed from the cmd line from the kbot directory and it works.
We've setup an install in the Software Library and use the same entry for the command line and the install works.
What am i missing??
I've turned of pre-pend msi.exe and changed the command line entry to the following.
.\SAP\Setup\NwSapSetup.exe /package:"SAPGUI_KHRIS_710" /silent
This continues to fail with the following error:
Error executing: '.\SAP\Setup\NwSapSetup.exe /package:"SAPGUI_KHRIS_710" /silent': System.ComponentModel.Win32Exception: The system cannot find the file specified
The file is there and the command can be executed from the cmd line from the kbot directory and it works.
We've setup an install in the Software Library and use the same entry for the command line and the install works.
What am i missing??
0 Comments
[ + ] Show comments
Answers (9)
Please log in to answer
Posted by:
cmccracken
13 years ago
Hey Craig,
Welcome to the forum. Is your installation command set to "Use Default" or "Configure Manually"? I use all zips, and run all of my installs as configure manually.
Casey
Welcome to the forum. Is your installation command set to "Use Default" or "Configure Manually"? I use all zips, and run all of my installs as configure manually.
Casey
Posted by:
cmccracken
13 years ago
I usually create a setup.bat file to hold all of my instructions, then I can just say "setup.bat" as the command. Perhaps that would help?
Casey
Casey
Posted by:
cblake
13 years ago
It's recommended that your installer be at the root of the ZIP, not in subdirectories. Though, as cmccracken
Posted by:
rmeyer
13 years ago
I also create a batch file for zip installation then it always works :)
Posted by:
GillySpy
13 years ago
The file is there and the command can be executed from the cmd line from the kbot directory and it works.
Do you possibly really mean kbot directory? if not then your test is not comparing apples to apples -- for a managed install your file should be extracted to
c:\program files\kace\kbox\downloads\<swid> and then run from that directory
What is in that directory?
Also don't forget all these things:
http://www.kace.com/support/kb/index.php?action=artikel&cat=4&id=821&artlang=en
Posted by:
MoranTug
12 years ago
relative paths do work, but you cant use .\ or \, if you call the files from DIRECTORY\, that seems to work for me
Comments:
-
That's it! In our case (msiexec.exe /i ".\Bridge\Build\Bridge.msi") did not work but (msiexec.exe /i "Bridge\Build\Bridge.msi") did. - rtrinidad 5 years ago
Posted by:
ScottinOkla
12 years ago
Searching for this error message in the forums brought me to this thread. I can't believe that the best solution is to imbed a batch file inside of the ZIP and run it that way. I was unable to get the install to start using $(KACE_DEPENDENCY_DIR) and had to hardcode the batch file to use C:\Program Files\KACE\KBOX\downloads\3053\
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.