Migrate user profiles

Hi,

I have 50 computers (Windows XP SP2) in my "old" domain (Windows
2003).
I need to "migrate" to the new domain (Windows 2003) the computer
accounts but want to migrate the user profile too.

Any ideas?


Thanks,
JTMELO

Dear Customer,

Thank you for using newsgroup.

According to the description, you wish is to migrate the user profile from
"old" domain to "new" domain. If I have some misunderstanding, pleas feel
free to let me know.

According to the description, here is some information which may be helpful
for you.

Analysis and Suggestion:
=====================

We can simply use ADMT to migrate local user profiles for all the
workstations from "old" domain to "new" domain. We don't have to copy all
the local user profiles from the old profile to the new profile. We may
simply migrate the user profiles with Security Translation Wizard in the
ADMT. We may translate the local user profiles to let all the computer be
aware of the migration. It is important to verify that user profile
translation succeeded for each user before that user is allowed to log on.
We can also migrate roaming user profiles during the user account migration
process. However, we still need to translate the local user profile.

When we migrate the user profiles, the Security Translation wizard will
move the user profiles from the source domain to the target domain. And
after the user accounts have been migrated, the ADMT will preserve the SID
history of the source domain. We can still use the migrated domain accounts
in the target domain to use the previous user profile. Even if you logon
the new domain with UPN, it will still use the previous user profile and
the folder name of the profile won't be changed.

For more detailed information, please refer to:

Translating Local User Profiles
http://technet2.microsoft.com/window...7-d959-4b00-af
f4-19b575ba28561033.mspx?mfr=true

After migrating the computer accounts from the "old" domain to the "new"
domain, the computer accounts that exist in new domain will be aware of the
migration. You may logon the new domain when the clients boot up without
removing the computer from the old domain. All the clients will be aware of
the migration of the domain.

For more information about ADMT, please refer to:

ADMT v3 Migration Guide
http://www.microsoft.com/downloads/d...770-3BBB-4B9E-
A8BC-01E9F7EF7342&displaylang=en

Support WebCast: Domain Migration Using the Microsoft Active Directory
Migration Tool
http://support.microsoft.com/kb/325393

Hope it helps.

Thanks for your time.

David Shen
Microsoft Online Partner Support

On 26 Maio, 07:44, v-das...@online.microsoft.com (David Shen [MSFT])
wrote:
> Dear Customer,
>
> Thank you for using newsgroup.
>
> According to the description, you wish is to migrate the user profile from
> "old" domain to "new" domain. If I have some misunderstanding, pleas feel
> free to let me know.
>
> According to the description, here is some information which may be helpful
> for you.
>
> Analysis and Suggestion:
> =====================
>
> We can simply use ADMT to migrate local user profiles for all the
> workstations from "old" domain to "new" domain. We don't have to copy all
> the local user profiles from the old profile to the new profile. We may
> simply migrate the user profiles with Security Translation Wizard in the
> ADMT. We may translate the local user profiles to let all the computer be
> aware of the migration. It is important to verify that user profile
> translation succeeded for each user before that user is allowed to log on.
> We can also migrate roaming user profiles during the user account migration
> process. However, we still need to translate the local user profile.
>
> When we migrate the user profiles, the Security Translation wizard will
> move the user profiles from the source domain to the target domain. And
> after the user accounts have been migrated, the ADMT will preserve the SID
> history of the source domain. We can still use the migrated domain accounts
> in the target domain to use the previous user profile. Even if you logon
> the new domain with UPN, it will still use the previous user profile and
> the folder name of the profile won't be changed.
>
> For more detailed information, please refer to:
>
> Translating Local User Profileshttp://technet2.microsoft.com/windowsserver/en/library/e9197ee7-d959-...
> f4-19b575ba28561033.mspx?mfr=true
>
> After migrating the computer accounts from the "old" domain to the "new"
> domain, the computer accounts that exist in new domain will be aware of the
> migration. You may logon the new domain when the clients boot up without
> removing the computer from the old domain. All the clients will be aware of
> the migration of the domain.
>
> For more information about ADMT, please refer to:
>
> ADMT v3 Migration Guidehttp://www.microsoft.com/downloads/details.aspx?familyid=D99EF770-3BB...
> A8BC-01E9F7EF7342&displaylang=en
>
> Support WebCast: Domain Migration Using the Microsoft Active Directory
> Migration Toolhttp://support.microsoft.com/kb/325393
>
> Hope it helps.
>
> Thanks for your time.
>
> David Shen
> Microsoft Online Partner Support

Hi,

Thanks for your help, but i have one "big problem".
In my new domain, i "create" the user accounts, i dont "migrate" them.
Now, how can i associate the old user accounts with the new user
accounts?


TM

Dear Customer,

Thanks for the reply.

According to the further question, here is some information which may be
helpful for you.

You may create a SID mapping file to complete the task of user account
migration. The Security Translation's working refers to the mapping file,
which includes the old user accounts, SIDs and the corresponding new user
accounts SIDs. When it running, it will scan the files and folders residing
on the target computer to search if there is matched entries, according to
this mapping file. If it finds such an entry, it will "replace" the new
entry with old entry, or "add" new entry with old entry or remove the old
entry, which we can choose in its options.

As for the mapping file, it can be written manually or generated by ADMT.
If you want to generate this mapping file, you have to migrate the
corresponding user accounts ahead of Security Translation. It may not fit
for this scenario and increase complexity. If you have already obtained the
old and new SIDs. I would like to suggest that you create this mapping
files manually.

If you perform security translation in "add" mode, the SIDs in the target
and the source domains both have access to the profile. Therefore, if you
need to roll back to the source environment, the SID in the source domain
can use the profile. If you perform security translation in "replace" mode,
you need to retranslate the profile by using a SID mapping file (undoing
the security translation) to roll back to the source environment.

For more about SIDs mapping file, please refer to:

How to use a SID mapping file with the ADMT tool to perform a resource
domain migration to Windows Server 2003
http://support.microsoft.com/default...b;EN-US;835991

Hope it helps.

David Shen
Microsoft Online Partner Support

Dear Customer,

How's everything going?

I'm wondering if the information has helped or if you have any further
questions. Please feel free to respond to the newsgroups if I can assist
further.

David Shen
Microsoft Online Partner Support