Jump to content

Replacing WIndows 2000 DC Server with New Server

Guest Benjamin Villanueva

By Guest Benjamin Villanueva
in Windows 2003 Server

 Share

Recommended Posts

Guest Benjamin Villanueva

Guest Benjamin Villanueva

Posted
Posted

Hi All,

 

We have Single DC running Windows 2000 Server. We are planning to replace it with new Server with the same OS and rename it as well as with new Domain Name.

 

Curently, we have 100 computers that are member of the domain. hope someone could give an advise for this without losing the current configurations. Preventing manually re-joining all clients.

 

any siggestion is appreciated.

thank you in advance!

  • Replies 4
  • Created
  • Last Reply

Popular Days

Popular Days

Guest Dusko Savatovic

Guest Dusko Savatovic

Posted
Posted

Re: Replacing WIndows 2000 DC Server with New Server

 

AFAIK Windows 2000 does not allow you to rename server name after it is

promoted to the DC and/or rename domain name. This feature requires at least

Windows Server 2003.

Special care should be taken if you use Exchange and/or use Certificate

Authority.

If you are concerned about consistent names of file shares, you can use

Enterprise DFS. This way all shares will point to your domain name

(\\yourdomain.tld\someshare).

 

You may procede as follows.

 

1. Install Win 2000 Server with new, prevoiosly unused name.

2. Promote server to DC in existing domain.

3. Transfer FSMO roles (schema master, domain naming master, RID master, PDC

emulator and Infrastructure master) to the new server.

4. Make the new DC a Global Catalog Server.

5. Install DNS service on the new DC and make it authoritative for your

Active Directory zones.

6. Install additional services to the new DC (e.g. DHCP and WINS).

Reconfigure clients to use the new server.

7. Optionaly, demote old server.

8. Optionaly, remove old server from the domain and erase any records about

that server from the DNS and AD (use ADSIEDIT).

 

 

 

"Benjamin Villanueva" wrote in message

news:2008823231426bvillanueva@greenhawk.com...

> Hi All,

>

> We have Single DC running Windows 2000 Server. We are planning to replace

> it with new Server with the same OS and rename it as well as with new

> Domain Name.

>

> Curently, we have 100 computers that are member of the domain. hope

> someone could give an advise for this without losing the current

> configurations. Preventing manually re-joining all clients.

>

> any siggestion is appreciated.

> thank you in advance!

Guest Meinolf Weber

Guest Meinolf Weber

Posted
Posted

Re: Replacing WIndows 2000 DC Server with New Server

 

Hello Benjamin,

 

You can not rename a 2000 DC without demoting and so loosing the domain configuration

in your case with only one DC.

 

!!!NEVER START BEFORE HAVING CREATED A BACKUP OF YOU DATA/MACHINE!!!

 

One question first:

Is the old server also Exchange server and will it be taken out of the domain

 

forever, when the new server is running?

 

- 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, dcdiag and netdiag on the old machine to check for errors,

if you have some post the complete output from the command here or solve

them first

 

- 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

 

- run dcpromo and follow the wizard to add the server to an existing domain

 

- if you are prompted for DNS configuration choose Yes (also possible that

no DNS preparation occur), then install DNS after the reboot

 

- 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 on both domain controllers

 

- if you have no errors, make the new server Global catalog server, open

Active directory Sites and Services and then double-click sitename, double-click

Servers, click your domain controller, right-click NTDS Settings, and then

click Properties, on the General tab, click to select the Global catalog

check box (http://support.microsoft.com/?id=313994)

 

- Transfer, NOT seize the 5 FSMO roles to the new Domain controller (http://support.microsoft.com/kb/255690)

 

- 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 according to this article

(http://support.microsoft.com/default.aspx?scid=kb;en-us;275278&id=kb;en-us;275278)

 

- if you use DHCP do not forget to reconfigure the scope settings to point

to the new installed DNS server

 

- export and import of DHCP database (if needed) http://support.microsoft.com/kb/325473

 

Demoting the old one if needed (BETTER HAVE MORE THEN ONE 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

 

 

 

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

 

> Hi All,

>

> We have Single DC running Windows 2000 Server. We are planning to

> replace it with new Server with the same OS and rename it as well as

> with new Domain Name.

>

> Curently, we have 100 computers that are member of the domain. hope

> someone could give an advise for this without losing the current

> configurations. Preventing manually re-joining all clients.

>

> any siggestion is appreciated.

> thank you in advance!

Guest greenh

Guest greenh

Posted
Posted

Re: Replacing WIndows 2000 DC Server with New Server

 

 

Thank you for all your reply.

 

To answer Meinolf, Its not using exchange and eventually be using to

other apps server(will Freshly installed).

 

Let me confirm my concern, we recently acquire a new domain name (.com)

and we are currently in the .net. This is one of the reason why we are

repalcing the current server in addition to add extra hp to the box.

 

Does renaming still be possible if the DN also be renamed? from .net to

.com?

 

or it is easier to go and upgrade to win2k3?

 

i really apprecite your helpful comment/suggestions.

 

thank again!

 

ben

 

 

--

greenh

------------------------------------------------------------------------

greenh's Profile: http://forums.techarena.in/members/greenh.htm

View this thread: http://forums.techarena.in/windows-server-help/1025931.htm

 

http://forums.techarena.in

Guest Dusko Savatovic

Guest Dusko Savatovic

Posted
Posted

Re: Replacing WIndows 2000 DC Server with New Server

 

Let me repeat,

Domain Rename is only possible with Windows Server 2003 and later, NOT

Windows Server 2000.

 

In my company, we have split DNS domain namespaces, outside domain is in

registered top level doman (TLD), the inside (Intranet domain) is

unregistered top level domain (examples .corp, .local etc).

 

Using the same TLD for both Intranet and Internet is accepted and supported,

but introduces the problem that you are currently experiencing. How you will

solve the problem depends on many factors, one of which is the size of your

company and number of resources (servers, workstations, services etc) and

also how you are satisfied with present design.

 

You shoud upgrade to Win2k3 and rename domain if:

a) you are satisfied with present design and do not consider maintaining two

domain namespaces (Intranet and Internet).

b) You don't have MSExchange

c) You do not have Certificate Authority

d) You do not use some other apps/services that are tied to the domain name.

 

HTH Dush

 

"greenh" <greenh.3erzba@DoNotSpam.com> wrote in message

news:greenh.3erzba@DoNotSpam.com...

>

> Thank you for all your reply.

>

> To answer Meinolf, Its not using exchange and eventually be using to

> other apps server(will Freshly installed).

>

> Let me confirm my concern, we recently acquire a new domain name (.com)

> and we are currently in the .net. This is one of the reason why we are

> repalcing the current server in addition to add extra hp to the box.

>

> Does renaming still be possible if the DN also be renamed? from .net to

> com?

>

> or it is easier to go and upgrade to win2k3?

>

> i really apprecite your helpful comment/suggestions.

>

> thank again!

>

> ben

>

>

> --

> greenh

> ------------------------------------------------------------------------

> greenh's Profile: http://forums.techarena.in/members/greenh.htm

> View this thread:

> http://forums.techarena.in/windows-server-help/1025931.htm

>

> http://forums.techarena.in

>

 Share
Go to topic listing
×
×
  • Create New...