Migrating users to domain and retaining existing profiles

[Homerboy]

I have ~95 PCs/Users that I am migrating from Netware to a Win2k3 DC.
Is there any (easy) way to maintain the existing users profiles on their PCs when they migrate? Once they join the domain, its a new local user profile and I simply can't have that.... way to many settings for programs, and personal options to tend with.

Ideas? Suggestions?

 

[redbeard1]

There is a couple of options.

For the XP Pro systems, the File and Settings Transfer Wizard works reasonably well. You run this and save the file it creates somewhere on the computer that you are migrating that particular user. Then join the computer to the domain, and log in as that user. As that user run the Wizard again and point it to the file you created. To help speed the process, before you run the Wizard, clear the temporary internet cache and the temp folder, as these get brought over in the Wizard, and if they are left there, they add a huge amount of time to the process. It is also advisable to check their desktop to see if they are storing pictures and music there. Having large files in that location also adds a lot of time to the process. The main issue I have with this Wizard, is that it will not import the PST from Outlook 2003 or 2007, so this has to be manually exported beforehand. Normally I make a folder on the C: drive named Migrate and put everything there. If the system has multiple users, I then create a folder with their names in the migrate folder. If there are network printers, the Wizard will generally bring them over. If they had mapped networked drives previously, the wizard will try and bring them over, so sometimes this can conflict with any new mapped drives using the same drive letter.

This link describes another way of migrating things, though it is not how they intended it. If you join the computer to the domain, log in as the user once on the domain, then log in as someone else, usually the administrator, with view all files and hidden system folders on, go to Documents and Settings and find the original user profile. Copy all but three files from the old profile over the top of the new profile. The three files you do not want are explained in the article. Again, to speed the process, delete the various temporary files. This should work for Win2k as well. The problem with this is that you definately have to export and import the email, whether Outlook or Outlook Express. If it is Outlook Express you also need to export and import their Address Book as well. This does not bring the printers over.

MS

 

[Homerboy]

Originally posted by: redbeard1
There is a couple of options.

For the XP Pro systems, the File and Settings Transfer Wizard works reasonably well. You run this and save the file it creates somewhere on the computer that you are migrating that particular user. Then join the computer to the domain, and log in as that user. As that user run the Wizard again and point it to the file you created. To help speed the process, before you run the Wizard, clear the temporary internet cache and the temp folder, as these get brought over in the Wizard, and if they are left there, they add a huge amount of time to the process. It is also advisable to check their desktop to see if they are storing pictures and music there. Having large files in that location also adds a lot of time to the process. The main issue I have with this Wizard, is that it will not import the PST from Outlook 2003 or 2007, so this has to be manually exported beforehand. Normally I make a folder on the C: drive named Migrate and put everything there. If the system has multiple users, I then create a folder with their names in the migrate folder. If there are network printers, the Wizard will generally bring them over. If they had mapped networked drives previously, the wizard will try and bring them over, so sometimes this can conflict with any new mapped drives using the same drive letter.

This link describes another way of migrating things, though it is not how they intended it. If you join the computer to the domain, log in as the user once on the domain, then log in as someone else, usually the administrator, with view all files and hidden system folders on, go to Documents and Settings and find the original user profile. Copy all but three files from the old profile over the top of the new profile. The three files you do not want are explained in the article. Again, to speed the process, delete the various temporary files. This should work for Win2k as well. The problem with this is that you definately have to export and import the email, whether Outlook or Outlook Express. If it is Outlook Express you also need to export and import their Address Book as well. This does not bring the printers over.

MS

Thanks for the reply... I knew/know of the manual process of copying over the profiles, sadly I was hoping (praying) that I could avoid that and somehow do it in batches or via some 3rd party app on the DC or SOMETHING. Manually copying 95 profiles just doesn't sound too appealing I guess.

I guess I will plan for a long-ass weekend in the near future.

 

[Allanv]

i have a script at work that i wrote that removes novel, joins the domain adds the users to a group for XP and 2k and anything else you may need

the manual process of copying the profiles is unavoidable but we did manage to narrow down to what we needed. the file transfer wizard is also ok for this.

if you want teh script let me know its just a 1 click bat file that you will need to modify for your needs

 

[Homerboy]

Originally posted by: Allanv
i have a script at work that i wrote that removes novel, joins the domain adds the users to a group for XP and 2k and anything else you may need

the manual process of copying the profiles is unavoidable but we did manage to narrow down to what we needed. the file transfer wizard is also ok for this.

if you want teh script let me know its just a 1 click bat file that you will need to modify for your needs

YESSSSSSSSSSSSSSSSSSSSS!

 

[Allanv]

YGM

 

[RebateMonger]

Originally posted by: redbeard1
If you join the computer to the domain, log in as the user once on the domain, then log in as someone else, usually the administrator, with view all files and hidden system folders on, go to Documents and Settings and find the original user profile. Copy all but three files from the old profile over the top of the new profile.

You can do the same thing without copying ANY files usng the method described in this UseNet posting.

This is the method that I use when moving client PCs from an old Domain to a new Domain. It's pretty fast.

All you do is create that new Profile by logging in once as the new Domain User, and then log in as a Local Administrator and change the Registry so the old User profile becomes the NEW User profile. The location of each User's Profile is in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\ProfileList.

 

[redbeard1]

Originally posted by: RebateMonger

Originally posted by: redbeard1
If you join the computer to the domain, log in as the user once on the domain, then log in as someone else, usually the administrator, with view all files and hidden system folders on, go to Documents and Settings and find the original user profile. Copy all but three files from the old profile over the top of the new profile.

You can do the same thing without copying ANY files usng the method described in this UseNet posting.

This is the method that I use when moving client PCs from an old Domain to a new Domain. It's pretty fast.

All you do is create that new Profile by logging in once as the new Domain User, and then log in as a Local Administrator and change the Registry so the old User profile becomes the NEW User profile. The location of each User's Profile is in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\ProfileList.

Does their pop3 email stay working using this method? Or does the email client need to be setup again?

 

[redbeard1]

Here's the original article for the registry version.

Certmag

 

[RebateMonger]

Originally posted by: redbeard1
Does their pop3 email stay working using this method? Or does the email client need to be setup again?

Any POP email settings seem to be retained, except for the passwords.

redbeard1,
Thanks for posting that original link. I hadn't seen that original article online.

I've moved three or four offices from old Domains to new Domains using the "Registry Method", and I've been pretty happy with it. COPYING User profiles can take a long time and it's never seemed 100% reliable for me. It always seems like, when doing 20 PCs, there'll be one or two that don't want to copy properly.

 

[Homerboy]

Originally posted by: Allanv
YGM

no PM yet

 

[Homerboy]

Rebeard1/rebatemonger:

Yeah I've read and seen those options before and are looking like my only candidates. I was hoping for some automated process, or at the very least a script of some nature...hell even 3rd party program, as to avoid manually putzing with 95+ machines (I guess it could be worse).

Regardless, thanks for the suggestions... please Allanv if you have that script PM me!!!

 

[RebateMonger]

Last month, I met with a company that specializes in high-end Active Directory tools. They were looking for new products, and I suggested taking a look at Profile Management tools for fixing corrupted Profiles and for Profile Migration.

 

[Homerboy]

Originally posted by: RebateMonger
Last month, I met with a company that specializes in high-end Active Directory tools. They were looking for new products, and I suggested taking a look at Profile Management tools for fixing corrupted Profiles and for Profile Migration.

and they are rolling it out in 2-4 weeks for $10?

 

[thunderingwolf]

Originally posted by: Allanv
i have a script at work that i wrote that removes novel, joins the domain adds the users to a group for XP and 2k and anything else you may need

the manual process of copying the profiles is unavoidable but we did manage to narrow down to what we needed. the file transfer wizard is also ok for this.

