V24.3 - User Alias Upgrade

Overview

For existing deployments that:

• Have standalone group aliases enabled.
• Have a configuration where MCE groups are enabled. (MCE Standalone, MCE and SfB hybrid environments) To maintain the current aliases set by users in MCE groups.

Verifying that the migration prerequisites have been met

To verify if your current deployment meets the requirements run the following in a connected MCE Powershell session:

Get-MceMigrations | Where-Object MigrationId -eq 1 | Select-Object MigrationId -ExpandProperty Prerequisites

This will return a description of the prerequisites for a given migration, as well as whether they have been met.

Performing the migration

1. Configure MCE to enable aliases for:

• SfB Aliases, if SfB is configured.
• MCE Aliases, if MCE is configured.
• See documentation for details Group aliases configuration

2. Start service and execute migration commandlet.

To execute the migration the following must be run in a connected MCE Powershell session:

Start-MceMigration -Id 1

Performing the migration will do the following:

• The latest aliases for each user in all pre-existing MCE groups before the upgrade will be migrated.
• Disabled MCE groups will not have aliases migrated.
• Any user that has set an alias after the upgrade, in a pre-existing MCE group, before the migration will not have their aliases overwritten.
  • In addition, any legacy aliases that match a newly set alias for another group participant will not be migrated.
• Aliases will not be migrated for users that no longer have access rights to a pre-existing MCE group.
  • Aliases for disabled MCE users will not be migrated.
  • Aliases for suspended users will be migrated.