Closed mnestor closed 6 years ago
I agree that it would be helpful to not have migrated items apply immediately. I think it would be better though to disable the item instead of removing the scope. If the scoping is complicated I really want it to come over when I migrate the policy from stage to production so I don't have to redo it and risk doing something different from what I tested.
+1 - this breaks so many of my migrations because the scoping doesn't match "exactly". I don't need an exact match when refreshing my dev/test instance from prod.
Beta posted in releases (https://github.com/jamfprofessionalservices/JamfMigrator/releases).
When migrating specific items to another JSS it would be nice if there was an option to remove all scoping so the policy/profile/etc came into the new JSS and didn't immediately apply to systems.