Skip to content

Jamf to Intune Migration Script Error When using Jamf Pro' new APIs with clients and roles #201

@jamesrodgersFL17

Description

@jamesrodgersFL17

When trying to migrate a Mac from Jamf to Intune using Jamf Pro's new API cleint and roles feature, I get a 401 error. Upon further investigation is appears the migration script usses the NEW API but with classic bearer token auth?

https://www.jamf.com/blog/understanding-jamf-pro-api-roles-and-clients/#:~:text=Jamf%20Pro%2010.49.0%20introduced%20a%20more%20secure%20method,API%3A%20Client%20Credentials-based%20authentication.%20Here%27s%20how%20it%20works.

LOG Results:

Script result: Device is managed by Jamf.
Checking if the device is ADE enrolled...
Device is ADE enrolled.
Company Portal is already installed.
swiftDialog is already installed.
jq is already installed.
User is ready to start the migration.
Serial Number: XXXXXXXXX
Auth Token: null
Computer ID: null
DEBUG: Unmanaging device with computer ID: null
DEBUG: unmanage_device response: {
"httpStatus" : 401,
"errors" : [ ]
}
Failed to unmanage device: {
"httpStatus" : 401,
"errors" : [ ]
}

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions