nt domain controler win 2000 server

hi Folks,

i have to create a new server to run as the PDC of our nt domian. the domain controler is an nt4 server box. does anyone know if its possible to use win 2000 and a bdc on an nt domain? if so any tips on going about doing it?

[QUOTE=wyntrblue;373489]hi Folks,

i have to create a new server to run as the PDC of our nt domian. the domain controler is an nt4 server box. does anyone know if its possible to use win 2000 and a bdc on an nt domain? if so any tips on going about doing it?[/QUOTE]

Are you wanting Win 2000 as a member server? If so then yes, it will work.

Are you saying you want the 2k server to be the BDC? If so then it can’t be done. It can be a ‘PDC emulator’ if you’re doing an in place upgrade of an NT PDC to 2k, but never a BDC.

Otherwise, see Juggy ^

yea we want the 2k server to be the bdc. cant be done eh :frowning: well that stops us dead in our migration tracks lol…

migration, up to 2000 ad? in which case it can be done, I’ve gotten my cource notes at work, if I get time I’ll dig them out and find the bit’s you’ll need. iirc it’s complicated, and not exactly straight forward, how big is your company, could you not start from scratch, programaticaly export the user setings from the nt domain into the 200 ad, I know I looked at doing this for our place a few years back, it was going to be easier than the ‘upgrade’

we have allready migrated the users from nt to a 2k3 AD domain, but i have been told we need to keep a cold standby of the nt domain. but the DC for the nt domain is going to be rebuilt for another use (as its not a bad machine) so i am supposed to replicate the current server. i dont wanna use nt unless i have no choice…

What you can do in that situation is to build a vanilla NT BDC, promote it to PDC then perform an inplace upgrade to 2k. You will still need to enter AD info for it’s potential new role as the first AD DC, but it will become a ‘PDC Emulator’ and handle your NT domain logons, but any BDCs will need to remain as NT.