-
Title
Executing CPUU with admin credentials -
Description
Quest has multiple KB articles where a possible usage of admins credentials within CPUU .bat is mentioned.
CPUU documentation also contains examples of the syntax for the source and target admin account, of entries which can be used within CPUU .bat.
Is it advisable to use this feature? -
Resolution
CPUU tool comes with detailed documentation and this documentation indeed has examples of "Command Line Parameters", however documentation also stresses out:
---------------------------
Entering or reviewing command line parameters is usually not necessary. The CPUU Configuration Wizard creates a batch file with the appropriate parameters for you.
You need to reference this section only in the following cases:
- You want to create the command line by yourself (though this is not recommended)...
----------------------------------
CPUU by default is being executed under currently logged in users credentials. In a regular environment user always has rights to access his own mailbox in source and in target environment so usage of admin credentials is not needed. If there are some issues and user does no have right to his mailbox then using admin credentials in the CPUU .bat is not a solution, it might help to process the profile (mailbox) but user will still not be able to use the mailbox afterwards.
A common misunderstanding is also this: when executing CPUU with admin credentials people assume it will process absolutely all Outlook profiles which can be found on the workstation. This is however incorrect.
CPUU always works in the current user's logon session. It only updates Outlook profiles that exist in the user's desktop NT profile, e.g. only for the user account that is currently logged on.
To rephrase: if one user has 5 profiles on the workstation then CPUU will process them all.
If 5 different users have their profiles on this workstation then only one profile for currently logged in user will be processed.
It is a rare scenario where usage of admin credentials in CPUU .bat is needed and can be justified, often it just causes inconvenience.
If your CPUU .bat is configured to use admin credentials and CPUU does not update the profile as expected then the next troubleshooting step would be to try and process the profile without using admin credentials in CPUU .bat.