It takes very long time to view the properties of domain pairs and other migration jobs. The console performance is very slow. This is happening only if a delegated user logs onto QMM.
Problem lies within the usage of cryptoAPI the product is using. Please refer to the resolution section for more details.
In a case where an account is given full admin role through Delegate.. menu and all consequent operations are run using this account, when working with QMM for Active Directory, CryptAcquireContext function is called several times. This API is accessing "Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA\MachineKeys\fc1e3851f429ea606d6ff1e01a5229f1_*" file.
According to http://msdn.microsoft.com/library/default.asp?url=/library/en-us/seccrypto/security/cryptacquirecontext.asp
Windows 2003:
"A key container created without this flag by an administrator can be accessed only by the user creating the key container and a user with administration privileges. A key container created without this flag by a user that is not an administrator can be accessed only by the user creating the key container and the local system account."
Windows XP:
"A key container created without this flag by an administrator can be accessed only by the user creating the key container and the local system account." This means that on Windows XP even if the account is a local administrator group, he does not have the rights on the container created by a different user (one whose account was used to install QMM and originally created the container), which causes the cryptacquirecontext function to fail with timeout and introduce the delay you are seeing.
There are two ways to work around this problem:
1. Use QMM delegated migration model fully, i.e. after assigning Full Admin role, create a delegated migration (right-click the domain pair and select "New Delegated Migration"). In this case the above function is not used and interface is operating as expected.
2. Explicitly grant the new account Full Control right on cryptoprovider file "Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA\MachineKeys\fc1e3851f429ea606d6ff1e01a5229f1_*" (random guid unique per each computer is substituted with an asterisk)
