Scripting Question

Install Kace on mixed network

11/24/2015 1420 views

I am tasked with install Kace k100 on all users in our Company

My network is a mix of domain and workgroup users and some work from the field on mixed networks.

Does anyone have a script that can reach out to a www-URL and then run the agent.msi?

Thanks in adance

Answer Summary:
1 Comment   [ + ] Show comment


  • I tried this so far msiexec.exe /qn "http://www.noname/testem/test.exe"
  • This content is currently hidden from public view.
    Reason: Removed by member request For more information, visit our FAQ's.

Answer Chosen by the Author

You would probably need to do this similar to how the agent is set up for GPO.  You would basically rename the .msi file to include the hostname for the K1000. https://support.software.dell.com/k1000-systems-management-appliance/kb/111244

Basically, this: ampagent-5.4.1000-x86_HOSTNAMEOFK1000.msi

Once you had that, you would need an internet accessible share to pull from.  The install at that point would just be msiexec /i ampagent-5.4.1000-x86_HOSTNAMEOFK1000.msi /qn
Answered 11/24/2015 by: jknox
Red Belt

  • The right command line to have the installation silent is the following:
    msiexec /i ampagent-6.4.180-x86.msi HOST=your.k1000.fqdn /qn
    Kind regards,
    Marco - StockTrader
    • That works equally as well. My way works better if they make it available for direct download for clients.
    • I have tried this before and it did not work. The agent installed but was not reporting back to Kace
      • Your K1000 has to be available externally and the K1000 and client both have to be able resolve each others IP and hostnames:


      • Both are visible the problem was with the text file with the Hostname in it was not created from the msi
  • Here is the method I used msiexec.exe /qn http://www.corpwebsite.com/ampagent-6.3.314-x86_kbox.oursitehere.msi

All Answers

What text file?  Are you talking about amp.conf?
Answered 11/24/2015 by: jknox
Red Belt

  • Sorry, yes the conf file was not created
    • You have some other problem then as the amp.conf file should always be created.

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:


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