Re: Reinstall DC
Hi!
Well, you will need another server which will retain AD and FSMO roles while
you reinstall this server.
Pls, see here for transferring FSMO roles:
http://www.petri.co.il/transferring_fsmo_roles.htm
The recommended process is as follows
Install Windows 2003 on the new machine
Assign the new computer a new name, IP address and subnet mask on the
existing network
Make sure that the preferred DNS server on new machine points to the
existing DNS Server on the Domain (normally the existing domain controller)
Join the new machine to the existing domain as a member server
From the command line promote the new machine to a domain controller with
the DCPROMO command from the command line Select Additional Domain
Controller in an existing Domain
Once Active Directory is installed then install DNS. You can do this through
Add/Remove Programs->Windows Components->Networking Services->DNS. If you
are using Active Directory Integrated DNS then DNS will br replicated from
the other DC/DNS.
Next make the new machine a global catalog server, go to Administrative
Tools, Active Directory Sites and Services, Expand, Sites, Default first
site and Servers. Right click on the new server and select properties and
tick the Global Catalog checkbox. (Global catalog is essential for logon
as it needs to be queried to establish Universal Group Membership)
If necessary install DHCP on the new DC. You can do this through Add/Remove
Programs->Windows Components->Networking Services->DHCP.
You will then need to remove any existiing DHCP prior to authorising the new
DHCP Server. When setting up the new DHCP server dont forget to set the
default gateway (router) and DNS Servers. Talking of which all the clients
(and the domain controllers themselves) need to have their Preferred DNS
server set the new domain controller.
Transfer all the FSMO roles to the new DC: See
http://www.petri.co.il/transferring_fsmo_roles.htm
You can copy data from the old to the new machine (use robocopy or xcopy to
retain NTFS permissions), you will need to reshare any shares.
Both Domain Controllers by this point will have Active Directory, Global
Catalog, DNS and the domain could function for a while at least should any
one of them fail.
You can/should keep the old DC on line - it will provide redundancy should
the other server fail - better to to this than keep if off-line as you
suggest.
If you really want rid of the old DC then:-
Check that you have:-
Moved the FSMO roles
Made the other DC a global catalog:
Installed DHCP on the new DC, set up the scope and authorise it. (If using
DHCP)
Make sure that all clients use the new DC as their Preferred DNS server
(either by static or DHCP options)
Power down to old DC and make sure that all is well, once satisfied power on
the old DC again, then run DCPROMO for remove it's domain controller status.
This is essential to avoid replication errors
If you want to remove the machine from the domain then you can do so one
it's DC role has been removed
"Juan Garc?a" <XXnl144039YY@ZZgmail.com> ha scritto nel messaggio
news:OlMmdQ12IHA.4448@TK2MSFTNGP05.phx.gbl...
>I would like to format a server that is DC (with GC), reinstall the SO and
>I need set the same name to the new reinstalled server. What should I do??
> Thanks.-
>