When running CPUU across a slow connection, the tool either does not complete or takes a long time (20390)

When running CPUU across a WAN/Dialup/VPN connection of limited speed, the utility seems to hang or takes a very long time to process a user.

On a slow connection this is normal. CPUU makes many calls/connections to the source and target environment in its normal processing. These calls can take considerable time.

During the processing of Outlook profiles, the CPUU utility calls both source and target and depending upon the profile being processed the network demand can be quite substantial. If the users profile should be updated using a slow connection, CPUU performance may appear to be slow. Thus, it may take several hours to update a profile.

Below are some points to consider:

1. The following functionalities take the most time to be updated using a slow connection:

Nicknames (AutoNameCheck)
Read/Unread message status
Junk e-mail senders list and Adult content senders list

When using CPUU with Exchange Migration Wizard, just select the corresponding option in the Configuration Wizard. If you are to update a profile for a mailbox migrated by Exchange Migration Wizard, you can force CPUU skip the above functionalities from processing and remove all nicknames from the profile by including the following string in the command line:

-Skip JunkSenders AdultSenders ReadStatus -Remove Nicks

For more information please refer tothe following KB article:
Updating Outlook profiles over the slow WAN or dial-up connections
https://support.quest.com/kb/8961

2. It is also advisable to use a cache file for processing as well. This will reduce the calls the utility must make to the Global Catalog servers. More information on this can be found within the Updating Client Profile.pdf attached.

3. Configure CPUU with the basic logging when using in production. Extended logging is for troubleshooting only.

4. Configure CPUU to write the log file to the local workstation rather than to the network share. Depending on the connection writing (placing) the log file to the network share can significantly slow down the processing time.