/build/static/layout/Breadcrumb_cap_w.png
12/12/2018 460 views

I'm trying to run some Device Actions, but it seems that takes a PC, and my team and I all have Macs. However, we also have Parallels. I have set up the agent on my Mac, as well as my VM. Both are setup to use different networks, and have different KUIDs. Yet I still get BAD_MAC_IP when I run runkbot 2 0, and so it's not inventorying. Has anyone run across this or a similar issue? Any advice would be appreciated.

0 Comments   [ + ] Show comments

Comments


All Answers

0

It depends on what device actions you have. If the device action is not PC dependent( like launching RDP or ping.exe ) then you can use device actions from Mac as well.

If the Agent is not inventorying then please check few things like

1. Is there a AMP_CONNECTED file under data directory /Library/Application Support/Quest/KACE/data

2. check for error in konea.log or user/KAgent.log

3. Is the K1 server name in amp.conf resolving to correct IP.


This should tell you why the agent is not inventorying.

Answered 12/14/2018 by: AbhayR
Red Belt

  • My goal is to launch Teamviewer from a Mac. Are you saying that this is possible? Do you happen to know what device action that I would need to setup to get this to work? Also, I'm fine with it if I can just use Microsoft RDP. I just need a way to launch remote assistance.
    • In older Kace Versions there was a statement saying some Device Actions require the use of internet explorer because activeX was used.

      here is an approach of doing this teamviewer device action
      https://www.itninja.com/blog/view/teamviewer-kace-integration-1

      also, please note that runkbot 2 0 is inventory skript on Mac and runkbot 4 0 is the windows version.

      BAD_MAC_IP comes from having a duplicate KUID/Hostname/IP/MAC

      and another important point is to have a correct configured router / gateway so that your Windows Subnet IP and/or Mac Subnet IP actually gets published to your Kace Server. What i am trying to say is that i have noticed the same issue several times when i have connected a new remote site via S2S VPN and all the clients from the newly added site are appearing on kace with the same ip, the one of the gateway. Check the Kace Server Log where you have found the BAD_MAC_IP entries for the IP of the client. If it is your gateways IP you might use transfer LAN or NAT Rules to fix this issue.