Adding Windows NT 4.0 Workgroup to Win 2003 Domain Environment

[tekgirl23]

Hi,

Currently, we are working on a mass migration on moving XP workstations from Windows 2000 domain to Windows 2003 active directory network using ADMT 3.0.

I have a Windows NT 4.0 server that is not part of the domain that will need to be moved to Windows 2003 domain. We will not upgrade it to Windows 2000 until later. It's more of a priority to get it moved to the new domain.

My question is what special steps would I need to take to migrate/join my NT 4.0 Server to the 2003 domain. I will need to preserve user profile and desktop settings so when it's moved to the new domain, the same profile and desktop settings are loaded. I know it has to be more than just adding it to the new domain. If I do that, I will have to manually copy my profile to the new domain account.

Also I'm sure I need AD client software so the NT machine will be able to authenticate against the new network however I wanted to throw it out here on this forumn to get ideas from other people who might have done the same thing.

The NT 4.0 server has a host of applications running such as SQL Server, ColdFusion, Java, etc...and I want to ensure nothing breaks.

Your help would be greatly appreciated.

Thanks,

Cooley

 

[WhoKilledKenny]

There should be no issue with making the NT Server a member of your AD, as long as it is a memeber server (not a PDC or BDC). The only place I could see a problem is if you were not running NetBIOS, but other than that there should be no problem.

For SQL, as long as you don't change the netBIOS name of the server it should not have any issues.