Understanding that everyone's distro of EX might be a little different, these are not proven instructions for everyone that will definitely work with no changes. This is just the deployment that I developed that worked for me on Win 7 and Win 10.
First a few details on the normal installation of Jenzabar for our environment. Our install package usually consists of the installer.exe file, a .dat file that contains answers for the installer about what menus to show, where certain databases and help files are located on network drives etc, and a shortcut with the following target info. |M:\install\EX_6.x\EX_6.3.3_Setup.exe /v"/qb+ SETUPFILE=\"m:\install\EX_6.x\ex_setup.dat\""|. Traditionally the installation folder is relocated to the users desktop and the shortcut is edited to reflect the correct file path to the installation files. We then have to run the 6.3.3 HotFix, which is just a simple install. The trouble with the Kace deployment package was correctly targeting the files without knowing the exact file path ahead of time. The following was my method for creating the deployment.
Create a batch file to replace the shortcut, which will be located in the same directory as the installation files during the deployment. My batch has the following text. |EX_6.3.3_Setup.exe /S /v"/qn SETUPFILE=\"%~dp0\ex_setup.dat""| . The /S and /qn are the variables which make the install silent. The /v passes everything inside the following quotes on to the windows installer for use as the answer file. The %~dp0 fills the correct file path for the current directory.
Compile the .exe, the .dat, and the .bat into a .zip using 7-Zip.
Associate the zip with the correct software inventory per usual.
My deployment used the following settings
Use Associated File
Override default installation. Full Command Line: setup.bat (name of my .bat)
Don't Prepend msiexec.exe
And that's it. Seems simple writing it out, but took a while to figure out. Hope that helps!
Setup Information:
Setup Type: Windows Installer (Delivered as an EXE)
Deployment Method Used: Vendor Provided Command Line (answer file driven)
I have tried to use a Managed install without the batch and place the command line command similar to what you have in override default installation. The installation fails. Looking at the logs, the error message comes up as unable to load properties from text file (ex_installer_parameters.dat) and unable to load setup files settings (ex_installer_parameters.dat). I do not get this error on a Windows 7 machine. I get this error on Windows 10. Any ideas on what causes this? -
fleminsa
7 years ago
This website uses cookies.
By continuing to use this site and/or clicking the "Accept" button you are providing consent
Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our
websites or when you do business with us. For more information about our
Privacy Policy and our data protection
efforts, please visit
GDPR-HQ
