10-27-2009 04:01 PM
In case anyone else runs into this. We see this happen when users are migrated using the Enterprise Transporter in a situation where the encryption algorithms do not match. They must be exactly the same setting (i.e. 3DES and AES is not the same as AES)
If the users have already been migrated, you should be able to stop the activation by creating an activation password and having the users perform an activation. You won't need to wipe or remove the users from the new server.