KACE Product Support

On PC1497 check the amp.conf to see if it has been blanked. You can compare it to a machine that is checking in to see what it should loo like.
Check DNS to make sure it can resolve the name.

To the KBOX when a machine isn't checking in, there is no way, from the status area, to know if it is just not checking in or if it has been disposed of. Both look the same way. This is where assets can come in and you can create a field that lets you change the status from say Active to Inactive.

You may want to consider a process change to where you delete the record of a machine you dispose of in the KBOX right away so that you don't have old items taking up a license key. - nshah 9 years ago

I did a test yesterday, I send out uninstall parameter to this machine (pc1497) then i pushed the agent out again, now its reporting,

It was not successfull with re-install, till i removed the agent. So my plan is to send out an uninstall to the whole enterprise, then force re-install, to get all clients attached ... - it-services 9 years ago

Seems a waste of effort as you run the risk of new issues arising when you uninstall a working client. I strongly believe in the mantra that "If it ain't broke, don't fix it". - EdT 9 years ago

The main fact why online-offline scripts do not work is cause Kace tries to push out the notification to the asset Name, on my Company "pc****".

so i can not even use Skript to remove the Agent, and cause the Agent provisioning does the REMOVE of the Agent every singel time i hit the button , I will never finish this Task.

i have user they are not in the Company for weeks, so how can I just uninstall the "damaged" agents, and do not deinstall the Agent on a machine I mark as proofen "good" ... oh man ... I already walk at the edge of KACE on my 3rd day of working with this console ... - it-services 9 years ago