Skip to main content

So,

I had a machine that somehow went into the void and when it came back out the tech that imaged it back from the repair shop managed to name it wrong. So, I had two computers with the same serial number and different names. Also, they would show up as two different assets in inventory searches. So I deleted the wrong one, but the real kick is, they had two different JSS IDs. Does this mean the JSS treated the same machine like two individual licensed and managed clients?

So, I assume this is not intended behavior?

Thanks,

Tom

Did it get a new logic board? The JSS tracks based on Mac Address. If they re-serialized a new logic board to the old serial number, that could look the same as what you describe.

John
--
John Wetter
Technical Services Manager
Educational Technology, Media & Information Services
Hopkins Public Schools
952-988-5373

Yep, what john said (as I was typing it myself). MAC address is different so
yes, all of the other entries would be duplicate.
--
Alan Benedict
?
Macintosh Technician
The Integer Group
O: 515-247-2738
C: 515-770-8234
http://www.integer.com

I am almost certain that is what happened. The fact that the tech
named it wrong threw the whole thing off. The machine got a logic
board replaced back in 2008 it looks like. So, I had this old dupe
entry which we thought was lost/stolen, and I only figure this out
because I just so happen to run into the user of this laptop and they
asked for my assistance.

What I don't want happening is the JSS counting the same machine twice
as a managed client and us getting charged twice for the same machine. Maybe I need to feature request, or dig into the SDK and see about
making custom reporting that will output duplicate entries of names,
serials, and so forth so you can spot check it yourself every now and
then.

Of course, we should have probably unmanaged the wrong entry since it
had been sitting in the JSS with out checking in for a year and a half. That was an oversight on our end, but I guess I never thought of it, nor
do I have time always to run such reports and do spot checks.

Terms & ConditionsCookie settingsAccessibility statement