search

jamf / JamfMigrator

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

migration is calling for it to fetch every policy #102

Open sbryant82 opened 4 months ago

sbryant82 commented 4 months ago

Using 7.4.2 Selective migration>policies when migrating a single policy, looking at the logs the app is fetching every policy in the database before it starts migrating. This is taking a long time with a current total of 184 policies in our database.

sbryant82 commented 4 months ago

image

BIG-RAT commented 4 months ago

Using migrate dependencies I trust. That can cause package lookups, and yes every package. The reason for that is the API allows you to create multiple package records in Jamf Pro (with different display names) that point to the same package file name. For example you could potentially have a listings in Jamf Pro for, say, OneDrive.pkg with a display name of OneDrive.pkg and another listing to that same package with a display name of OneDrive (no extension). Only one of those listings is valid. Like to find a better way to guard against this but haven't come up with anything yet.