How to deploy software with dependencies with the KACE
I am trying to install Microsoft SQL Command Line Tools through KACE. It has a software dependency that the SQL ODBC Driver also be installed or the installation will fail. No matter how I write the script, it kicks off both the Command Line Tools and the ODBC Driver installation at the same time, which leaves me with the ODBC Driver, but not the Command Line Tools since it fails. I am very new to Kace and really struggling with this one.
I have tried a KScript and a .bat script, but they both will not pause between the two installation. I would greatly appreciate any ideas to get me going in the right direction.
I have tried a KScript and a .bat script, but they both will not pause between the two installation. I would greatly appreciate any ideas to get me going in the right direction.
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
Hobbsy
7 years ago
Have you tried creating a script with multiple steps, so the first step is the check to see if SQL ODBC driver is installed, and the second is then the installation of the SQL command line tools.
With the first step, it should check for the installation and on failure run the installation of the ODBC driver, that way if it is already installed it will skip to the main install on the second step
Comments:
-
kscript is the best way. can you update the question and put a screen shot of your kscript that did not work for you. - SMal.tmcc 7 years ago
Posted by:
taylora
7 years ago
Thank you for the suggestions. I did some more research and found out my arguments when installing were wrong. Here is what I needed:
ODBC Drivers - arguments of: /i /quiet /passive /qn IACCEPTMSODBCSQLLICENSETERMS=YES ADDLOCAL=ALL
Microsoft Command Line Utilities - arguments of: /i /qn IACCEPTMSSQLCMDLNUTILSLICENSETERMS=YES
I sent it out as a managed installation with the ODBC being a priority 1 and the Utilities a priority 2. It worked great. I may eventually re-write it as a script, but it has been installing without issue through managed installations.
ODBC Drivers - arguments of: /i /quiet /passive /qn IACCEPTMSODBCSQLLICENSETERMS=YES ADDLOCAL=ALL
Microsoft Command Line Utilities - arguments of: /i /qn IACCEPTMSSQLCMDLNUTILSLICENSETERMS=YES
I sent it out as a managed installation with the ODBC being a priority 1 and the Utilities a priority 2. It worked great. I may eventually re-write it as a script, but it has been installing without issue through managed installations.