When using Zipped Packages:
The K1000 appliance agent uses different mechanisms for processing/executing zipped installs between Managed Installs and Installs posted/deployed using the Software Library. This is most noticeable when you look at the directory in which the install package is downloaded to on the client system.
Managed Install: C:\Program Files\KACE\KBOX\<SoftwareID>\
Software Library Install: C:\Program Files\KACE\KBOX\downloads\<SoftwareID>\unzipped\
When using Answer Files:
In most cases there aren’t any complications as the agent takes into account the path differences and executes the install using the parameters set in the Managed Install or Software Library Item. If the Install Command Line used references a certain answer file you may have to adjust the Install Command Line used for the Software Library Item to compensate for the different path (vice versa if you created your Software Library Item prior to your Managed Install).
(Managed Install Example: setup.exe –silent –responsefile C:\Program Files\KACE\KBOX\<SoftwareID>\files\answer.txt)
(Software Library Example: setup.exe –silent –responsefile C:\Program Files\KACE\KBOX\<SoftwareID>\unzipped\files\answer.txt)
In some cases the Custom answer file referenced references files based on paths as well. You may have to create 2 custom answer files to compensate for the path differences as well. In most cases you can have 2 answer files in the same package and call the desired answer file using the Install Command Line structure required for that application install.
When using Multi-Level installations:
Another thing to note is when the Software Library Install completes the downloaded installation packages is automatically deleted where as the Managed Install package provides the option of deleting files or not deleting files. In some cases for applications that initiate the install with the original executable then call other executables (or other installer package) to complete the install the files may be deleted prior to install completion. This typically occurs when the install initiating executable is closed before the application is fully installed (which is typically triggered by the installer itself and not by any outside action). To compensate for this the use of a batch file or other scripting method may be the best course of action for initiating the install. Using a script of some sort will allow you to script in a delay. Since the Agent will see the script still running it will not trigger the deletion of the install files until the script has completed. The delay being part of the script allows the install initiator to close out and have the follow-up installations continue for the set time in the delay.
For information on how to set a delay in the scripting method chosen please consult that manufacturer’s documentation. If you are unable to locate the information on the manufacturer’s website or documentation you may try checking the already documented methods at http://www.appdeploy.com. You may find someone else has already done all the work for you or there is someone in the forum that can help.