Keeping registry settings when joinging a new domain

[fbicfc]

Hi,

I am about to switch on a replacement server running SBS 4.5 and have discovered that the w2k computers need to be re-joined to this server even though the server is a straight swop in every detail (IPs/Server name/Shares etc).

The problem that occurs is that the w2k computers seem to create a new user profile with default settings and not the actual user profile when they are re-joined to the new server, this means that our developers are losing all of the settings in the registry for components and other sw that they use.

Is there a way to export the users and import them to the new server?

Any help will be appreciated.

 

[markco20]

My first recommendation is using Microsoft's User State Migration tool. You may want to use a test machine first to see how this works for you.

http://www.microsoft.com/windows2000/techinfo/reskit/tools/new/usmt-o.asp

Another option is through a list of registry tweaks. You'll need to change domains and log into the domain with the user first. This will create a profile directory under %systemroot%\documents and settings\username.<newdomain>. You should now have the old user directory named username and the new one named username.<newdomain>. (this could be different based on your specific circumstances, but the concepts the same) From there, try the following.

First, make sure the domain user has full rights to his/her profile directory under the new domain.

Go the Security tab for %systemroot%\profiles\%username%\ and verify user has full control over their home directory. If their domain account does not have full control, it will cause a new profile directory to be created.

Second, make sure the user has full control over the ntuser.dat file in their profile directory. The NTUser.dat hive gets loaded into HKEY_Current_User and includes all of the individual users registry settings.

To do this, follow the following steps.

1. Log on with a local-administrator account (not the user's account).

2. Change the permissions on ntuser.dat to allow the user to access it. Start Regedt32 and go to HKEY_USERS. With HKEY_USERS selected, click the Load Hive option from the Registry menu. Select the file &quot;%SystemRoot\Documents and Settings\Profiles\username\Ntuser.dat, where username is your domain account name.

3. When prompted to enter a key name, type in any name as it just corresponds to the temporary location. You can now see an entry for the new key. Select it and click Permissions from the Security menu. Now, add the user and give him/her full control. You may also want to click on Advanced on the security tab and choose Replace Permissions...

4. Click on the hive you loaded and choose Unload Hive from the Registry menu.
**** YOU MUST UNLOAD THE HIVE OR THIS WON'T WORK ****

5. Finally, you need to change the path Windows looks for the profile. In Regedt32, go to the following key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList

6. You should see a list of SIDS. Look for through the SIDS until you find the ProfileImagePath value pointing to the erroneous directory (i.e. C:\Documents and Settings\username.dom when it should be C:\Documents and Settings\username) . When you see this, edit the ProfileImagePath so it points to the appropriate directory

7. Log off of local administrator and log back in as the user, this should bring back the correct profile.

- Tweek -
Information Systems Analyst
Consulting Group in L.A.

- Tweek -
Information Systems Analyst
Consulting Group in L.A.

 

[fbicfc]

Tried using the USM but it only works for Win 9x & NT4 users.

I am getting mixed results using other methods, the best method I have found (don't quite understand how it works), if you log in the w2k terminals to the network and then switch the server over without logging out the w2k terminals, the w2k computers appear to negotiate and join the new server domain automatically with no need to re-join the domain.

Thanks for you help.