@Logan_Guard wrote:
Just noticed in Automated Device Enrollment that Asset Tag information loaded in the Placeholder is not showing up in the Device Inventory Details after enrollment. This has worked in the past but was wondering if anyone else has experienced this lately in Jamf School?
Hello,
Here's a breakdown of potential causes and troubleshooting steps, combining general Jamf knowledge with the specific context of Jamf School:
Possible Causes:
Jamf School Updates/Glitches:
Software updates can sometimes introduce unexpected bugs. It's possible a recent Jamf School update has caused this issue.
Temporary glitches or server-side issues within Jamf's services could also be at fault.
ADE PreStage Configuration Changes:
Check if any recent changes were made to the ADE PreStage configuration in Jamf School. Even seemingly minor adjustments can have unintended consequences.
Verify the asset tag field is correctly mapped and configured within the PreStage.
Data Synchronization Issues:
There might be delays or errors in the synchronization between the ADE placeholder data and the device inventory.
Network connectivity issues during enrollment could disrupt this process.
Apple School Manager (ASM) Integration:
If your ADE setup relies on ASM, ensure the data flow from ASM to Jamf School is functioning correctly. Any discrepancies in ASM could affect the data in Jamf.
Device-Specific Issues:
While less likely, there's a possibility of device-specific issues preventing the asset tag data from being recorded.
Jamf School API problems:
If Jamf school uses an API to pull that information, there could be issues with the API.
Troubleshooting Steps:
Verify PreStage Configuration:
Double-check the ADE PreStage configuration in Jamf School. Ensure the asset tag field is properly configured and mapped.
Confirm that the asset tag data is being correctly entered into the ADE placeholder.
Test with a Single Device:
Perform a test enrollment with a single device to isolate the issue. This can help determine if the problem is widespread or specific to certain devices.
Check Jamf School Logs:
Review the Jamf School logs for any errors or warnings related to ADE or device inventory.
Restart Jamf Services:
If possible, try restarting the Jamf School services to rule out any temporary glitches.
By systematically working through these troubleshooting steps, you should be able to identify the root cause of the issue and find a solution.
