Creating MSI script using KBOX 1000
I am fairly new to all of this, i dont have an extensive background in scripting. But i have to be doing something wrong. I created an MSI using the APP Deploy Repackager. I can run the MSI on my machine and it works. So i thought i would go ahead and upload this file into a script in KBOX. Here is what i did:
Attached the MSI as a dependency
Under Verify:
Directory: $(KACE_DEPENDENCY_DIR)
File: Myfile.msi
Under Remediation: (Launch a Program)
Directory:$(KACE_SYS_DIR)
File: msiexec.exe /i
Parameters: $(KACE_DEPENDENCY_DIR)\myfile.msi
When i run this script i can see where the msi file has been put on my computer, but it hasnt been ran. Is there something that i am missing?
Attached the MSI as a dependency
Under Verify:
Directory: $(KACE_DEPENDENCY_DIR)
File: Myfile.msi
Under Remediation: (Launch a Program)
Directory:$(KACE_SYS_DIR)
File: msiexec.exe /i
Parameters: $(KACE_DEPENDENCY_DIR)\myfile.msi
When i run this script i can see where the msi file has been put on my computer, but it hasnt been ran. Is there something that i am missing?
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
dchristian
13 years ago
Maybe this would be easier.
Instead of running a ksrcipt, change your script type to an online shell script.
Then upload your script as a dependency.
For the script text:
Just remember to change the script file name from script.sh to script.bat.
Instead of running a ksrcipt, change your script type to an online shell script.
Then upload your script as a dependency.
For the script text:
msiexec.exe /i myfile.msi /qn Just remember to change the script file name from script.sh to script.bat.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
