How can I update agents that no longer check-in to KACE?
We had some issues with our physical K1000 box, ended up with a VSA which upgraded some clients, and then a newer VSA was installed. Most of my machines, approx. 800 out of 900, are running latest agent 8.0.152 and working correctly. The problem that I have with the other ~100 machines is that they are running different versions of the kace agent. They are either running 6.4.180, 6.4.522, or 7.2.10. The solution that I've found is to fully uninstall the agent, then have them run a gpupdate so that the 8.2.10 agent gets provisioned through GPO. The problem is that it's a large number of machines, and they are not always on the network. Sometimes they may only be on the network for a couple hours through the day. What I've been doing to this point is a couple times a day, exporting device names that have agent versions != 8.0.152, exporting that list to a text file, running a powershell that then generates a list of machines from that list that are actually online, then taking that list and running an uninstall script through psexec that goes through the online machines. It's just tedious as all heck and such a PITA!
Do you guys/gals have any suggestions on how I can get them cleaned up?
-
For the PCs that do connect to the network, you could setup a PS Script to do the uninstall task and then run a GPUpdate /force as part of a log on script. Then set a WMI filter on the GPO so it only targets devices with KACE Agent versions less that 8. This could possibly affect those that are outside the network but use a VPN to connect to the network as well. - DaveMT 6 years ago
-
This sounds like what I need. The query I put together uses the win32_product class, which is apparently a big problem for wmi filtering since it takes 1-2mins to run. This causes the filter to timeout, so I'm trying to figure out another class to use. - captains1stm8 6 years ago
Answers (1)
For all 7.x agents use the agent auto update feature (Settings | Provisioning | Agent Update) to do so.
They simply need a check in then (which is forced when they have contact to the appliance)
Comments:
-
For the < 7.0 agents, I can just create a 2nd gpo via the gpo provisioning tool, but how will it know to only uninstall the agents < 7.0? Also, for the the agents > 7.0, the problem is that they never checkin. They're online and I can ping them, access shares, etc, but I'm unable to get them to communicate with the k1000. Even if I log onto the problematic machine, and do a runkbot 4 0, it will not checkin. - captains1stm8 6 years ago
