Wincit
asked on
Migrating Domains from 2000 to 2003
We had 2 (two) domains, one cityhall domain and one police domain. We made a third domain call it "all" domain. We used the ADMT 3.0 to merg all users / groups and computers from police into the all domain, but when the user logs in they get a new desktop. How do we keep the same desktop / outlook pst files (we do not have exchange) my documents and printers?
The reason you get this is because the machine create a NEW profile based on the new domain. YOu need to add an extra step in moving ther information over on login via login script. This will take old profile data (EG: Desktop, PST, etc and move it under the new profile folder created.
ASKER
What would this script usually look like?
i don't see how i could do a wild card batch file to fix this.
copy c:\documents and settings\%username% c:\doucments and settings\%username%.all
that simple?
how do i make it run once?
i don't see how i could do a wild card batch file to fix this.
copy c:\documents and settings\%username% c:\doucments and settings\%username%.all
that simple?
how do i make it run once?
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
Maybe this can also help.
I did several inter-forest migration tests for my company, between two
AD 2003 domains.
I used ADMT v3.0 and it worked very well in "moving" local user
profiles.
But it didn't work the first time I used it, I had to troubleshoot a
little and understand why.
So ADMT can't really move a user's local domain profile (Documents and
Settings\%username% on XP) like you would move a file or folder in
Windows Explorer.
But what it can do is "re-use" this local profile for the new migrated
user account (all settings are retained when the user logs on with his
new account to the target domain : wallpaper, IE favorites, shortcuts,
etc...) and this is the goal.
What you need to do is :
1. Migrate the user account using the ADMT account migration wizard
2. Migrate the computer account using the ADMT computer account
migration wizard (choose to migrate all objects, files and folders,
registry, local groups and of course user profile, etc... and choose to
replace security).
There are just two things to be aware of (at least in my case, this is
why it didn't work the first time) :
- do not log on to the workstation with the new migrated user account
(target domain) BEFORE you migrate the computer account
- do not migrate the computer account while the old user account
(source domain) is logged on to the workstation
In the first case, ADMT will use the new profile in documents and
settings and you won't retain the user settings (you'll get a new
pristine user profile...).
In the second case, ADMT won't be able to use the old user account
because it's locked.
Hope this helps
I did several inter-forest migration tests for my company, between two
AD 2003 domains.
I used ADMT v3.0 and it worked very well in "moving" local user
profiles.
But it didn't work the first time I used it, I had to troubleshoot a
little and understand why.
So ADMT can't really move a user's local domain profile (Documents and
Settings\%username% on XP) like you would move a file or folder in
Windows Explorer.
But what it can do is "re-use" this local profile for the new migrated
user account (all settings are retained when the user logs on with his
new account to the target domain : wallpaper, IE favorites, shortcuts,
etc...) and this is the goal.
What you need to do is :
1. Migrate the user account using the ADMT account migration wizard
2. Migrate the computer account using the ADMT computer account
migration wizard (choose to migrate all objects, files and folders,
registry, local groups and of course user profile, etc... and choose to
replace security).
There are just two things to be aware of (at least in my case, this is
why it didn't work the first time) :
- do not log on to the workstation with the new migrated user account
(target domain) BEFORE you migrate the computer account
- do not migrate the computer account while the old user account
(source domain) is logged on to the workstation
In the first case, ADMT will use the new profile in documents and
settings and you won't retain the user settings (you'll get a new
pristine user profile...).
In the second case, ADMT won't be able to use the old user account
because it's locked.
Hope this helps
ASKER
Thanks for the quick help. I didn't want it spoon fed to me, but a quick throw together wouldn't have hurt.