/build/static/layout/Breadcrumb_cap_w.png

Scripting Question


Windows Carbon Black Scripted Deployment

07/17/2017 4194 views

It seems to not want to install the Carbon Black via scripting and Distribution via the K1000.

 I am trying to the scripted install with the following parameters below.

msiexec /i installer_vista_win7_win8-64-2.1.0.8 COMPANY_CODE=Company Code /qn /passive /L* C:\windows\CbLog.txt    OR msiexec /i installer_vista_win7_win8-64-2.1.0.8.msi /q /L* msi.log COMPANY_CODE=Company Code

6 Comments   [ + ] Show comments

Comments

  • Can we get the error?
    Also try this and let me know if it works:
    msiexec.exe /i "installer_vista_win7_win8-64-2.1.0.8" COMPANY_CODE="Company Code" /qb /L* C:\programdata\CbLog.txt
  • verify - on_verify_success
    verify - on_verify_failure
    verify - launch_program
    Launching program: 'C:\ProgramData\Dell\KACE\kbots_cache\packages\kbots\199\kace1045.bat' '' wait='false'

    Debug Log

    Running kbot: runkbot 199 1500388508
    KBotScript::LogScriptInfo - Start
    id=199 name=Carbon Black version=1500388508 type=policy
    execute disconnected=false logged_off=true
    execute events
    KBotScript::LogScriptInfo - Finish
    KBotScript::LogScriptInfo - Start
    id=199 name=Carbon Black version=1500388508 type=policy
    execute disconnected=false logged_off=true
    execute events
    KBotScript::LogScriptInfo - Finish
    KBotScriptManager::CleanupDependencies - clean up dependencies in kbot directory C:\ProgramData\Dell\KACE\kbots_cache\\packages\kbots\199\
    CleanupDependencies: file installer_vista_win7_win8-64-2.1.0.8.msi is part of the dependency list, keep the file
    CleanupDependencies: file kace1045.bat is part of the dependency list, keep the file
    runkbot ----- launching [path='C:\ProgramData\Dell\KACE\kbots_cache\packages\kbots\199' program='kace1045.bat' parms='' wait='false'] -----
    runkbot ----- completed [exitCode=0] -----
  • it appears the script runs, but program doesnt install
  • What are the contents of kace1045.bat
  • C:\Windows\System32\msiexec.exe” with params C:\Windows\System32\msiexec.exe” with params “/q /i $(KACE_DEPENDENCY_DIR)\installer_vista_win7_win8-64-2.1.0.8.msi /L *vx log.txt COMPANY_CODE=FNUFG6BD$(KACE_DEPENDENCY_DIR)\installer_vista_win7_win8-64-2.1.0.8.msi /L *vx log.txt COMPANY_CODE=Company code .... this is the latest attemp
  • Lets rewind and try a new approach. Set up the script like this:

    Launch a program...

    Directory: $(KACE_SYS_DIR)
    File: Msiexec.exe
    Parameters: /i "
    $(KACE_DEPENDENCY_DIR)\installer_vista_win7_win8-64-2.1.0.8" COMPANY_CODE="Company Code" /qb /L* C:\programdata\CbLog.txt

    Set the 'Wait for completion' and 'visible' check boxes.


    Give this a try and then see what you get.
    • Also make sure that you have installer_vista_win7_win8-64-2.1.0.8 uploaded under dependencies.
      • What is your recommendation on as windows run as. we tried all the options and the last few time we put in a domain credential.
      • I run pretty much everything as system

All Answers

0
You're logging the installation so open the log, find the text "Return value 3" and the half-dozen or so lines above that will detail what went wrong.

/qn /passive
If the installation isn't even working (you will have tested this on a VM beforehand, right?), I suspect that it's because of the above, where you've used 2 different UI-operating switches. Stick with one or the other.
Answered 07/18/2017 by: VBScab
Red Belt

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

View more:

Share

 
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