Current migration uses can use conversion database version 220.127.116.11 or above to achieve these ends.
Let's say “Most” of your Exchange aliases are similar to Meeting Maker Logins, so you built the list of Exchange aliases from the MM user table. Now you have to update accounts that have a different Exchange alias:
- Add your domain name to the “customer_setup” table
- Run a query “Q_Build_CustIDs_From_MMUserids” to build the “customer_setup” table from the MM “Users” table
- Add entries to the “User_Adjusted_Maps” table to “remap” MM Logins to Exchange aliases. Please remember to include both the MM Login and UserID
- Run the query “Q_Build_CustIDs_AdjustExchangeAliases” to update the customer_setup with the correct exchange aliases
- Run the query “Q_1_Make_User_Map” to build the mm_exchange_user_map table.
We haven't tried this with Oracle Calendar Server conversions yet but the logic should work exactly the same.