jamf / JamfMigrator

A tool to migrate data granularly between Jamf Pro servers
MIT License
140 stars 10 forks source link

Security & Privacy - Failed (409). Update error: unknown. #45

Closed macmule closed 4 years ago

macmule commented 4 years ago

Profiles with the Security & Privacy payload are failed to migrate with a 409 error.

20200114_101908 ----------- Starting Migration ----------- 20200114_101909 [CreateEndpoints] [osxconfigurationprofiles] Security & Privacy - Failed (409). Create error: unknown.

BIG-RAT commented 4 years ago

?Do they by chance have FileVault/Institutional Key included?


From: macmule notifications@github.com Sent: Tuesday, January 14, 2020 7:24 AM To: jamf/JamfMigrator Cc: Subscribed Subject: [jamf/JamfMigrator] Security & Privacy - Failed (409). Update error: unknown. (#45)

Profiles with the Security & Privacy payload are failed to migrate with a 409 error.

- You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/jamf/JamfMigrator/issues/45?email_source=notifications&email_token=AFJYQF7G62HWUSXSWM6XXYTQ5WVH3A5CNFSM4KGSEKY2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IGBGVVQ, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFJYQF43QAK6CODF5YACEYLQ5WVH3ANCNFSM4KGSEKYQ.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/jamf/JamfMigrator/issues/45?email_source=notifications\u0026email_token=AFJYQF7G62HWUSXSWM6XXYTQ5WVH3A5CNFSM4KGSEKY2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IGBGVVQ", "url": "https://github.com/jamf/JamfMigrator/issues/45?email_source=notifications\u0026email_token=AFJYQF7G62HWUSXSWM6XXYTQ5WVH3A5CNFSM4KGSEKY2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IGBGVVQ", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

macmule commented 4 years ago

FV2 isn't always enabled.

But escrowing to the JPS is.

BIG-RAT commented 4 years ago

Seems to be the name of the policy. If you take the ampersand out of the name does the policy migrate? Mine did. Also, I didn't have this issue with my 10.13 server so I may need to see what has changed.

BIG-RAT commented 4 years ago

Modified how the ampersand is encoded.

macmule commented 4 years ago

Looks good.. just migrated to a 10.18 from 10.19 & no issues

macmule commented 4 years ago

Ok, looks good.. but actually doesn't seem to API over all...

20200227_145035 ----------- Starting Migration -----------
20200227_145036 [CreateEndpoints] Migrating osxconfigurationprofiles
20200227_145036     [CreateEndpoints] [osxconfigurationprofiles] succeeded: Security & Privacy
20200227_145036     [CreateEndpoints] [osxconfigurationprofiles] succeeded: Security & Privacy
20200227_145036     [CreateEndpoints] [osxconfigurationprofiles] succeeded: Security & Privacy

We had 3 profiles for:

Only the "Content caching" one came over.

It appears that jamf-migrator isn't pulling over the profiles if the have the same name..

I replaced the "&" with "and" & same logs, but sane import issue:

20200227_145355 ----------- Starting Migration -----------
20200227_145356 [CreateEndpoints] Migrating osxconfigurationprofiles
20200227_145356     [CreateEndpoints] [osxconfigurationprofiles] succeeded: Security and Privacy
20200227_145356     [CreateEndpoints] [osxconfigurationprofiles] succeeded: Security and Privacy
20200227_145356     [CreateEndpoints] [osxconfigurationprofiles] succeeded: Security and Privacy

Appending the role (content, laptop, desktop) seemed to work

BIG-RAT commented 4 years ago

I expect what's happening is the profile gets overridden by the next one with the same name. Same issue occurs with policies. I'm not aware of how to create distinct items through the API that have the same name. When attempting I get the following:

Conflict

Error: Duplicate name

? cheers, leslie ________________________________ From: macmule Sent: Thursday, February 27, 2020 10:02 AM To: jamf/JamfMigrator Cc: Leslie N. Helou; Comment Subject: Re: [jamf/JamfMigrator] Security & Privacy - Failed (409). Update error: unknown. (#45) Ok, looks good.. but actually doesn't seem to API over all... 20200227_145035 ----------- Starting Migration ----------- 20200227_145036 [CreateEndpoints] Migrating osxconfigurationprofiles 20200227_145036 [CreateEndpoints] [osxconfigurationprofiles] succeeded: Security & Privacy 20200227_145036 [CreateEndpoints] [osxconfigurationprofiles] succeeded: Security & Privacy 20200227_145036 [CreateEndpoints] [osxconfigurationprofiles] succeeded: Security & Privacy We had 3 profiles for: * Content caching * Deskops * Laptops Only the "Content caching" one came over. It appears that jamf-migrator isn't pulling over the profiles if the have the same name.. I replaced the "&" with "and" & same logs, but sane import issue: 20200227_145355 ----------- Starting Migration ----------- 20200227_145356 [CreateEndpoints] Migrating osxconfigurationprofiles 20200227_145356 [CreateEndpoints] [osxconfigurationprofiles] succeeded: Security and Privacy 20200227_145356 [CreateEndpoints] [osxconfigurationprofiles] succeeded: Security and Privacy 20200227_145356 [CreateEndpoints] [osxconfigurationprofiles] succeeded: Security and Privacy Appending the role (content, laptop, desktop) seemed to work - You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe. [ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/jamf/JamfMigrator/issues/45?email_source=notifications\u0026email_token=AFJYQFZS3IEI3BWWS2BHURLRE7IW3A5CNFSM4KGSEKY2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENEVNRA#issuecomment-592008900", "url": "https://github.com/jamf/JamfMigrator/issues/45?email_source=notifications\u0026email_token=AFJYQFZS3IEI3BWWS2BHURLRE7IW3A5CNFSM4KGSEKY2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENEVNRA#issuecomment-592008900", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]