CPUU enumerates users MAPI profile, however skips the processing and reports the following: Profile USER: Profile is already updated. At the same time USER profile is not updated, and the profile still points to the source Exchange server.
This problem may happen if users underwent multiple migrations and old MAPI profiles that were backed up by CPUU during processing were not removed.
The issue can be encountered in the following scenario:
First migration was recently completed: Exchange1=>Exchange2
CPUU was not run with the cleanup options and backed up profile remains in the registry.
Another migration was started: Exchange2=>Exchange3
User has a MAPI profile pointing to Exchange2 and backed up profile still pointing to Exchange1
CPUU is executed. It enumerates MAPI profile and backed up profile with the particular registry key. The profile is skipped because CPUU considers it as already updated
Profile remains pointing to Exchange2. (Expected - Exchange3)
Look for the following in CPUU log:
Enumerating backup profiles.
Backup profile User was found
CPUU finds the backup profile that was left from the previous migration and considers that it was already updated. This decision is made after looking at the particular registry key under the stored backup profile as described in solution SOL15449 - What happens if the CPUU utility is ran more than once? -https://support.quest.com/SUPPORT/index?page=solution&id=SOL15449
CPUU checks the registry for a specific key. If this key exists, then the profile has been already updated and CPUU will skip this profile. CPUU is searching for the following Registry Key:
[HKEY_CURRENT_USER\Software\Quest\CPUU \HiddenBackup\<ProfileName>]
NOTE: Typical default Profile Name in Outlook is Outlook
The value is:
CPUU profile state=hex:1e,00
Please also refer to the Updating Client Profiles document for more details:
The original profile is saved in the registry (HKEY_CURRENT_USER\Software\Aelita\CPUU \HiddenBackup) and will be used for rolling back changes if the utility fails to update the profile. If the profile is successfully updated, the backup copy will not be removed so that you can undo the profile update if needed. As soon as all profiles are successfully updated, you can remove the backup copy of the profile and all other auxiliary information saved by CPUU by running CPUU in Cleanup mode.
© ALL RIGHTS RESERVED. Feedback Nutzungsbedingungen Datenschutz Cookie Preference Center