"KBOX" DNS Entry
I currently have a ticket open with support. Ever since our 6.4 upgrade I have about 1,400 machines that lose their AMP connection. When I take a look at them the amp_auto.conf file is correct, but the amp.conf file just has host=kbox and the services have stopped. I've kept these machines semi-connected by running "amptools host=mykbox.domain.org" in my login script. At the next check-in it reverts back to just host=kbox.
When I brought this up to support they let me know that they have nothing that would be causing this. I also have a DNS entry to point "kbox" to one of my Kace servers. They have also never heard of this. I'm going on two weeks now of these machines having issues. I know I didn't dream up the DNS entry for "kbox", but for the life of me I cannot find any technical documentation to back me up. Right now I'm currently being told that something I'm doing is changing the name in the amp.conf file even though I had no issues at all on 6.3. Does anyone have any links that back this up, or has anything seen this especially on 6.4?
I created a custom inventory rule to inventory that file. Is anyone else seeing host=kbox?
ShellCommandTextReturn(cmd.exe /c type C:\programdata\dell\kace\amp.conf)
Answer Chosen by the Author
I ended up updating my SAN cert to include "kbox.mydomain.org". I applied to to all of my Kbox's and since then I haven't had any trouble. My best guess was the addition of Konea in 6.4 that may have caused this. Either way I know it's not a standard config.
I'm curious on how many customers out there run multiple Kace servers with SSL?
Answered 11/03/2015 by: dugullett
Please log in to comment
log in to commentPlease