How to fix 7.1 agents so they check into inventory themselves?
We recently upgraded our K1000 from 6.4 to 7.1.149. Since then, I have been testing out the 7.1 agent on a couple machines, which are now having trouble checking into inventory themselves. The machine status shows that they are online, but shows that they have not checked in over a day. If I manually run Runkot.exe 4 0, then the test machines will check in. I already have opened at support ticket with Quest, but the engineer is not able to determine the issue. Also the following steps have been taken to try to resolve the issue.
1. Making sure Powershell scripts are not blocked.
2. Running AMPTOOLS.exe retrust, restart
3. Having the Quest engineer check the logs
4. Stop / Restart Konea service
From what I been reading, that this is a common issue and some people are just sticking with the 6.4 agent. Has anyone had any luck getting the new agent to work properly? If sticking with the 6.4 agent is the only work around for now, then I will just need to roll back a couple of machines.
9 Comments
[ + ] Show comments
Answers (0)
Please log in to answer
Be the first to answer this question
https://support.quest.com/kace-systems-management-appliance/kb/226357 - Channeler 7 years ago
Support Response:
I was making some test in my test appliance and notice that starting in version 7 mapped inventory field should not be set to "none" or any other option other than "System Name".
Go to Assets > Assets types > click on device asset and check the Mapped Inventory Field, ensure that is set to "system name".
I have recently changed this to have the mapped inventory from BIOS serial number and serial number instead and will be leaving it for a few days to test it. - RyanPersaud 7 years ago
As for now, we are still sticking with 6.4 agents, I have already rolled back the few test machines, which seem to me checking in again.
We got Dell and Quest looking into this issue. Once I get some info back, will let you know. - Jkimberlin 7 years ago