Issues with upgrade of k1000 to version 7
Hi Guys,
I have just upgraded to the latest version 7.0.121306.
I have also pushed the agent update to version 7.0.763
via the agent update settings.
Since the upgrade, I have been having a number of issues.
Of the 1500 machines in my network, only around 50 are
show to be turned on...(with a blue screen aicon). All the rest
have a red line across the tiny screen icon....(meaning they are offline).
Also its been about 36 hours since initializing the agent update to
the latest version. Again, only about 60 machines are showing
an updated agent. The rest are showing as offline with old agents.
Any ideas? Something seems to be wrong.
Thanks.
2 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
ttucker
7 years ago
Call Kace support. I had the same issue and they had a hotfix they applied that corrected it. Apparently from what the guy said the machines are actually connected but flagged incorrectly in the database so Kace treats them as if they were disconnected. The hotfix took about 30 seconds to run and did not require a reboot of the appliance. It has only been about 14 hrs since I applied it but I am back down to my normal number of disconnected machines. Also support told me that 7.1 update and 7.1 agent will be out this week or next and they have that hotfix built in along with other fixes and support for Windows server 2016.
Here is a link to the KB article about the disconnects. Ask them for a hotfix for this.
https://support.quest.com/kb/217012
1 - Quest informed us that there could be congestion and the agents may still check in, just much slower than normal for their initial check-in after upgrading their client.
2 - we preformed a retrust action ("C:\Program Files (x86)\Dell\KACE\AMPTools.exe" retrust) then restarted the service ("C:\Program Files (x86)\Dell\KACE\AMPTools.exe" restart)
3 - Quest delivered a hotfix to us to address this known issue.
4 - Quest has elevated our situation to Level 2 for tickets.
Now we did see a few system start talking after a while for the answer to number one, but not a lot. The Retrust helped to get agents talking again. We would either run it manually on the systems or run it via a startup batch file via GPO. But this didn't completely resolve it. The Hotfix did nothing to solve our issues. We are working with Quest in this issue getting elevated but we are also having an issue with machines not completing Inventories as well.
I hope this was of some help for you to give you a direction or a few things to try. - DaveMT 7 years ago
I've the exact same issue even with the newest release, 7.1.62. Machines with agent 7 will not respond to force inventory requests and sometime go 20+ hours with no inventory!
My only solution was to push out the old agent 6.4.522 to all machines. - Darkplace 6 years ago
But this was my solution to the problem...given to me by kace.
Hope it helps you.
https://support.quest.com/kb/127898 - akmagnum 6 years ago