Single NT4 PDC to single 2K3 AD master?
Single NT4 PDC to single 2K3 AD master?
Author
Discussion

SneakyNeil

Original Poster:

9,296 posts

268 months

Sunday 1st July 2007
quotequote all
Anyone done this, I'm going to take a wild guess that it's not as straightforward as the procedure for replacing one AD master with another?

Clients are XP...

Answers on a postcard? Cheers!

snowy

542 posts

312 months

Sunday 1st July 2007
quotequote all
If your server is running NT4 then i assume that it is very old, you may be best advised to buy a new server and migrate users/compters to a new win2k3 forest using the "Active Directory Migration tools" (ADMT), ensure you maintain the SID history, this would enable users to maintain access to their current data, once all users/computers have been moved then move any data across

SneakyNeil

Original Poster:

9,296 posts

268 months

Sunday 1st July 2007
quotequote all
snowy said:
If your server is running NT4 then i assume that it is very old, you may be best advised to buy a new server and migrate users/compters to a new win2k3 forest using the "Active Directory Migration tools" (ADMT), ensure you maintain the SID history, this would enable users to maintain access to their current data, once all users/computers have been moved then move any data across
Yes sorry I didn't make that clear, the 2k3 hardware is new. Is it essentially the case that you establish a period of parallel running, move services over and then gracefully retire the old box or is it a one-way step change kind of thing?

I'll read up on ADMT, cheers.

theboss

7,555 posts

250 months

Sunday 1st July 2007
quotequote all
I'd perform an in-place upgrade on the domain, unless you have any specific reasons not to. If the NT box is beneath the hardware requirements for Win2003 then clone it to a temporary or virtual server, perform the upgrade on that machine, then bring in the new DC, move everything over and dcpromo the old one.

kiwisr

9,335 posts

238 months

Sunday 1st July 2007
quotequote all
Safest way, and recommended by MS, would be to install NT4 on the new server and make it the PDC. Then upgrade this to W2K3. If anything goes wrong you can just re-promote the original NT4 to PDC again.

This also has the advantage that you can practice the upgrade offline beforehand, as usually the biggest problems in upgrading an old NT4 box will be driver based.

But do not do an in-place upgrade on the existing PDC, that's just about the worst thing you could do. If it goes wrong, and it probably will, then you could end up in a messy situation.

Edited by kiwisr on Sunday 1st July 13:40

theboss

7,555 posts

250 months

Sunday 1st July 2007
quotequote all
kiwisr said:
But do not do an in-place upgrade on the existing PDC, that's just about the worst thing you could do. If it goes wrong, and it probably will, then you could end up in a messy situation.
Agreed, as I said, I'd be inclined to clone it and do the upgrade in isolation. Should be able to do it with a copy of Ghost and the free VMware converter.

Edited by theboss on Sunday 1st July 13:59

malman

2,258 posts

290 months

Monday 2nd July 2007
quotequote all
Yep done it and did it the virtual route. Took a virtual BDC offline in case off emergency. Created a virtual NT4 PDC to be upgraded to 2003 temporarily and left the new hardware with a clean install of 2003.

SneakyNeil

Original Poster:

9,296 posts

268 months

Monday 2nd July 2007
quotequote all
Sounds like a plan, cheers guys thumbup