Skip to main content

Hello,

I am a ServiceNow developer and working with our internal JAMF team member. We have integrated the two with the out-of-the-box connector. The data is coming into ServiceNow, but we have noticed an issue on the JAMF side.

In the User and Location area, it is not populating even though the SME says it is mapped and setup properly. It is linked to Active Directory but seems to not be populating this area though it seems to have everything that is needed.

 

Any idea what might not be setup or mapped that could explain this area not getting populated? It is impacting our Hardware and Software asset processes.

 

Any thoughts or suggestions would be appreciated.

Thanks.

You’ll want to make sure that Jamf Pro is configured to collect user information on inventory. This is done in Settings → Computer Management → Inventory Collection. You’ll also need to enable this for mobile devices in Settings → Device Management → Inventory Collection.

 

 


Additionally to what ​@stevewood said, there is (or was) an issue in Jamf Pro where this information is not filled if the user is also created as a Jamf Pro user (under “User accounts and groups” in settings).

We have to manually set the user after enrolling a device for one of our admins.


Thanks for the comments. I will check back with my contact on the internal JAMF team and have them check into these two areas. I do think I remember him showing me that the one checkbox was checked but will verify with him.


@stevewood - I checked with the contact and that value is set and still not populating.

 


Are you using an enrollment customization for enrollment?  Other wise you will need to run a script similar to: 

sudo jamf recon -endUser ldapUsername

You can even have the script run this against either the logged in user (if the shortname matches there ldap username) or against something like Jamf Connect. 


Is your jamf engineer using enrollment customizations and forcing users to authenticate before enrollment?  That will automate the process completely assuming your directory services are configured.  If not, then the engineer will need to use the command listed above osudo jamf recon -endUser ldapUsername] in a script and ping against all of the machines.  This method works well assuming the end-users are leveraging their UPN of sorts.  Could also make a variable of the username and have the recon send it too - again, assuming it’s able to be scraped from the device.

I’ve done both scenarios.  The first one (enrollment customization) is at my current org and works REALLY well.  The second scenario (script based) was at my previous org and their IdP wouldn’t allow for OIDC for enrollment customizations...but we used Jamf Connect (yes I had to write custom code for it to work properly) and it gave me their UPN to be able to send back to jamf via script to populate that data.


Reply