if you want teh script let me know its just a 1 click bat file that you will need to modify for your needs

I would love that script if you wouldn't mind. We are currently looking at migrating off Novell.

Thanks

 

[Allanv]

give me your email address and it shall be yours

 

[spyordie007]

Originally posted by: RebateMonger

Originally posted by: redbeard1
Does their pop3 email stay working using this method? Or does the email client need to be setup again?

Any POP email settings seem to be retained, except for the passwords.

redbeard1,
Thanks for posting that original link. I hadn't seen that original article online.

I've moved three or four offices from old Domains to new Domains using the "Registry Method", and I've been pretty happy with it. COPYING User profiles can take a long time and it's never seemed 100% reliable for me. It always seems like, when doing 20 PCs, there'll be one or two that don't want to copy properly.

Or you could just use USMT:
http://www.microsoft.com/downl...BE4C595&displaylang=en

Yes it still requires copying over the network, but it gives you a high-level of flexibility - such as the ability to limit which pieces of the profile to take with you.

Another possibility would be to write a quick script to update the registry key on the machines, it would be very easy to write something like this in PowerShell...

 

[t0mn8r]

I seem to remember that there is a way to extract info from NW (that nasty old beast). but it was so long ago (and I'm sooo senile) that I can't remember.

I think it was an option in NT 4.0...

So old.....

HTH

 

[2canSAM]

Just went through a 250 user move using USMT. We consolidated 4 domains into 1. The tool did everything we needed and worked like a charm, but I am really interested in that registry change. I will have to check that out in case we ever do this again (not likely at this company)

 

[Homerboy]

Originally posted by: RebateMonger

Originally posted by: redbeard1
If you join the computer to the domain, log in as the user once on the domain, then log in as someone else, usually the administrator, with view all files and hidden system folders on, go to Documents and Settings and find the original user profile. Copy all but three files from the old profile over the top of the new profile.

You can do the same thing without copying ANY files usng the method described in this UseNet posting.

This is the method that I use when moving client PCs from an old Domain to a new Domain. It's pretty fast.

All you do is create that new Profile by logging in once as the new Domain User, and then log in as a Local Administrator and change the Registry so the old User profile becomes the NEW User profile. The location of each User's Profile is in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\ProfileList.

Back to this again....
All I should need to do is simply edit that one registry setting from user.local to just user and everything should be copacetic? The CertMag article talks about editing the rights of the user.dat file:

However, just editing the registry path is not enough. User settings in the registry are stored in the user.dat file for each specific user. Only the original user has permissions to that file. You must give the new user permissions to the old user.dat. If you don?t do this, the default user profile will be used instead of the old one. To set appropriate permissions, you must do the following:

1. Launch REGEDIT from the command line to launch the Registry Editor. From the Registry Editor, go to File, Load Hive.
2. Navigate to the user.dat file of the old user. It?s located in that person?s folder under documents and settings. You need to make sure hidden files are visible (in Windows Explorer, select Folder Options, View, View hidden files and folders).
3. Once you have loaded the user.dat file as a hive, go to Edit, Permissions in Windows XP (or go straight to the Permissions menu in Windows 2000).
4. Give the new user full permissions to the registry key you have created. Once you are done, highlight the registry key and click File, Unload hive.
5. That?s all there is to it. The new user now has full access to the user.dat file.

I'm in an mixed environment of Win2k and XP. Do I need to do that too?

 

[RebateMonger]

I (and the original author) neglected to mention that if the new User isn't a Local Administrator on the PC, then you'll want to give the new User Full Control of the entire Profile.

 

[Homerboy]

yeah they wont be.. interestingly enough they WERE before but that right has... well been taken away until further notice
Regardless I just ran a rough test and it seemed to work and is certainly nicer and quicker than the copy/paste method.

 

[Homerboy]

RebateMonger you're on pager support this weekend right? I'm doing this migration then

 

[redbeard1]

However, just editing the registry path is not enough. User settings in the registry are stored in the user.dat file for each specific user. Only the original user has permissions to that file. You must give the new user permissions to the old user.dat. If you don?t do this, the default user profile will be used instead of the old one. To set appropriate permissions, you must do the following:

1. Launch REGEDIT from the command line to launch the Registry Editor. From the Registry Editor, go to File, Load Hive.
2. Navigate to the user.dat file of the old user. It?s located in that person?s folder under documents and settings. You need to make sure hidden files are visible (in Windows Explorer, select Folder Options, View, View hidden files and folders).
3. Once you have loaded the user.dat file as a hive, go to Edit, Permissions in Windows XP (or go straight to the Permissions menu in Windows 2000).
4. Give the new user full permissions to the registry key you have created. Once you are done, highlight the registry key and click File, Unload hive.
5. That?s all there is to it. The new user now has full access to the user.dat file.

I just used this to migrate an office of 15 users from their old SBS 2003 server domain to their new SBS server.

Some observations from the process.

I found that I had issues getting the workstations to properly join the new domain by simply changing the domains. On the workstations that I was going to change, I would manually set the dns to look at the new server, and I still ended up having odd ldap and kerberos issues. The best way was to back the workstations out to a workgroup, reboot the computer into that workgroup, then change the dns setting to the new server and join the new domain.

After using the above registry hacks a few times, I decided that to get consistant successful results, I would reboot the computer after the changes were made. I had a few of the systems not boot properly into their profiles the first time after I made the changes from the adminstrator account, even though the user.dat hive was supposedly unloaded, and the user was given full rights to his original profile. Rebooting right after I made the registry changes and then going into the users account fixed the inconsistancies.

Like the File and Transfer Wizard, this change does not bring over the password for pop accounts in Outlook, so they need to be added again.

They use external pop mail accounts so I exported their email out of Exchange to the workstations, let them use pop during the conversion, and then imported it back into the new server when they were joined in. An issue with importing their pst to the Exchange Server is that their local contacts do not show up when they go to create a new email and click on the TO button. You need to right click the contacts folder, choose properties and then find the check box that says something to the effect of "show this in the contacts list".

One of the computer users had a Dell Axim PDA, and he had to run through the active sync user setup again, as it was smart enough to know that something had changed with the profile he had been using.

One of the systems had a nasty trojan on it and I had to clean it as the trojan had changed permissions to prevent anyone from getting into the Control Panel, which I needed to use for changing the email settings. I was finally able to get the accounts into the control panel once and change the settings, but it prevented me from getting in a second time. I was able to make it so the local administrator account could get into the Control Panel, so I made the domain change with that account. My fear was that when I let them back to their old profiles, the problem would reappear, but once in the new domain, the problem stayed gone. I'm assuming that the application of the new Group Policy was able to over ride the damage done by the trojan.

Comparing the options of using the File and Settings Transfer wizard, copying the profile over manually (not copying the three ntuser files in the root of the users profile folder), and using this registry method, or manually backing up their data and then manually importing it, the registry procedure seems to be best option once you get the hang of it.

:thumbsup:

 

[redbeard1]

Another update.

A couple of days after things were finished, I had the customer call me and say that two user could not see there desktop, email and such. In talking with them I found that when they logged on, the computer had displayed the message that the system could not find the user profile so the default profile was loaded. I had both users reboot their computers and they were then able to logon normally.

When I was first trying this profile migration method, I found that if the user did not have rights to their old profile, as the article describes, this same error would occur. Since some of these computers have multiple users, I added domain users to the local adminstrators group.

My assumption on the errors the users saw the other day was that when they turned their computers on, the systems had not finished running all of their processes and did not have a complete connection to the domain yet.

Anyone else observed this?

Originally posted by: RebateMonger
I (and the original author) neglected to mention that if the new User isn't a Local Administrator on the PC, then you'll want to give the new User Full Control of the entire Profile.