#Jamf pro ldap serial number

Want to move a batch of devices to another room? Easy, just create a CSV with their serial number and add the information you want to change. Especially as it gives us the ability to make bulk changes to existing devices, too. With this data available, we can now make use of some Smart Groups that are based on Rooms to deploy different applications, printers, or other settings as part of the whole onboarding process.Īs I said, it's not very fun, but I love it. For a full list of default values, take a look at the documentation, but extension attributes are fully useable by prefixing the column with EA and then the name. If you don't use asset tags, you can leave that out, but you can instantly see how powerful this simple tool can be. Once this is assigned, it will also automatically update our Smart Groups. We're now telling Jamf, as soon as you see that serial number, I want you to assign the Asset Tag, Room, and (Extension Attribute) Usage Type to that device. Instead, we'll make use of Inventory Preload by creating a CSV file with the following information: Serial Number That would also completely break our fully automated workflow! If we had a new order of 100 devices coming in, destined for 3 different rooms, would you want to manually assign that room information AFTER enrolment along with the usage type? Of course not. For my environment, I make heavy usage of the Room, and custom Usage Type attributes. We want to automate things as much as possible! So, that's what we're going to do.

Building up different onboarding workflows for all of these would be a nightmare.

When deploying lab style environments, you're very likely deploying to different rooms, buildings, or clusters that require different things. But, quite simply, it allows us to pre-populate Jamf with information about a device before it's enrolled (and after, too!).