The amp.conf dilemma....
You've all seen it. Even at 9.1.204 we still see it. Right now I'm going through a list of hosts all of which are physically "online" and pingable but show as "offline" in KACE. When I investigate further by doing an RDP to the machine and checking by doing a kstatus, I see "no" for both "running" and "connected". When I check the amp.conf, it's not blank, it has the correct "host=kbox" at the top, but nothing else. As I said, the "host=" entry is there and I can resolve the kbox DNS name from the client. I can ping the Kbox directly from the client. NOW, If I replace the amp.conf with a known good one from a working system and do a "amptools restart" the system comes online and checks in. Unreal.
For the life of me I cannot figure out what causes this. I've seen all the posts on this with no real solution. I understand Quest says it's not their problem and it's my environment. All of the KACE directories are white-listed in our security endpoint/virus solution so they don't get touched. That isn't the problem, since I have thousands of other machines that have never had this issue. So for now, I've resigned to create a script that I can target to affected machines that replaces their amp.conf with a know good copy and restarts the amp agent. The problem is that on some systems, I have to do this once a week! I have a few replication servers that drop off once a week. I'd love to talk to anyone else that sees this. We were told that this problem would go away with v9 but it's exactly the same as it was with v7 and v8.