Help needed transfering data from NT server to 2003 1

[projector1]

Hi
We are planning to take the old admin server (Windows NT4 serever) down and replace it with a windows 2003 server. I would be greatful if you could give me some ideas on how i would transfer the user accounts, profiles, data from the old NT server to the new Windows 2003 server. Like i said we are not upgarding the old server but replacing it with a brand new server.

thanks

 

[bofhrevenge2]

You could type net user > c:\filename.txt at a command prompt on the pdc. This will dump all the usernames to the target file in text format. If you turn this into a CSV then you can import the names into AD.

http://www.computerperformance.co.uk/Logon/Logon_CSVDE.htm

As for moving the data i usually use XCOPY but redirecting a backup to the new server should work just as well. Alternativly depending on the amount of data you could just connect across the network to the other server and use explorer, the only problem is that this will stop on errors without telling you how far it got.


Hope this helps.

 

[newbobbys9]

I have a related question. Many of my PDCs were used for other things over the years--shares, apps and printers. Is it possible to upgrade to a 2003 member server. Microsoft states that after the upgrade the server is in limbo until assigning a dc role. But is it possible to have it ignore the upgraded sam, and become a member server? Thanks.

 

[bofhrevenge2]

I'm really not sure, under NT4 this is not possible but it is possible to downgrade a 2003 DC to a member server using DCPROMO.

Unless anyone else knows better i'd try building an NT4 PDC then upgrade it to 2003 to try the theory.

Let me know how you get on.

Thanks.

 

[RachelD]

I'm sure there is someone out there who knows for sure, but I don't think you can upgrade to a member server.

Another option you have is to change the role of the NT server prior to installing 2003. Then you could upgrade those servers in place without having to bring lots of DCs onto the domain.

I used a utility called upromote (

http://utools.com/Default.asp)

to downgrade an NT BDC to a member server when I rebuilt my domain and brought in a new PDC and BDC to replace the old ones. I had this old NT BDC running on the network for a few weeks as a member server while I brought its Windows 2003 replacement online.

If you have a lot of servers, I think it's only about $200 - $250 for unlimited use at one site. Not too bad considering the trouble it can save.

 

[Claudek]

In regards to the original question, To have Windows 2003 handle user accounts etc, it has to be a Domain Controller (this entails a little bit more than from NT).
Good news for you is that Microsoft has an excellent tool which will allow you to migrate across all your user accounts and security groups and roaming profiles etc from NT to Windows 2003. It will also migrate across workstations and user profiles there to the Windows 2003 domain. You will need to create another domain in Windows 2003 - so if your NT domain is ACME, your new domain can be called ACMECO.local for eg (can't be same as old one).

Have a look here for more info -

http://www.microsoft.com/windowsserver2003/upgrading/nt4/tooldocs/default.mspx

Unless you have a very complicated domain/network, the migration should go quite easily (with planning of course).



Claudius (What certifications??)

http://www.iteq.com.au

 

[markdmac]

Projector1,

If you wish to replace your existing server while preserving your user data you can use ADMT. A copy of this is on the Windows 2003 CD or can be downloaded fromt he link Claudius posted. ADMT will allow you to move both computer and user accounts over. However, it sounds to me like you probably want to go another route.

If I were you I would introduce a swing server (temporary server) as an NT4 BDC in your NT4 domain. Wait for the SAM database to replicate, then promote it to PDC and shut down the old PDC. This way you have a full backup plan in case anything goes wrong. Upgrade the swing server to 2003 to get your AD configured and the SAM accounts migrated to AD. Now you can introduce your new Windows 2003 server and promote it to a DC with DCPROMO. You will need to configure this new server with DNS and DHCP. Your next step would be to transfer the FSMO roles to the new server from the swing server. When you verify that the 5 FSMO roles are now on the new server, you can use DCPROMO to demote the swing server to a member server, then remove it permanently from the domain. Again, if anything goes wrong you can then just power back up your old PDC and be back at square one. For the swing server, you could use a newer workstation, just something with enough to run Win2k3 temporarily.

I hope you find this post helpful. Please let me know if it was.

Regards,

Mark

 

[markdmac]

Newbobbys9,

unless you use a third party utility as was described above to turn a BDC into a member server without a reload, what you are asking can NOT be done. In an NT4 domain, the PDC MUST be the first DC to be upgraded. You can introduce 2000 or 2003 member servers till your heart is content, but can not upgrade a DC until the PDC goes first.

I hope you find this post helpful. Please let me know if it was.

Regards,

Mark