Primary identifier for Machines- is this changeable?

[powellbc]

It seems the IP address is the primary identifier for machines. If a machine changes IP we cannot remote into it until the inventory is updated, which is once a week (by default, of course).

Is there a way to change this primary identifier, and if so will it help with the issue of being able to remote into a machine with a new IP? Or is the only solution to increase the inventory collection period?

[rderewianko · Accepted solution]

The primary Identifier is actually the mac address. Comming in V9 it'll be switched to UDID
https://jamfnation.jamfsoftware.com/featureRequest.html?id=366

The best bet would be to change the checkin frequency. Currently We have ours set as daily. Due to IP addresses constantly changing. By default whenever you build a policy out it also checks the box "update inventory" so any policy run on a machine also updates the IP.

[bentoms]

IIRC, every time a Mac contacts the JSS it's IP is updated.

So if you have the every15 scheduled task still, the macs ip should update every 15 minutes. (Give or take the randomisation).

Also, I'd check in the JSS to verify this. As if an IP has updated whilst Casper Remote has been updated you need to click "Refresh" to get the updated details.

[mm2270]

Yes, the check in time is what updates the Mac's IP address, not the inventory date. In fact doing a simple sudo jamf log will update the IP address in the Mac's record as well. Only the rest of the data is reliant on a full recon happening to be updated.

[powellbc]

Thanks everyone for the great info.

[Chris_Hafner]

It is important to point out that this is where one of JAMF's favorite "AND" sayings goes. It's all about Casper 'AND' ARD. While casper remote is a great utility, it's hard to deal with direct support for units that are mobile or otherwise change IP's regularly as you know. While the JSS has to wait (one of Caspers biggest benefits in my book) for a unit to contact it, ARD works the other way around. Give it a shot for remote support.

[acdesigntech]

I've not seen the Macs IP get updated in Casper when it checks in. To this end, I've created a LaunchDaemon that watches the network connection on laptops and submits updated inventory when it sees the active network port change. It disables wireless when it detects en0 has become active, and vice versa.

It's worked out well so far.

[mm2270]

@acdesigntech, sorry, but then something is wrong with your setup, because that's how its supposed to work.

I just verified this a moment ago before posting, just so I wouldn't be talking out of my rear. :)
My Mac had checked in at 6:44 PM, had an IP from our Ethernet network. The time on my clock was 6:47, so well before its next automatic every15 check in. I disconnected from Ethernet and connected to the company Wi-Fi, then ran a 'sudo jamf log'. Went back and refreshed the page in the JSS for my Mac and it listed Last Contact Time as 6:47 and its new wireless IP address. I did not submit full inventory, just a log function.

I then switched back to Ethernet (we also have a LaunchDaemon that disables wireless if it detects an Ethernet connection) It switched over, I ran a quick 'sudo jamf policy -trigger every15' (no actual policies ran) to try that out, and went back to the JSS. IP address changed for my Mac back to the internal one as well as the Check in time of course.

Keep in mind this was a matter of seconds from switching network connections, and doing the check in and updated IP. Not even enough time for a normal recon to happen. It definitely updated without a full inventory report. In fact, Last Report Date is still listed as happening at 11;50 AM today.

If you're not seeing that, well, you might want to have a talk with JAMF support. They designed it to work that way so they'd be interested in making sure it works for you.

[acdesigntech]

i'll have to check again, maybe it is actually working that way. IDK. Too many things going on at once, and vacation looming over all :D

Hopefully I'll have a bit more time this year to get these types of things in order. Our team is being promised that we'll be doing fewer projects and more getting our environment stable...

Thanks for the help, Mike.

[Chris_Hafner]

Just to clarify: The unit still needs to contact the JSS as per it's checkin interval before the IP info get's updated. It just dosen't need to run any policy or inventory.

[acdesigntech]

You guys are right. I was able to verify that this morning :)