I need to remove my xp client workstations from one windows server 2003
active-directory domain and add them to a different one. Is there a way to
migrate the user profiles (so that the icons stay the same)?
Printable View
I need to remove my xp client workstations from one windows server 2003
active-directory domain and add them to a different one. Is there a way to
migrate the user profiles (so that the icons stay the same)?
Dear Customer,
Thank you for posting here.
According to description, you wonder if there is a way to migrate the user
profiles between domains. If I have any misunderstanding, please feel free
to let me know.
Based on the research, 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
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
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
Thanks David, however I am not actually migrating any one to the new domain.
We are actually just setting up a new domain and creating new users from
scratch. I just wanted to know if I would be able to copy the user profile
over from the old user to the new user. We're not using ADMT or anything to
actually migrate users from domain1 to domain2.
Thanks for your help.
TJ
"David Shen [MSFT]" wrote:
> Dear Customer,
>
> Thank you for posting here.
>
> According to description, you wonder if there is a way to migrate the user
> profiles between domains. If I have any misunderstanding, please feel free
> to let me know.
>
> Based on the research, 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
>
> 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
>
> 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
>
>
Local user profiles can be copied as easy as any folder.
1.create new user in new domain
2.log on with new user cred. and than log off on workstation
3. log on as admin and copy old user profile over the new user profile
folders
Tim wrote:
> Thanks David, however I am not actually migrating any one to the new domain.
> We are actually just setting up a new domain and creating new users from
> scratch. I just wanted to know if I would be able to copy the user profile
> over from the old user to the new user. We're not using ADMT or anything to
> actually migrate users from domain1 to domain2.
>
> Thanks for your help.
> TJ
>
>
> "David Shen [MSFT]" wrote:
>
>> Dear Customer,
>>
>> Thank you for posting here.
>>
>> According to description, you wonder if there is a way to migrate the user
>> profiles between domains. If I have any misunderstanding, please feel free
>> to let me know.
>>
>> Based on the research, 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
>>
>> 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
>>
>> 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
>>
>>
Hello TJ,
Thanks for your reply and sorry for my misunderstanding.
According to your description, my understanding of the scenario is:
You have one client computer (computerA), and it is now in domainA. An user
named user1 (domainA\user1) use this computer. Currently, you want to
remove this computer from domainA and want to join it to another domain
(domain). However, you want the user use account (domainB\user1) to log on
to the computer in the new domain with existing user profile. You don't
want to use ADMT to perform this migration.
If I have any misunderstanding, please let me know.
Based on the research, this can be achieved by using USMT. You may follow
the steps:
1.Log on to the computerA with an administrative account (Administrator) in
domainA. Then run the following command:
scanstate \\fileserver\migration\mystore /ue:*\* /ui:domainA\user1
/i:miguser.xml /i:migapp.xml /o
2.Remove the computerA from domainA.
3.After creating a new user "user1" in domainB and joining computerA to
domainB, you should log onto computerA with an administrative account
(Administrator) in domainB.
4.Run the following command on computerA:
loadstate \\fileserver\migration\mystore /mu:domainA\user1:domainB\user1
/i:miguser.xml /i:migapp.xml
5.Log on to computerA with the new user account (e.g. domainB\user1), see
it the user profile has been migrated successfully.
With this method, you don't need to create trust between domainA and
domainB. However, you need to create a new user domainB\user1 for
domainA\user1.
Please note: we need to install the User State Migration Tool on the
computer.
For your convenience , I have list the download link for you.
Windows User State Migration Tool (USMT) Version 3.0.1:
http://www.microsoft.com/downloads/d...28c-691b-4b36-
b7ad-6c604be4c595&displaylang=en
Hope it helps.
David Shen
Microsoft Online Partner Support
Hello TJ,
How's everything going?
I'm wondering if the suggestion 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
Thanks a bunch David, this is good information. I will let you know if this
does not work. I will be testing the next few days.
Many thanks!
TJ
"David Shen [MSFT]" wrote:
> Hello TJ,
>
> Thanks for your reply and sorry for my misunderstanding.
>
> According to your description, my understanding of the scenario is:
>
> You have one client computer (computerA), and it is now in domainA. An user
> named user1 (domainA\user1) use this computer. Currently, you want to
> remove this computer from domainA and want to join it to another domain
> (domain). However, you want the user use account (domainB\user1) to log on
> to the computer in the new domain with existing user profile. You don't
> want to use ADMT to perform this migration.
>
> If I have any misunderstanding, please let me know.
>
> Based on the research, this can be achieved by using USMT. You may follow
> the steps:
>
> 1.Log on to the computerA with an administrative account (Administrator) in
> domainA. Then run the following command:
>
> scanstate \\fileserver\migration\mystore /ue:*\* /ui:domainA\user1
> /i:miguser.xml /i:migapp.xml /o
>
> 2.Remove the computerA from domainA.
>
> 3.After creating a new user "user1" in domainB and joining computerA to
> domainB, you should log onto computerA with an administrative account
> (Administrator) in domainB.
>
> 4.Run the following command on computerA:
>
> loadstate \\fileserver\migration\mystore /mu:domainA\user1:domainB\user1
> /i:miguser.xml /i:migapp.xml
>
> 5.Log on to computerA with the new user account (e.g. domainB\user1), see
> it the user profile has been migrated successfully.
>
> With this method, you don't need to create trust between domainA and
> domainB. However, you need to create a new user domainB\user1 for
> domainA\user1.
>
> Please note: we need to install the User State Migration Tool on the
> computer.
>
> For your convenience , I have list the download link for you.
>
> Windows User State Migration Tool (USMT) Version 3.0.1:
> http://www.microsoft.com/downloads/d...28c-691b-4b36-
> b7ad-6c604be4c595&displaylang=en
>
> Hope it helps.
>
> David Shen
> Microsoft Online Partner Support
>
>
Thanks a bunch David, this is good information. I will let you know if this
does not work. I will be testing the next few days.
Many thanks!
TJ
"David Shen [MSFT]" wrote:
> Hello TJ,
>
> Thanks for your reply and sorry for my misunderstanding.
>
> According to your description, my understanding of the scenario is:
>
> You have one client computer (computerA), and it is now in domainA. An user
> named user1 (domainA\user1) use this computer. Currently, you want to
> remove this computer from domainA and want to join it to another domain
> (domain). However, you want the user use account (domainB\user1) to log on
> to the computer in the new domain with existing user profile. You don't
> want to use ADMT to perform this migration.
>
> If I have any misunderstanding, please let me know.
>
> Based on the research, this can be achieved by using USMT. You may follow
> the steps:
>
> 1.Log on to the computerA with an administrative account (Administrator) in
> domainA. Then run the following command:
>
> scanstate \\fileserver\migration\mystore /ue:*\* /ui:domainA\user1
> /i:miguser.xml /i:migapp.xml /o
>
> 2.Remove the computerA from domainA.
>
> 3.After creating a new user "user1" in domainB and joining computerA to
> domainB, you should log onto computerA with an administrative account
> (Administrator) in domainB.
>
> 4.Run the following command on computerA:
>
> loadstate \\fileserver\migration\mystore /mu:domainA\user1:domainB\user1
> /i:miguser.xml /i:migapp.xml
>
> 5.Log on to computerA with the new user account (e.g. domainB\user1), see
> it the user profile has been migrated successfully.
>
> With this method, you don't need to create trust between domainA and
> domainB. However, you need to create a new user domainB\user1 for
> domainA\user1.
>
> Please note: we need to install the User State Migration Tool on the
> computer.
>
> For your convenience , I have list the download link for you.
>
> Windows User State Migration Tool (USMT) Version 3.0.1:
> http://www.microsoft.com/downloads/d...28c-691b-4b36-
> b7ad-6c604be4c595&displaylang=en
>
> Hope it helps.
>
> David Shen
> Microsoft Online Partner Support
>
>
Hello,
I have a similar case as Tim as, but we only need to migrate the workstation from domainA to domainB.
I want my user to keep their local profile on their machine and we won't build newer workstation for them.
We already have migrate all domainA users to domainB. We now only need to migrate the workstations. I already have looked at the tools proposed above, but ADMT isn't an option for us, since we don't have admin accounts on both domain controler. UMT isn't really an option either since it copies the profile to a file server then back to the workstation. We have users over WAN with a slow connection.
What we are looking for, is a tool that can migrate users from domainA to domainB while keeping their own local profile. A batch tool that does that without going through every workstations would be great since we have over 800 workstations to migrate.
Hi customer,
It seems there are multiple issues posted in this thread. Generally, we
request one question per post in the newsgroups. In order to concentrate
fully on each of these issues and provide clarity for others that may be
following here, it is recommanded that you post them as separate threads.
This will also make the thread more clear and consistent for your
reference. Please feel free to open different posts for these questions.
We will be very glad to work with you.
Thank you for your patience and understanding.
David Shen
Microsoft Online Technical Support
I understand that this post was quite some time ago.
If possible, I was wondering if the method above using the USMT application would work in a similar scenario.
Everything is the same accept I am migrating domainA/user1 to domainB/0001
will it still work? or does it have to be from domainA/user1 to domainB/user1 ?
Thanks
You can do it as follows:
1. Log on to the computerA with an administrative account (Administrator) in domainA. Then run the following command:
scanstate \\fileserver\migration\mystore /ue:*\* /ui:domainA\user1 /i:miguser.xml /i:migapp.xml /o
2. Remove the computerA from domainA.
3. After creating a new user "user1" in domainB and joining computerA to domainB, you should log onto computerA with an administrative account (Administrator) in domainB.
4. Run the following command on computerA:
loadstate \\fileserver\migration\mystore /mu:domainA\user1:domainB\user1 /i:miguser.xml /i:migapp.xml
5. Log on to computerA with the new user account (e.g. domainB\user1), see it the user profile has been migrated successfully.
With this method, you don't need to create trust between domainA and domainB. However, you need to create a new user domainB\user1 for domainA\user1.