dcpromo an creating a new domain in Windows 2000 AD (mixed-mode)

[Guest]

Hi!
I have a mixed-mode Windows2000 AD domain which now have cumbersome and somewhat not recommended (FQDN) domain/dns name called aek02.aek.fi. I have one Windows 2000 DC server (full host name is aek02.aek.fi => that
cases/generates Userenv 1000 and Kerberos errors together aek02.aek.fi domain/dns) whose role is DC/DNS/GC, then I have one Windows 2000 Server as Member Server (full host name is aek03.aek.fi) and finally I have one
NT 4.0 BDC Server left.
My one DC stands for Oracle8i and file server, W2K Member Server stands Solid and Pervasive SQL and print server, NT 4.0 BDC has MS Exchange 5.5 installed (we use Exchange 5.5 only for lan/internal, because our mailboxes is physically located ISP´s and we use ISP´s.
I have 21 W2K Professional workstation with SP4. Also we have no own web -server => the ISP hosts our external web site (www.aek.fi)

So my question is that I want to get rid of that aek02.aek.fi domain/dns and want to dcpromo
W2K Member Server (aek03.aek.fi) to DC and create new domain root called
aek.fi. What is the best workaround to rename old domain/or make a new domain in my situ.

Many thanks in advance !

-Mika-

 

[Jim Singh]

Mike -

Since you have aek2 as DC-DNS and GC, this process will require some work
based upon how the dns zones are setup. I recommend that when you promote
the aek3 as DNS sever make it AD-integrated zone, this will take care of the
manuall replication if you were to create other zones in your organisation.
Now, you can take the following steps for DC/DNS?GC transition;
a: create the aek3 as additional domain controller in the aek.fi domain.

b: let it replicate with the aek2. normally i would suggest about 24 hours.
you can force replicate it too with replmon.

c: install DNS on it and create the forward lookup zone similar to aek2.

d: if aek02 is ad-integrated zone, then you dont have to manually add hosts
and mx records in aek03. if not, then add the hosts records and MX record
for you exch 5.5 server.

e: assign the aek03 the GC role from ad site and services.

f: do the aek02 demotion; that included transferring the FSMO roles. you can
use ntdsutil.exe for this. or use gui mode. iam assuming since you only have
one dc in your environment, you probably have all your roles on aek02! so
transfer all the 5 fsmo roles.

g: turn aek02 off. delete the aek02 computer account from AD.

Make sure to test these procedures in lab first!
-Jim

Hi!
I have a mixed-mode Windows2000 AD domain which now have cumbersome and

somewhat not recommended (FQDN) domain/dns name called aek02.aek.fi. I have
one Windows 2000 DC server (full host name is aek02.aek.fi => that

cases/generates Userenv 1000 and Kerberos errors together aek02.aek.fi

domain/dns) whose role is DC/DNS/GC, then I have one Windows 2000 Server as
Member Server (full host name is aek03.aek.fi) and finally I have one

NT 4.0 BDC Server left.
My one DC stands for Oracle8i and file server, W2K Member Server stands

Solid and Pervasive SQL and print server, NT 4.0 BDC has MS Exchange 5.5
installed (we use Exchange 5.5 only for lan/internal, because our mailboxes
is physically located ISP´s and we use ISP´s.

I have 21 W2K Professional workstation with SP4. Also we have no own

web -server => the ISP hosts our external web site (www.aek.fi)