Closed macmule closed 4 years ago
Confirmed. Looks like something changed on the server side. I'm able to migrate to a Jamf Server running v10.13 but not one running v10.17. What version is running on the server you're trying to migrate to?
10.17.1, also getting a 409 on a couple of profiles.. will check them later today.
On Mon, 16 Dec 2019 at 23:02, Leslie Helou notifications@github.com wrote:
Confirmed. Looks like something changed on the server side. I'm able to migrate to a Jamf Server running v10.13 but not one running v10.17. What version is running on the server you're trying to migrate to?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jamf/JamfMigrator/issues/42?email_source=notifications&email_token=AASZZTWE4W5PH4NHHULMCATQZACGRA5CNFSM4J3RGMIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHANURA#issuecomment-566286916, or unsubscribe https://github.com/notifications/unsubscribe-auth/AASZZTWSSWBADGY55K23UVTQZACGRANCNFSM4J3RGMIA .
--
Regards,
Ben
The profiles might be something else, but just had someone mention a similar LDAP API issue with jamf 10.17.x in the jss-api slack channel
Looks like LDAP groups need to resolve the LDAP server id rather then name now (Jamf Pro v10.17) - thanks @daniel-maclaughlin for the heads up. Fix coming shortly...
Awesome.. thanks @BIG-RAT.
I would thank @daniel-maclaughlin, but.. he knows.. :P
Fix implemented in version 5.0.0. Appreciated the heads up @macmule.
Seeing a 409 error when trying to migrate LDAP servers & groups.
The LDAP server is there already, ldap.datajar.co.uk.. XML below: