Has anyone had any sucess rolling out the KBOX agent via GPO Software Installation? I'm using "KInstallerSetupSilent.msi" and have written a custom transform file which specifies my server name, SSL use, AMP over SSL. I've tested that the transform works by applying it manually.

When trying to rollout the MSI (with MST) via GPO, it just will not work correctly. It's throwing an error 1603 in the log, which is a generic "installer encountered a fatal error" message. I've doublecheck that the permissions on my distribution point are correct, checked that I'm using the ALLUSERS property correctly, but to no avail.

I've turned up MSI logging, but all I get is the message "DoAdvertiseScript is returning: 1603" and that doesn't shed any light on what's going wrong. Anyone able to do this successfully?
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Wish I could help, but I've never tried via GPO. I deployed most of my agents using logon scripts - which gave me no trouble.
Answered 04/16/2010 by: airwolf
Tenth Degree Black Belt

Please log in to comment
0
Here's what we use. There's a GPO applied to all Computer OU's to ensure KBOX is installed:

  • The GPO tells the computer to run a script at startup (Computer Configuration/Policies/Window Settings/Scripts/Startup) with a UNC path to the script. My UNC path will be different for you: \\sam\autoinstall$\KBOX\provision.cmd
  • The "provision.cmd" script checks for normal pieces of KBOX and if not found installs KBOX. The script contents are included below: @echo off
    cls

    echo Please wait while KBOX is installed...

    if not exist "%ProgramFiles%\KACE\KBOX\KBOXClient.exe" (
    goto KBOXinstall
    )
    if not exist "%ProgramFiles%\KACE\KBOX\KBOXManagementService.exe" (
    goto KBOXinstall
    )
    if not exist "%ProgramFiles%\KACE\KBOX\KBOXSMMPService.exe" (
    goto KBOXinstall
    )


    exit

    :KBOXinstall

    ping -n 90 -l 0 localhost 1>nul 2>nul
    \\kbox\client\!install_kbox.cmd

  • Our KBOX has the default name of kbox and the Samba share is turned on so the contents of the "!install_kbox.cmd" calls the standard \\kbox\client\agent_provisioning\windows\<silent kbox installer> (our KBOX is down right now or I'd include the actual script name and contents).

This works well for us to ensure all PC's have the client installed using an AD GPO.
Answered 04/16/2010 by: RichB
Third Degree Green Belt

Please log in to comment
0
The is a KACE knowledge base article on how to use the "KInstallerSetupSilent.msi" in GPO
http://www.kace.com/support/customer/faq/index.php?action=artikel&cat=2&id=848&artlang=en

Unfortunately, you may have run into an known issue, that should be resolved in a future release.
Answered 04/17/2010 by: KevinG
Purple Belt

Please log in to comment
0
Have you thought about using the deploy bat file instead of the MSI? It can be parameterized with all the customizations you need, has verbose error checking, and I've seen it used successfully in a GPO.
Answered 04/19/2010 by: jkatkace
Purple Belt

Please log in to comment
Answer this question or Comment on this question for clarity