MigrateToSystemWideActivation behaviour

Have a couple of questions on this new API.

• Will it retain activation metadata?
• Is it idempotent or should we write our own guard to ensure it is only run once?
• Does it move to LA_ALL_USERS on Windows?
• Does it require any administrator privileges to run?

Slightly related, is LA_ALL_USERS still only relevant on Windows?

Thanks

Hey @dzimmermann,

Thank you for reaching out.

  • Will it retain activation metadata?
    Yes, the activation metadata is retained during the migration.

  • Is it idempotent or should we write our own guard to ensure it is only run once?
    The API is idempotent and can be safely invoked multiple times.

  • Does it move to LA_ALL_USERS on Windows?
    Currently, the migration works on both macOS and Windows.

  • Does it require any administrator privileges to run?
    Admin privileges are required only when migrating from LA_SYSTEM.

  • Is LA_ALL_USERS still only relevant on Windows?
    LA_ALL_USERS is relevant for both macOS and Windows.

Please feel free to reach out to our support channel via support@cryptlex.com if you need any help.

Great, thanks @AneesKhan

1 Like

@AneesKhan A few more questions:

  • Is the method safe to call if there is no data in the old scope?
  • Is the data in the old scope removed during the migration?
  • Are trials also migrated in this fashion?

Hey @dzimmermann.

Thank you for your questions. Please find our responses below:

  • Is the method safe to call if there is no data in the old scope?
    Yes, it is safe to call the method even if there is no data in the old scope. If any activation data already exists in the new scope, the migration function will not make any changes. Additionally, if there is no data in either scope, the flag is simply switched to LA_ALL_USERS.

  • Is the data in the old scope removed during the migration?
    Yes, when the data is actually migrated from the old scope, it will be removed from the old scope afterward.

  • Are trials also migrated in this fashion?
    At the moment, migration of trial activations is not supported. However, we have noted this as feedback.