We upgraded our K1100 to 6.3, and so now I'm attempting to upgrade the agent installer on our K2000 (still at 3.5, for now) to an updated version of the Agent software.  I've tried several different commands, but none seem to work.

On trying to deploy the 6.2 agent, my command was:

msiexec /i ampagent-6.2.1025-x86.msi HOST=123.456.789.1 /qb

The agent installs, but there's no amp.conf in programdata\dell\kace, so the Agent doesn't know what to contact.  The irritating thing is that when I run this command manually at the command line on the target system, it installs and correctly creates/configures amp.conf and checks in.  I've tried several variations of this command, swapped agent versions, etc but none seem to work.  

Anyone have any idea what I'm doing wrong here? Maybe another set of eyes can help.



1 Comment   [ + ] Show Comment

Comments

  • I've had to do that before as well. My task is also post-install. I always use both the Ip and name if the other don't work. DNS is a pain.
    Russ
Please log in to comment

Answers

0
We've had the same problem. We used a task with the line: msiexec /i /qb ampagent-6.4.180-x86_k1000.xxxx.com.msi. The agent installs but sets the host address=kbox. Obviously these clients never connect.

Installs using this task used to work but it stopped recently. As a workaround we've altered it to use the no UI switch instead of the basic UI. This seems to work every time. Not sure why? Installing manually using the normal UI also works.

This works: msiexec /i /qn ampagent-6.4.180-x86_k1000.xxxx.com.msi 
Answered 02/11/2016 by: Goggeh
Senior Yellow Belt

Please log in to comment
0

I use msiexec /qn /i ampagent-6.2.1025-x86.msi HOST=domain.edu and it works fine.  Are you installing on one system or the domain?  I seen the IP address so just wondering.

Russ

Answered 05/01/2015 by: rjobe
Fourth Degree Green Belt

  • this is a post-install task on individual computers, so pointing the installer directly at the IP of the KBOX, as I read others have had problems with deployment and using hostname (which I also saw).

    I currently have it working, but only by creating a new Agent postinstall task and then renaming the 6.3 agent to follow the task's nomenclature.
Please log in to comment
0
Please explain further?  What is the exact issue?

Corey
Answered 05/03/2015 by: cserrins
Red Belt

Please log in to comment
0
did you upload the new msi to this task?

to save having to upload the new msi after upgrades I have gone to calling the msi from the k1000

msiexec /i "\\kbox.tmcc.edu\client\agent_provisioning\windows_platform\ampagent-6.3.306-x86.msi" HOST=kbox.tmcc.edu /qn

Answered 05/04/2015 by: SMal.tmcc
Red Belt

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