Hello NAJMUSSAQIB,
1.
Just to clarify your terms, child domain controller is an additional DC in
the same domain according to your naming list and not belonging to a real
child domain?
2.
Secondary DNS is a real secondary DNS zone or a second DNS server?
Also PDC/BDC is since Windows 2000 not longer used as terms, all DCs are
the same, the differences belong to the 5 FSMO roles and there placement.
According that 1 is additional and 2 is just a second DNS server in the domain
you can follow the next steps:
!!!NEVER START BEFORE HAVING CREATED AND TESTED A BACKUP OF YOUR DATA/MACHINE!!!
- For Exchange control if this applies, shouldn't but just check:
http://support.microsoft.com/?id=314649
- Also if you use Exchange 2000 in the domain see this for adding 2008 DCs
to the domain, ONLY Exchange 2000 SP3 is allowed with RESTRICTIONS:
http://msexchangeteam.com/archive/2007/08/16/446709.aspx
- On the old server open DNS management console and check that you are running
Active directory integrated zone (easier for replication, if you have more
then one DNS server)
- run replmon from the run line or repadmin /showrepl(only if more then one
DC exist), dcdiag and netdiag from the command prompt on the old machine
to check for errors, if you have some post the complete output from the command
here or solve them first. For this tools you have to install the support\tools\suptools.msi
from the 2003 installation disk.
- run adprep /forestprep and adprep /domainprep and adprep /rodcprep from
the 2008 installation disk against the 2003 schema master(forestprep) / infrastructure
master(domainprep/rodcprep), with an account that is member of the Schema/Enterprise/Domain
admins, to upgrade the schema to the new version (44) or 2008 R2 (47)
- you can check the schema version with "schupgr" or "dsquery * cn=schema,cn=configuration,dc=domainname,dc=local
-scope base -attr objectVersion" without the quotes in a command prompt
- Install the new machine as a member server in your existing domain
- configure a fixed ip and set the preferred DNS server to the old DNS server
only, think about disabling IPv6 if you are not using it, some known problems
exist with it. Follow (http://blogs.dirteam.com/blogs/paulbergson/archive/2009/03/19/disabling-ipv6-on-windows-2008.aspx)
to disable it
- run dcpromo and follow the wizard to add the 2008 server to an existing
domain, make it also Global catalog and DNS server.
- for DNS give the server time for replication, at least 15 minutes. Because
you use Active directory integrated zones it will automatically replicate
the zones to the new server. Open DNS management console to check that they
appear
- if the new machine is domain controller and DNS server run again replmon,
dcdiag and netdiag (copy the netdiag from the 2003 to 2008, will work) on
both domain controllers
- Transfer, NOT seize the 5 FSMO roles to the new Domain controller (http://support.microsoft.com/kb/324801
applies also for 2008), FSMO should always be on the newest OS DC
- you can see in the event viewer (Directory service) that the roles are
transferred, also give it some time
- reconfigure the DNS configuration on your NIC of the 2008 server, preferred
DNS itself, secondary the old one
- if you use DHCP do not forget to reconfigure the scope settings to point
to the new installed DNS server
- if needed export and import of DHCP database for 2008 choose "netshell
dhcp backup" and "netshell dhcp restore" command (http://technet.microsoft.com/en-us/library/cc772372.aspx)
Demoting the old DC
- reconfigure your clients/servers that they not longer point to the old
DC/DNS server on the NIC
- to be sure that everything runs fine, disconnect the old DC from the network
and check with clients and servers the connectivity, logon and also with
one client a restart to see that everything is ok
- then run dcpromo to demote the old DC, if it works fine the machine will
move from the DC's OU to the computers container, where you can delete it
by hand. Can be that you got an error during demoting at the beginning, then
uncheck the Global catalog on that DC and try again
- check the DNS management console, that all entries from the machine are
disappeared or delete them by hand if the machine is off the network for ever
- also you have to start AD sites and services and delete the old servername
under the site, this will not be done during demotion
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!!
http://www.blakjak.demon.co.uk/mul_crss.htm
| Quote: |
Dear All,
Consider the following scenario:
1. FOREST: MAHYKHOORY.CO.AE
2. Domain Controller: PROXY.MAHYKHOORY.CO.AE
3. Child Domain Controller: APPSRVR.MAHYKHOORY.CO.AE
4. Operating System: Windows Server 2003 SP2
DNS services are running on both in terms of Primary and Secondary.
DHCP service is running on a Child D.C. FSMO and Global Catalog
resides on PROXY.MAHYKHOORY.CO.AE. MS EXCHANGE 2000 is running on a
seperate box i.e. mail.mahykhoory.co.ae. We have a internet gateway as
netsrvr.mahykhoory.co.ae (MS ISA 2004).
Since, we have two domain controllers (PDC and Child DC) and they
contain the exact replica of an AD, it will be easy for us to offline
PDC and let Child DC handles the operations for the time being. In the
meantime, we will make the a new PDC with the same hostname as of
current PDC and migrate AD to Windows 2008 AD (from Child DC). Also,
is it possible to keep PDC on Windows 2008 and Child DC on Windows
2003?
A step by step procedure will be much appreciated (including the tools
).
Thanks,
- NAJMUSSAQIB
|
Windows-Expert.com Forum Index
•
FAQ
•
Search
