Re: How to replace single domain controller in domain with a singl



Hello danyadd,

As stated in the article (http://technet.microsoft.com/en-us/library/cc794951.aspx)
Although you can use System Properties to rename a domain controller (as you can for any computer), Active Directory and DNS replication latency might temporarily prevent clients from locating or authenticating (or both) to the renamed domain controller. To avoid this delay, you can use the Netdom command-line tool to rename a domain controller.

Doesn't matter when you change the ip.

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


Thanks very much for your reply,
I think I will follow the first procedure because I don't have a temp
DC to
add to the domain.
I have two more questions.
1) Renaming the DC:
I didn't know about the Netdom.exe command-line tool way.
I was thinking to use the System Properties user interface (UI).
What's the difference?
2) Should I first change IP address or DC name?
Thanks

"Meinolf Weber" wrote:

Hello danyadd,

After preparing the domain for 2008 with adprep command you can
follow the arcticle. If all is done, remove the old machine from the
network and then rename the DC and change the ip address to the old
one. Also you have to delete in AD sites and services the old DC
name, not done during demotion.

Rename 2008 DC:
http://technet.microsoft.com/en-us/library/cc794925.aspx
Another way would be more work but also more secure for AD:

- install a temp DC in the domain, move all 5 FSMO roles, make it GC
and

DNS (Ad integrated zones), export of DHCP database for 2008 choose
"netshell

dhcp backup" and "netshell dhcp restore" command
(http://technet.microsoft.com/en-us/library/cc772372.aspx)

- run dcdiag, netdiag and repadmin /showrepl to check for errors

- prepare the domain for 2008

- demote the old DC to member server, reboot and rename it, reboot
and change

the ip address and run ipconfig /registerdns, check the DNS zones for
the

correct changes ip/name

- install the 2008 with the old ip/name and promote, make it DNS
server,

GC and move all 5 FSMO roles, import of DHCP database for 2008 choose
"netshell

dhcp backup" and "netshell dhcp restore" command
(http://technet.microsoft.com/en-us/library/cc772372.aspx)

- run dcdiag, netdiag and repadmin /showrepl to check for errors

- move the files/printers

- remove the old 2003 member machine from the domain

- demote the temp DC to member server and remove it from the domain

- check DNS configuration and remove old server entries if exist

- open AD sites and services and remove the old DC's from the list

- run dcdiag, netdiag

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
We are planning to replace our only domain controller running
Windows
2003
x86 standard SP2 with a new server running Windows 2008 x64
standard.
We have a single Windows2003 native forest, single domain, with 1
domain
controller. The server to be replaced holds the all the FSMO roles.
We
are running Active Directory Integrated DNS on the server we are
replacing.
It is critical for us to keep the same server name and IP address
for
the new server, because everything on our network is pointing to the
server we are replacing.
I've found this page
http://support.microsoft.com/default.aspx/kb/555549/en-us
but i'd like to know:
1) Is this article applicable also to Windows 2003 -> Windows 2008 ?
2) How can I keep the same server name and IP address ?
Thanks in advance for any tips or useful links
Daniele



.



Relevant Pages

  • Re: Domain controller name -rename issue
    ... Make sure you have at least a system state backup before starting the rename of the production one. ... The DNS host names of domain controllers in a renamed domain are not ... Windows NT 4.0 primary domain controller to Windows 2000 ... it with dcpromo /forceremoval to member server. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Replacing current DNS/DHCP server...
    ... First by running dcpromo make win 2003 an 'additional domain controller ... 2.Make win 2003 Global Catalogue and allow time for replication. ... On win 2000 server backup DHCP database in a path available on the ... On win 2000 stop DHCP server and start DHCP server on win 2003. ...
    (microsoft.public.windows.server.dns)
  • Re: Domain controllers
    ... other DNS was still on the zones transferred to the new domain controller. ... Both DHCP and WINS databases CAN be move -- there are KB ... from one server to another -- search Googgle against Microsoft ...
    (microsoft.public.win2000.active_directory)
  • Re: Server 2003 Client Access issues
    ... I would disable the DHCP on the router and use your server only to give ... gateway for your server and all the other computers by adding it to the DHCP scope on ... support tool netdiag on your domain controller when done to see if it reports a clean ...
    (microsoft.public.win2000.networking)
  • Re: Need to set up DHCP on domain controller???
    ... Well I have never set up a domain controller being a router with two nics. ... from the DHCP server. ...
    (microsoft.public.win2000.networking)

Loading