Migration from Win NT to 2003

[kcpant]

Hi friends,


Is migration from Win NT 4.0 server to Win 2003 Std Server possible? if yes, what is the process to do that? one of my client using a win NT 4.0 domain setup having around 200 machines as client and 2 server, one PDC and one BDC.I want to upgarde these servers to W2K3 Std, and without loosing any hierarchy and domain configuration.

[Norman_21]

KC,

You need to use the ADMT Tool:
http://www.microsoft.com/downloads/details.aspx?FamilyID=788975b1-5849-4707-9817-8c9773c25c6c&displaylang=en

Hope this help

[kcpant]

Thanks Latif, for immediate reply. I need some more information on practical experience of migrating from NT 4.0 to W2K3, If you have done this kind of upgrade ( I've used ADMT for NT 4.0 to 2000), please suggest more elaborately what procedure to be followed. I want to remind you that I'm going to upgrade the same server, not migration to another server.

[Colin_29]

It is dead easy to do an in place upgrade but personally I think that that method leaves a bit to be desired. The main problem is that NT4 forces a 4GB partition size whereas with W2K3 you have no restrictions and I tend to use a minimum of 12GB. Depending of what the server is used for and if there is a need to use quotas etc, I will often use the whole disk space for the C drive.

Back to the practicalities: generally I introduce another temporary server as an NT4 BDC and promote it to a PDC. If able to do so I would then shut down one of the BDCs to safeguard the SAM just in case all goes wrong (it hasn't yet and I've done quite a few).

Next, install W2K3 on the new server (now a PDC) and follow the process through running DCPROMO, allowing it to create DNS, etc. You will end up with a W2k3 domain.

Then blow away each of your old NT4 BDCs in turn and rebuild to W2K3 from bare metal. In this way you will get good clean builds. Then run DCPROMO of them to make them DCs.

Finally distribute the FSMO roles over your two DCs, run DCPROMO on the temporary server to take it back down to member server status and then remove it from the domain. Job done.

[Colin_29]

Of course, only having two servers, you would need to shuffle data around and mess about a bit with DHCP, WINS etc. but none of these issues are insurmountable, they just need a bit of planning.

[Norman_21]

KC,
I believe that the Concept is more important than the physical steps for the upgrade so please get ready with a pen and a small note while watching this WebCast for Migrating Windows NT 4.0 to Windows Server 2003:
http://msevents.microsoft.com/cui/WebCastEventDetails.aspx?culture=en-US&EventID=1032264134&EventCategory=3

Meanwhile, get the following commands from the resource kits for NT 4.0 to clean up the SAM Database prior to the upgrade. You don't want to migrate disabled users accounts for people who may have left the company long time ago.

usrstat yourdomainname > C:\user.txt
net group > C:\group.txt

Above will collect information from both PDC and BDC Servers. Examine the text file with your staff to determine which accounts or groups need to be removed. Off course the group database will be collected from the PDC only.

To quickly list the upgrade steps:

1. Clean up the SAM DB from unused accounts & groups.
2. Insert the W2K3 Upgrade CD in the WinNT 4.0, run d:\I386\winnt32 to do the upgrade.

4. When the server reboots, you'll be prompted with the AD wizard

5. Run the AD for the PDC as the First Domain in the forest
6. Chose Interm Mode. This option will not allow 2000 DC but it'll allow 2000 computer just not DC.
7. Chose to Install and configure DNS Server option
8. Since you still have BDC, chose Permission compatible with pre-windows 2000 Server
9. When finished the AD, you'll find all the migrated users in the USERS container of the AD Users and computers.

10. Create OU and move the users for easy account management

Upgrade your BDC to a member server and join it to the Domain Controller.

I still advice you to watch the WebCast first.

Sorry for the delay but I didn't get a chance to get online before this time

Take care





Above commands will

[Colin_29]

I agree with LATIF, take a look at the webcast but you will need to skip some bits as it is in true Microsoft style and covers large corporates (multi-domains etc.) At least you will see the process up front.

The main thing is to plan ahead. DNS is key so you need to look into that up front. On a small system like yours I would let the wizard create DNS for you during the upgrade.

As I said in my previous post, following the pure upgrade path as LATIF describes and as is on the webcast, will result in you having a 4GB partition. If this is ok for you then go for it. It will however be more of a hardship to sort out at a later date if you find that your C drive is full.

Good luck
Colin

[kcpant]

Thanks Latif & Colin for the help, I'll do it accordingly on next week ( and will assign points too :) )

thanks again, thread is still open for your suggestions..

[Jon Finley]

Here's the main MS link you'll need for the upgrade: http://www.microsoft.com/windowsserver2003/upgrading/nt4/default.mspx

Jon

[Jon Finley]

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

http://www.microsoft.com/downloads/details.aspx?FamilyID=e92cf6a0-76f0-4e25-8de0-19544062a6e6&DisplayLang=en

Jon

[Norman_21]

Just comment about the 4GB C:\ partition.
Personally, I'd rather make it 4GB since it'll save alot of time when running defragmentation and cleaning up your C:\ drive.
Then, when installing new applications, I'll just redirect them to D:\ or any other partition than C:, specially if you have Backup Exec or any application that grows in size.

In regard of the DNS, put the same domain name of the PDC, e.g.) kcpant.com even though it's recommended to use the LOCAL extension instead of the COM extension for security reasons but it really depends on you and how you want to setup your environment!


Hope this help

[Oleg Koroz]

According your feedback you dealing with Proliant Servers, so you might know needs of:
http://h18023.www1.hp.com/support/files/server/us/download/10776.html
Primer should be done from NT4 before Upgrade to W2K and w2K3
Firmware http://h18023.www1.hp.com/support/files/server/us/index.html as System Rom, Array controller ..etc
You have to patch some NIC with Updates
http://h18007.www1.hp.com/support/files/networking/nics/index.html
And white papers for Upgrade
http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00208465/c00208465.pdf

[Norman_21]

kcpant & Colin,

The hats look nice on you guys!!!
Keep up the great work

Congrats,

Latif

[Colin_29]

Thank you LATIF. I think the colour is particularly nice and it has only taken me two years. How do you guys find the time?

[Norman_21]

Colin,
I know how you feel because I felt the same when I got my paceball hat.
How do I find the time? When ever I get a chance, trust me.

[kcpant]

Hi Friends,
Thanks Latif, I'm happy to see a hat on my head, and same like Colin, It's taken "only" 2 years for me also.

Thank you all friends, you all have good knowledge of migration ( A little bit I do have, and , as KOV replied, I also strongly recommend to first update FW for all hardware+PSP update+ other updates if available.) I've done some migartion projects on Win2000, but I was lil bit hasitated about W2K3 upgrade, but, hats off to you guys, you have given a lot of good sugestions to get it done.

Thanks again

K C Pant