amp.conf Getting wiped?
Workaround create a windows task by using k1000 scripting feature and have this run on all of the machine. Of course you'll have to bring the "dead agents" back online for this to work. But once you have this taken care of, you won't run into this issue in feature. Again this is a work around not fix.
HOWEVER no one has ever been able to reliably reproducethe issue and engineering is convinced that the behavior is not caused by theappliance but rather by AV solutions / firewall / proxy or simliar in certainenvironments.
A workaround, which is supposed to avoid this behavior,is planned to be implemented in the 9.0 Version of the appliance (current ETAis August 2018).
In the meantime, what you could try is something likecreate an offline script which re-sets the hostname in certain intervalls (for exampleonce per week).
For devices that are already disconnected / have an emptyamp.conf we need to replace the affected amp.conf with a working one andrestart the agent or run "amptools.exe -resetconf host=your_fqdn" inthe agent binary folder on the affected devices.
You could use psexec (as explained here: https://support.quest.com/kb/127898) or a gpo for this.
We are currently investigating this issue. Not all customers are facing it (which would've been easier, so we can find the root cause) It seems to happen in some environments.
No settings or programming within the Kace Agent, are established to reset or reconfigure the amp.conf file. So I was wondering, could anyone help to check AV logs, Firewall, or in case those agents are remote, review load balancer or Proxy?
FYI renaming host, is the fastest way to get around this situation in meantime the investigation completes
Use the “Amptools.exe resetconf host=x.x.x.x” in order to rename host on client machines.
The AMPTOOLS command can be found in one of the following Windows-based locations and must be performed in an elevated (Run as Administrator) command prompt:
On 32-bit systems: C:\Program Files\Dell\KACE\
On 64-bit systems: C:\Program Files (x86)\Dell\KACE\
I opened case today, as we have recently noticed this issue still occurring. We are on 7.2 of the server and 7.2 of the agent. But some PCs still on 7.1 agent also have had this issue.
It can't be AV as Symantec would delete the file not empty the file.
And in the past the agent used to have 2 paths back to the server the URL name as well as the server's IP to ensure communication would not be so easily broken. But I don''t see that any longer in the flle.
We see this on WIN 7 32 and 64 and WIN 10 64.
And while you could run the amptools fix what if you can't remote to a system in the field?