Step by step: hot to migrate from NT 4 Server to windows 2003 server w

[crazy72]

i've readen many articles around about this problem and this is what i will do to migrate our nt server to windows 2003 server.
The final result is that we cannot rejoin each client to new server and not migrate all client desktop and users.

Direct migration is impossible cause sam,sid and other protection.
So i've not a bdc in my domain.
- I will add a bdc to existent pdc.
- To continue to work during the operation i will detach bdc (synchronized with pdc)
- I'll connect it to a notebook or hub (for ad)
- I'll promote it to a pdc
- i'll upgrade the operating system to win2k3
- i'll test it with a client connected to the old server, if no error around i'll detach old pdc and replace it with new win2k3 server
Doing this i will retain all accounts and security option.
- After all i'll move all data and recreate share connection and policy on directory ( for this i need to do from the beginning, old policies are not more valid)

Can be this a good and fast method ?

Thanks for all answer
Chris

 

[88bw]

Hello;
Having just gone through this process successfully here is an alternative path to upgrade.
1. Build an NT4 Server BDC
2. Sync with PDC
3. Upgrade to 2000 Server w/AD using migration tools (adprep)
4. Promote to PDC
5. Upgrade former NT4 to 2003
6. Sync with current PDC (the one you built and upgraded)
7. Promote to PDC-demote other to BDC

I think I have it all in there. Pretty easy. I would as back-up export all user info to a spreadsheet in case of any hiccups. btw....BACK-UP current DC before upgrade in case of major failure. Better safe than not.

 

[88bw]

I just reread your post....you got it covered just different terminology.....sorry for the repitition.