IPv4 addresses in conditional_item comparisons
Greg Neagle
Greg Neagle
Per Olofsson
"IP Address added as a conditional_items attribute" is rather vague. That said, an array of IPv4 addresses should work fine for solving some problems on some networks (e.g. install a package to machines on a certain range of public IPs that don't move to other networks a lot). If you have to deal with laptops on private IP addresses that visit NAT:ed home routers things turn ugly real quick. In MunkiReport there's a /lookup/ip method to help with connectivity checks for Munki runs.
I recently had to solve the problem of "Only start backups when machines are on the university network, but not on wireless or over VPN", which required inspecting which interface is active for routing traffic to our backup server.
It all comes down to what you're trying to solve. That said, I'm all for adding more conditional_items, the more the better. We're making extensive use of smart groups in Absolute Manage, which is basically the same thing, where clients' OU and AD group membership control software distribution.
--
Per Olofsson, IT-service, University of Gothenburg
Greg Neagle
I had planned on eventually extending the mechanism so that administrators could define additional arbitrary attributes (and maybe even override existing attributes), but I was recently contacted by a list participant who is working on this very thing, so I'll wait and see what he's come up with...
-Greg
Matt J
expected. Thank you!
Matt Johnson
Seattle Public Schools
Joe Wollard
--
Joe Wollard
--