Updated the advertised agent to 6.4 and about half my inventory stopped reporting in
It seems an agent update failure has occurred on a pretty big scale in my environment. I've jumped into several branch office servers to manually perform the update and it asks me for the location of a 5.4 agent msi that I simply don't have, so it fails to remove "the old version" (even though everything was definitely running on 6.3 prior to the update).
Any guidance from my esteemed colleagues?
1 Comment
[ + ] Show comment
Answers (3)
Please log in to answer
Posted by:
SMal.tmcc
9 years ago
you can use amptools to uninstall, then provision the new client out
AMPTools.exe uninstall all-kuid
Comments:
-
it they are still allowing you to run scripts on these machines you can create a uninstall and install new agent batch script. upload the new agent msi as a dependancy - SMal.tmcc 9 years ago
Posted by:
jknox
9 years ago
If the update is asking for the 5.4 agent, it was installed by GPO and the file isn't available at the location used for the GPO. Typically, you could recreate the location and put the 5.4 agent msi there. Support could help, but if you truly have the 5.4 agent on clients and wanted to upgrade to 6.4, it would be easiest to uninstall the 5.4 agents and install the 6.4 agent.
Comments:
-
You are correct in that it was installed via GPO. The kicker is it was successfully updated to 6.3. It was only a hop from 6.3 to 6.4 that asked me for the ol' 5.4 msi file. - iMonkey 9 years ago
Posted by:
kevin.j.reagan@gmail.com
9 years ago
We wrote a KACE Health Script whose purpose is to guarantee that the agent is installed and is operational. It has an option to update the agent if the currently installed agent is not at the desired version.
http://www.itninja.com/question/k1000-keeping-agents-healthy
Kevin
The Update agent function worked well on the previous versions.Possibly a problem with the 6.4 agent. - ridnar 9 years ago