When using the K2000 to install the K1000 client, the client installs, but will not communicate with the K1000


    We've been using the K2000 for PC deployment for some time now. We have the K1000 client  set as a post installation task during the process.

 The install goes fine and looks as if  all is well with the PC, but when checking the K1000,  no communication  happens between the fresh PC and the server.

If I manually uninstall/reinstall the K1000 client, communication  picks right up.

Our K2000 is not currently on the network .  Not sure if its a requirement when running the install.

The install command we are using is below. Any ideas? Our  K1000 server name is Kbox1000. I'm using the example commands that  came with the k1000 client  sample on the K2000.

msiexec /i ampagent-5.5.30275-x86.msi HOST=kbox1000 /qb-


Dave R.

1 Comment   [ + ] Show comment
  • Have you tried the tested method of renaming the MSI file so in your case it would look like ampagent-5.5.30275-x86_kbox1000.msi
    and then putting that into your post install task on the K2000 with a command like

    msiexec /i ampagent-5.5.30275-x86_kbox1000.msi /qb - Hobbsy 5 years ago
    • I was hopeful, although not sure why, but that did not work. Thanks for the try, Hobbsy. I hear we'll have to update to 6.0 soon, so maybe that will fix it. - DRogers 5 years ago
      • We are experiencing the same issue and we are on v 6.2. - tdickert 5 years ago

Answers (1)

Posted by: SMal.tmcc 5 years ago
Red Belt
your host switch is wrong.  You want the full name  host=kbox1000.acme.com
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