updating IP addresses in the JSS

[tlarkin]

Hello Everyone,

Due to the size of our environment we only update inventory once daily, and it is randomized. So, a machine may not update it's IP address information on the spot. This causes issues with using Casper remote. I want the client to update the IP address probably twice a day since we use layer three switches here. However, I am not seeing an option anywhere to just update the IP address in inventory.

Anyone know of some wizardry to do this?

[ernstcs]

Scope a policy with your desired interval that runs the command 'jamf log'

I think that should do the trick.

Craig E

[tlarkin]

Wow, I didn't even see that command there....

I think that is exactly what I want

thanks

[bentoms]

This is similar to a request I & others have made since v7 whereby you can run recon with switches & ONLY submit what is in the switches & not do a full recon..

This worked pre v7.. not sure if it now works in 8.

Regards,
Ben Toms
IT Support Analyst GREY Group
The Johnson Building, 77 Hatton Garden, London, EC1N 8JS
T: +44 (0) 20-3037-3819 |
Main: +44 (0) 20 3037 3000 | IT Helpdesk: +44 (0) 20 3037 3883

[John_Wetter]

Just having a scheduled task for ‘something’ at a set time and hot having a policy for it would be the same as jamf log for this. It just needs to check and it gets an IP update, it doesn’t need to do anything.

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

[tlarkin]

I got a call from jamf Support today. In Casper Version 8, anytime the
unit checks in for policy the IP address is always updated now. So
anytime it checks framework settings, checks in for policy, inventory,
etc, the IP address will be updated

[bentoms]

So, this is like 5 years later. I've moved to another company & @tlarkin is now a JAMF. :)

But I've had a few questions on this over at the #jamfnation IRC.

Does what @tlarkin say above still hold true in v9? I'm sure it does, but would like some verification. Even an RTM. :)

[tlarkin]

@bentoms

You can just run the jamf log command in terminal and it will update current user and IP address.

Cheers,
Tom

[bentoms]

Woah, rapid response thanks @tlarkin.

But, I meant more. When does it happen.

I'm sure that a clients IP updates at checkin as well as recon etc, but wanted to double check.

(Oh & there should be a cheeky Mark as answered for you in here too).

[tlarkin]

@bentoms

The beauty of tagging me in a post is that I get an email instantly and I am actually available to chat at the moment.

Every time the client checks in via the scheduled task it will update the last known IP address, and last logged in user. You can manually invoke this on demand by either running one of the two commands:

sudo jamf policy

or

sudo jamf log

Running the 'policy' command will force a check in just like whatever check in trigger you are using, just like an every hour check in. The log command just updates IP/User info. Otherwise when a device checks in, or submits inventory on its own it will also update this information.

You can test it yourself. Disable ethernet, and connect to wifi only. Then run the jamf log command and check the device record. Swap interfaces and use Ethernet and disable wifi then repeat the process. You should see the IP address change in the device record.

Does this clarify your question? Let me know if you have any more questions.

Thanks,
Tom

[bentoms]

@tlarkin perfect!

One to bookmark for when it's needed.

Thanks for the helps as always fella.