Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Computer Records Not Updating #111

Open
coeserver opened this issue Dec 3, 2024 · 2 comments
Open

Computer Records Not Updating #111

coeserver opened this issue Dec 3, 2024 · 2 comments

Comments

@coeserver
Copy link

Working with JAMF support, we migrated computers from source to destination. The first time we ran the process, it did not put the computers in the site that we wanted to import into. Ran again hoping it would update the computer records - it updated half of them and began throwing error in the log..

20241203_153119 [CreateEndpoints] [computers] update succeeded: NAME-LR 20241203_153121 [CreateEndpoints] [computers] update succeeded: NAME-LD 20241203_153123 [CreateEndpoints] [computers] update succeeded: NAME-ADL 20241203_153126 [CreateEndpoints] [computers] update succeeded: NAME-ML04 20241203_153127 [CreateEndpoints] [computers] retrying: NAME-GS01 20241203_153127 [CreateEndpoints] [computers] retrying: NAME-GS01 20241203_153128 [CreateEndpoints] [computers] retrying: NAME-GS01 20241203_153128 [CreateEndpoints] [computers] retrying: NAME-MAH 20241203_153128 [CreateEndpoints] [computers] retrying: NAME-GS01 20241203_153128 [CreateEndpoints] [computers] retrying: NAME-MAH 20241203_153129 [CreateEndpoints] [computers] migration of id:204 failed, retry count exceeded. 20241203_153129 [CreateEndpoints] [computers] NAME-GS01 - Failed (409). Update error: Duplicate UDID.

This is the point in the log where the errors started showing. I partially redacted the device name in this snippet. JAMF support is currently investigating the possibility of an API issue, but they suggested I create an issue here.

@BIG-RAT
Copy link
Contributor

BIG-RAT commented Dec 4, 2024

Hoping to get some additional details on the process.
Are computers assigned to a site on the source server and you're migrating to the destination, with no site selected or a site selected.
or
Computers are not in a site on the source and you're migrating to a particular site on the destination.

Account on the destination server is a full admin (can access all sites) and is not logged into a site. It's been a while but I used to have issues with jamf-migrator (now Replicator) if the account used with migrator was logged into a site with a web browser.

@coeserver
Copy link
Author

We're using the API client on both ends. Computers on the source are not assigned to a site, but I'm importing them into a site on the Destination.

I ran the process again, and it did update all the records when I just migrated Computers. I am having a similar issue with Mobile Devices now though, that aren't getting migrated at all after 3 attempts.

I have been logged into both web interfaces at the time of migration though, I'll try to do Mobile Devices again while being logged out - I don't know if this is an API issue or a replicator issue at this point.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants