So an employee got a new Macbook Air. Not being a Mac Admin, I do what I can with them. I did a backup of the computer using Time Machine and then restored the backup to the new computer. Looking back, I probably should have just resorted the user profile and not the programs.

I am now having this problem where the two MacBooks are checking into the KBOX and must have the same Agent ID, as they keep replacing each other in the Inventory. I have the computer assets set so it uses the BIOS serial number as the asset name, which is supposed to fix duplicate entries from being created, but it doesn't seem to help with this issue.

The user is keeping both Macbooks, so I can not wipe the old OS out and reload it.

Does anyone know how to completely remove the KBOX agent from a Macintosh, to the point that it creates a new entry when it is reinstalled? Or do you know how to force the agent to change it's ID so it creates a new inventory entry once it checks in?

Thanks!
Ken
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
You can remedy it with this (from http://www.kace.com/support/kb/index.php?action=artikel&cat=3&id=673&artlang=en)
to Fix and Clean it up (scenario 2)
Each entry of Mac, IP and Name above could represent many machines sharing the same KUID. If you have this problem you should:
  1. Schedule the script Reset KUID as an online script (DO NOT USE RUN NOW) to all of your affected machines.
  2. To prevent it in the future you can image your machines using this technique OR, if using the Kace 2000 Appliance then install the agent via a post-install task. In both cases, make sure the agent does not connect to the network until it has it's new host name.
Answered 10/13/2011 by: GillySpy
Seventh Degree Black Belt

Please log in to comment
0
Thanks, I will give those a try!
-Ken
Answered 10/13/2011 by: KboxKen
Orange Belt

Please log in to comment
0
Gilly,

Reading though scenario 2, it is describing precisely what I am seeing. I think I scheduled the script correctly, but how long until the issue fixes itself? I figure I am just being impaitant, but the computer has already checked in. Also, this script appears to be designed for Windows computers, will it work on a Macintosh? I did change the Supported OS on the script to Mac.

Thanks,
Ken
Answered 10/13/2011 by: KboxKen
Orange Belt

Please log in to comment
0
Update: I built the SQL report using the query mentioned on that page and it appears that I may have more then one machine doing this, which I did not realize. So I have changed the script settings to "Deploy to All Machines", set it so it deploys to all operating systems, and set it to run every 15 minutes... which is my check in rate. From there I hit "Save" as your instructions specifically say to not use "Run Now".

Thanks,
Ken
Answered 10/13/2011 by: KboxKen
Orange Belt

Please log in to comment
0
Finally remembered where to check script status on a machine (Inventory, select computer, Scripting Logs). When I checked the entry for the Macintosh in question, I found this. Also, I checked one that is reporting in correctly, and saw the same messages in it's log.

Started: Oct 13 2011 11:45:14 AM
Finished: Oct 13 2011 11:45:14 AM
Elapsed Time: 0 second
Status: 4
Status Log ResetKUIDRunOnce already exists. Exiting. [hr] Started: Oct 13 2011 11:20:44 AM
Finished: Oct 13 2011 11:20:44 AM
Elapsed Time: 0 second
Status: 3
Output Log Skipping 'Reset KUID' because not allowed to execute logged off

I realized that "Logged off" means the user was logged off... Going to make sure the second computer has the agent installed and is up to date.
Answered 10/13/2011 by: KboxKen
Orange Belt

Please log in to comment
0
Update:

The MacBooks were still acting up and not checking in properly, so I left that "reset KUID" script running every 15m on a schedule and forgot about it for the last two weeks. I finally got back to my inventory list and noticed that they are both checked in now as separate entries. Since the "Finding Duplicate computer" report that I built is not showing any other issues, I am going to turn off the script and keep an eye on them as I remember.

Thanks for the pointers Gilly.
Ken
Answered 10/26/2011 by: KboxKen
Orange Belt

Please log in to comment
0
Hey , i was fortunate enough to land in this forum. I had the same problem with Macintosh & i've given a shot at what you wrote here. Thanks & more power to you guys!
Answered 10/29/2011 by: pattyfoz
Yellow Belt

Please log in to comment
0
Hey pattyfoz, very happy to hear that it worked for you. I figured someone else out there had the same problem, so I was pretty surprised to be the first one asking about it.
Answered 10/31/2011 by: KboxKen
Orange Belt

Please log in to comment
Answer this question or Comment on this question for clarity