Re: Domain Controller hardware replacement

Tech-Archive recommends: Fix windows errors by optimizing your registry

Hello drix77@xxxxxxxxx,

I would do it in this way:

- install the new servers as a member, configure IP addresses, point DNS to the running DNS server, add them to domain
- dcpromo the first with AD integrated DNS, make it GC
- dcpromo the second with AD integrated DNS, make it GC
- dcpromo the third

give it time for REPLICATION.

Move the FSMO roles to the new DC's:
2003
http://support.microsoft.com/kb/324801
2000
http://support.microsoft.com/default.aspx?scid=kb;en-us;255690

After moving the roles and also configuring DNS settings to the new DNS servers you can dcpromo the old serves and remove them from the domain.

If you really want to be sure, that everything works, stop DNS SERVER SERVICE on the old DC's. Check that everything works from your clients and servers like before.

Best regards

myweb
Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.



What would be the best practice for harware replacement for domain
controllers.

Currently have 3 DC's, 2 have dns.
Hardware is at end of lifecycle and we are replacing the hardware.
Scenario 1:
Demote 1, build new server and dcpromo with same name and IP.
Repeat for the 2 others.
Scenario 2:
Dcpromo 3 new servers with new names into domain, and then demote the
old ones.
Change IP's to match the old ones.
Scenario 3:
Use HP migration tool (P2P), very little documention on using this
with
DC's, anyone ever sucessfully used it?
I am leaning towards option 1 and keeping the same names and IP's,
just
to simplify and avoid having to change dns settings on every server.
I assume that all site links would have to be recreated, anything else
I am missing? Logon scripts etc should all be replicated to the new
boxes right?.
DNS and WINS should only be a matter of replicating between old and
new
servers.
DHCP just needs to be moved.
Thanks, just looking for confirmation that it will be this easy or
other opinions, would like to establish a proper procedure.
All I can find is info on 2k to 2k3 upgrades on MS and I would like to
avoid going the way of backup and restore.
Richard


.

Relevant Pages

  • Re: Help SMPT Errors
    ... FAIL Reverse DNS entries for MX records ERROR: The IP of one or more of your ... it may mean that your DNS servers did not respond fast enough). ... INFO NS records at parent servers Your NS records at the parent servers ... PASS Parent nameservers have your nameservers listed OK. ...
    (microsoft.public.exchange.admin)
  • Re: Windows 2000 logon process
    ... Paul Williams ... when clients are accessing the GPO stored in SYSVOL during logon. ... PW>> Sound's like - that's a combination of DNS and Dfs client pointing ... Global Catalogue servers? ...
    (microsoft.public.win2000.active_directory)
  • Re: Replication issues
    ... I wanted to say Zone Transfers not Zone Forwarding. ... on 2 servers out of 4 DNS servers. ... DNS and 2003 DNS and how to set up Conditional Forwarding. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Howto refresh IIS 6 Application pool identity credential info
    ... You already have 80% of the work setup (DNS Aliases and HostHeaders) on the ... domain accounts (one for each layer) should be sufficient. ... The Application Servers are load balanced clustered, ... as the account name and SPN alias is correctly defined on both nodes. ...
    (microsoft.public.inetserver.iis.security)
  • Re: new domain setup
    ... want to review the fesmo roles for the servers like infrastrure ... Another note, i would install DNS on the DC's before you run DCPROMO, ...
    (microsoft.public.windows.server.setup)