I've just installed some new agents and noticed they are at 6.2.0.4 with no KLC version information displayed. The existing agents are at 6.2.0.0 - 1.2.0.22 At the top of the panel I can see "Force update even if agent is at version 6.2.0.0 - 1.2.0.22". If 6.2.0.4 is the latest version then why isn't this showing given the VSA knows there is a later agent version??? Also, I'll probably regret asking this, but is there a readme for agent releases so we can determine if the update is worthwhile or needed? The new agents I pushed out didn't have the KLC version next to them yet when I force updated them this was pushed out too. Do I need to do something extra here (like update the package?) at the time of initial installation. I don't want to have to revisit new devices to get the latest KLC pushed out too, or is there another explanation???? Thanks, Daz.
Sorry for formatting, stupid forum software munged the original. Feel free to fix this Kaseya .......
Yep, I use an advanced data filter for a view too - for Agent Version I use
< 6020004
I also have "Machines that have been online in the last 1 day" selected in the view.
Then, periodically, I'll go select that view (named "old agents online now") and select all, check the "force" box, and hit update - if it's just a few I'll schedule them with a distribution window of 1 minute so they all get pushed asap, if it's a lot I'll spread it out over a longer timeframe.
And I always use "attempt to power on machine" as well - it works sometimes, and what the heck, I might pick up an extra machine or two that need updating!
I noticed this today too. I couldn't KLC to a machine, and after updating the agent (and restarting the workstation) we could...
Does annoy me when there is an update like this as it becomes a bit of a logistical nightmare to update the machines checking in. It would be extremely helpful if Kaseya could chip in here and let us know how important updating connected machines is, I'm doing it anyway but would like an indication of how much bandwidth is required for this update.
More importantly it would be REALLY useful if Kaseya can inform us so we can plan to push these out. Having an area on the Kaseya website somewhere that we can go and read information about the latest patches etc. would be handy to me, I know a lot of people won't bother but I do like to know what's going on. When there are system updates I apply semi-manually and read the descriptions that go along with them though often these seem to be written in secret-kaseya-dev-code.
I am also having this issue.
New agents that get installed fresh show as 6.2.0.4 without any KLC suffix at the end
Existing agents show different versions ranging from
6.2.0.0-1.2.0.22
through to
6.2.0.4-1.2.0.22
It doesn't seem to matter what I do as far as forcing updates goes I can't seem to get all the agents to fall into any current standard version. I would assume if I forced an update across all agents then they should all update to version 6.2.0.4 - 1.2.0.22, but they don't
I suspect it is something to do with this update that we had to manually run a while back to force the Update Agent section to show KLC versions?
community.kaseya.com/.../klc-connection-relay-improvement-patch.aspx
Perhaps the agents ARE actually up to date but the above hotfix broke the way it reports back its version, or the way it gets displayed in the Update Agent section?
Anyone else had any luck or hopefully Kaseya can supply a comment?
Thanks
Dwayne
Hi Dwayne, I find that if the agent is reporting to be just 6.2.0.4 then when I go to update agent it happily lets me update which results in 6.2.0.4 - 1.2.0.22 if however I try to update 6.2.0.4 - 1.2.0.22 it tells me that it's already up to date and doesn't need updating. Obviously if I tick the box to force an update it also works fine. So not sure why yours doesn't update if only at 6.2.0.4.
so if agents are not on the latest, can we just select update without needing to force the update?
It would be useful if there was a tick-box to hide agents that are current. trying to accurately click the tickboxes to select agents on 6.2.0.0 but not 6.2.0.4 from half way across the page is doing my head in.
normally i'd just select them all and not worry, safe in the knoledge that current agents won't be upgraded since the 'force update'...tickbox is unticked. But with that tickbox still reading 6.2.0.0, I'm worried that agents already at 6.2.0.4 will be needlessly upgraded again.
Create a view using an advanced data filter - Agent Ver NOT 6020004
Just an update for those looking at the system - I'm now seeing the latest agent as 6.2.0.8. For the filter, I've set mine to be NOT *6020008*. This will pick up any prefix, suffix, or additional information after 6.2.0.8 (eg: 6.2.0.8.1, should it ever get to that)