AD Fields to take note of: Note: An account can't be locked out. Leaving it checked ensures it will be left in, or change to an enabled state. But even after several user profile imports, the old user name: EU\susanapi was still showing up in Share Point, and Share Point treated the new user account as a separate account. Unfortunately, Sharepoint doesn't understand this change automatically.
Using a single repository for configuration settings seems to make sense, apart that is from server-specific information such as the watermark used to capture the state of installations.
The property name entered must be a valid schema property.
Note: The Add button will appear when Other is selected.
I had to do the same thing When users left the company, their accounts are deleted in AD (But their profiles are not deleted in Share Point). New AD-Account created and I just used the "Migrate User" command to associate the new account with their existing user profile.
By this, All their profile Data, Security Settings, Tasks assigned and My Site are associated back with the users.