How to update agent 5.4 to 6.x after v5.5 K1000 bites the dust?
Our v5.5 K1000 died and our Server Admins built us a brand new v6.x K1000. The previous backups were found to be corrupted and therefore not usable.
The v6 K1000 will not see the clients with the older agent, and trying to provision machines with the agent already installed fails.
What would be the best way to update the agents without physically visiting each machine?
The v6 K1000 will not see the clients with the older agent, and trying to provision machines with the agent already installed fails.
What would be the best way to update the agents without physically visiting each machine?
1 Comment
[ + ] Show comment
Answers (3)
Please log in to answer
Posted by:
rockhead44
9 years ago
If you have Active Directory, package the k1000 agent .msi (found in your client share) and distribute via Active Directory.
http://www.itninja.com/blog/view/how-to-update-gpo-kace-agent
Posted by:
Nico_K
9 years ago
check at first if the new appliance has the same dns name (since the agents try to connect the appliance with the hostname they know from their amp.conf)
if this is not the fact the easiest way would be:
remove all agents from the clients and deploy a new one using a GPO.
If the dns name is the same (or can be changed to this) the appliance itself can update using the own auto update.
The Auto Update is found under: Settings > Provisioning > Agent Update
if this is not the fact the easiest way would be:
remove all agents from the clients and deploy a new one using a GPO.
If the dns name is the same (or can be changed to this) the appliance itself can update using the own auto update.
The Auto Update is found under: Settings > Provisioning > Agent Update
Rockhead44s idea is a good one but has one flaw: if there is an old agent found this may fail.
Comments:
-
We are nearly in the same boat (running 5.5 and plan to upgrade to 6.4). I am concerned about the auto update process actually working. We can if need be update via gp. For our macs it would have to be local or via ard. Has anyone made this jump before with Mac and PC clients? Guidance is welcome. - Jbr32 9 years ago
Posted by:
jgeorge
9 years ago
Once again I would like to thank everyone who responded to this question.
What we ended up doing is to use the provisioning schedules to run the uninstall routine, then re-run them with the installation routine enabled.
Here are more details:
What we ended up doing is to use the provisioning schedules to run the uninstall routine, then re-run them with the installation routine enabled.
Here are more details:
Uninstall the KACE agent through Advanced Provisioning.
1.Select Settings > Provisioning. The Agent Provisioning page appears.
2.Click Provision Agents.
3.Select the Uninstall option.
NOTE: You may need to use two different sets of credentials, depending on how the target computer is set up. Some computers will respond to using the local Administrator Account, while others may need you to use your Domain account.
If the agent will not uninstall after running the uninstall option twice, you may need to log on to the machine and uninstall the agent manually.
Ref: https://support.software.dell.com/k1000-systems-management-appliance/kb/128865
The K1000 hostname and IP address are the same as before so I don't think the problem is DNS related. - jgeorge 9 years ago