We are rolling out a Kace 1000 for inventory and software/patch management but having some issues with Macs connecting. 

Our environment is Windows Active Directory and all PCs are provisioned via AD GPO.  That seems fine.  
My issue is Mac computers on the domain in the same AD groups do not provision.  I have been testing the Single Agent Provisioning and scheduled provisioning to target the Macs by IP address.   

The Mac systems seem to provision but never show up in inventory.  They connect to the k1000 but get stuck at step 5 Client Sync - Waiting...
The AMPAgent is running on the local systems.  Remote Management and Remote login are enabled on the test Macs.  I can ping the k1000 from the target systems and can access the Kace network shares where the agent installers are located.  

Here is the client log: 
  [08/14/14 10:02:13 AM] Begin provisioning...

  [08/14/14 10:02:13 AM] Executing Unix platform provisioning. 

  [08/14/14 10:02:13 AM] Probing tcp ports for accessibility. 

  [08/14/14 10:02:13 AM] Port 22 [ssh] open. 


  STEP 1: CONNECT TCP/SSH - SUCCESSFUL



  STEP 2: AUTHENTICATION - SUCCESSFUL


  [08/14/14 10:02:13 AM] Target is osx-x86_64. 

  [08/14/14 10:02:13 AM] K1000 agent NOT detected via ssh query. 

  [08/14/14 10:02:13 AM] Attempting remote agent installation. 

  [08/14/14 10:02:14 AM] Copying K1000 agent installer. 

  [08/14/14 10:02:14 AM] Running K1000 agent installer. 


    mp /Volumes/Dell_KACE dev /dev/disk1s1

    installer: Package name is AMPAgent

    installer: Installing at base path /

    installer: The install was successful.

    "disk1" unmounted.

    "disk1" ejected.


  [08/14/14 10:02:27 AM] Verifying installation. 


  STEP 3: PUSH SCRIPT\PROVISIONING - SUCCESSFUL


  [08/14/14 10:02:27 AM] K1000 agent detected via ssh query. 

  [08/14/14 10:02:27 AM] Version is 6.0.1079. 

  [08/14/14 10:02:28 AM] K1000 agent KUID: 96EB558024D946B19CF8967F23493E15 

  [08/14/14 10:02:28 AM] K1000 agent is connected via AMP. 

  [08/14/14 10:02:28 AM] End provisioning run.


  STEP 4: AMP CONNECTION - SUCCESSFUL


  STEP 5: CLIENT SYNC - WAITING...

      The provisioning process has completed.
      The K1000 is waiting for the agent to connect and sync the client.
      Please refresh this page to update the status of steps 4 and 5.

Any help is appreciated! 
10 Comments   [ + ] Show Comments

Comments

  • Can you go to Settings-> Logs tab and check "Server Errors" and "K1000 Logs" from the same time frame and describe and unusual messages there
  • I do not have a logs tab under settings or see any logs or server errors. I login to the kboxaddress/adminui web portal. Is there another way to access the logs?
  • If you have a K1200, then it must be under http://kbox/system
  • It's a K1000 but looks like I don't have system level access. I can check with the domain admins, but if the PC side is working they will be reluctant to make changes or provide the logs. Are there any other client settings I should be checking first?
  • Is there a user logged into the Mac? There's a bug with the 6.0.1079 version of the client that causes inventory to fail if there isn't a user logged into the machine.
  • Really? We are working with a Kace rep who failed to mention the bug when I brought this issue up during training. Tried provisioning by GPO, Targeted IP, and manual install from the K1000 fileshare without any users logged into a freshly imaged machine with out success. I also requested a copy of the server log from our server dept.
  • After provisioning a new test system through the K1000 admin interface, the agent installed but did not connect, even without any account logged in. After logging in as a local admin and manually downloading the ampagent-6.0.1079.osx.all.dmg file from the Kace share I finally got one to show up in inventory. Now, are both steps necessary for provisioning? Neither one alone seems to be effective.
    • Provisioning through the admin interface should be enough, assuming there is a user logged in when the inventory runs. You can check the local machine to see if the client is installed by looking in /Library/Application Support/Dell/KACE/data and looking for the AMP_CONNECTED file.
      • It's strange: The AMP_CONNECTED and AMP_SERVICE_STARTED files are both present, and the AMPAgent is running in the Activity Monitor, but the problematic systems still fail to show up in the K1000 inventory.
      • You can try forcing an inventory update on the local machine:
        sudo /Library/Application\ Support/Dell/KACE/bin/runkbot 2 0
      • Tried forcing the inventory update on 2 problematic systems. Command completed without errors and updated the inventory.xml file then uploaded it to the k1000, but systems still do not show in my org's inventory.
  • Josh, ask one of the primary KACE admins if your KBOX is using different organizations. If so, ask if what 'filtering' criteria is being used to place a client in a specific organization. For instance we have several orgs setup and filtering is based on their IP address or OU membership in Active Directory.

    FYI, I to am having issues with the 6.0 client on Mac's not checking-in/running inventory. Wondering if KACE Support has timeframe for resolution. Tired of making apologies to our Mac admins as to why our KBOX continues to fall short on the OS X side of the house.
    • Yes, we have 5-6 organizations, but I only have access to 2 of them. Filtering is based on OU/AD Membership. On the PC side it seems fine for the 10 PCs I have checked. I can relate to how your Mac admins feel! I am in the same boat.
  • If you are able to manually run a check-in on the client using 'sudo /Library/Application\ Support/Dell/KACE/bin/runkbot 1 0' with no errors, but still don't see the client show up in the org you have access to, then I would strongly suspect that the client is being filtered into another (perhaps default?) org. I'm not sure whether there is anything on the local client logs which show it's org membership.
  • All logs seem to show the clients connecting successfully. Both runkbot commands also complete successfully.
    Sys Admins finally informed me that these systems are going into our default organization which I do not have access to. They were provisioned in the same way as all other systems going into the correct orgs. This is affecting about 33% of systems I provision.
Please log in to comment

There are no answers at this time

Answers

Answer this question or Comment on this question for clarity