Ondemand Migration for Email

Updating Outlook Profiles - OnDemand Migrator with CPUU

Summary

 When using ODME to migrate from an Exchange platform to an OnPrem Exchange or Office 365, the CPUU utility can be used to update Outlook profiles so that users can seamlessly connect to the new target mailbox without manual intervention. 

CPUU is a multi-purpose utility used with Quest Migration Manager for Exchange and ODME. Much of the feature set and documentation is tailored to Migration Manager. Note that Migration Mgr provides a full Active Directory sync, the permissions and the other features (Rules, junk mail settings etc) are not available when CPUU is used with ODME. It is important to note when CPUU is used with ODME, that ONLY the following are updated.

Supported CPUU Features

  • Switch Outlook profiles from the source to the target Exchange server (Existing Offline folders (OST files) are not preserved)
  • Update Send/Receive Setting
  • Rules (see note)

Note: In order for Rules to be updated, the add the legacyExchangeDN attribute value of the target user to the proxyAddress attribute of the source user as x500 address. This must be done manually or via script.

 

Basic steps.

  1. Designate Source & Target Mailboxes to be migrated.
  2. Download/configure CPUU https://support.quest.com/on-demand-migration-for-email/current/download-new-releases
  3. Migrate Mailbox/ Set option to Update Profile.
  4. Run CPUU on client
  5. Verify results.

 

Support Reference: https://support.quest.com/technical-documents/on-demand-migration-for-email/current/user-guide/22

Additional software: MSOnline Assistant.

http://go.microsoft.com/fwlink/?LinkID=286152

Installing and configuring CPUU

Install CPUU on a file share. Run configuration utility. Accept the defaults with the following exceptions. On the credentials tab, set the option to Prompt for credentials. i.e. during the update process, the user will be prompted for their credentials.

 

 

On the Features tab, you can, change the handling of Outlook feature to skip everything with the exception of Send/Receive Settings and Rules, as the rest are not updated with this Migration Scenario.

 

On the files tab, select the Update; Rollback; and Cleanup boxes. Complete the Wizard. Setup login script or map client to network share where CPUU is installed

 

Start the Migration

Follow existing documentation for using ODME. When ready to switch the end user, you must initiate the update from the options tab in ODME. Choosing options, be sure to set the “Enable Outlook Profile Update” on the Outlook Profile Tab.

 

 

View log, verify switch message was created.

 

 

Run the cpuu_update.bat to switch the client.

 Note that you can add this to a login script. If the switch message is not found, the utility will exit and make no modifications. The update will only occur once ODME has completed the switch operation (above).

 

 

Verify results.

Each time cpuu runs, it will create a log. Check the log for errors. Review Outlook client to verify the profile was updated to connect to the OnPrem Exchange or Office 365 mailbox.

  • Hi,
    this is clear but what is the configuration when you are migrating using the same mail domain on the source and on the target?
  • Exactly the same. There is one "Radio" button that is different in start of the CPUU configuration. Additionally "Prompt for credentials" is now the recommended method for CPUU.
  • Hi Jeff, thanks for your quick reply. I'm referring to the additional settings needed so CPUU can reconfigure the Outlook Profile. I mean the -AlwaysUseAutodiscoverFiles switch in the CPUU_Update.bat file, the AutodiscoverSrcFile and AutodiscoverTrgFile paramenters in the CPUU.ini file, etc. Also you need to create XML files for autodiscover, but all of these settings are not well documented. I'm making some tests in a Exchange 2013 to Office 365 migration scenario and i have some trouble with CPUU. Also since we're using ODME, is it possible to have the configuration working without manually converting the source mailbox to a mail user after the migration?
  • is it possible to have the configuration working without manually converting the source mailbox to a mail user after the migration? Yes

    Use the -AlwaysUseAutodiscoverFiles switch. It will forces Outlook to use the AutodiscovexxxFile.xml files instead of relying on DNS, SCP, ect. See support.quest.com/.../232266

    To create the needed AutodiscoverxxxFile.xml, see
    support.quest.com/.../232473
  • Hi Loreman,

    Thanks for posting in the On Demand Migration for Email (ODME) community forums. The following KB article provides additional details about performing an Office 365 tenant to tenant migration with ODME and using Client Profile Updating Utility (CPUU) to update end-user Outlook profiles:

    support.quest.com/.../233352