New DC, DNS, DHCP & WINS Server

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

larrabee.john@hol-mac.com - 27 Jun 2007 21:03 GMT

I have a DC (W2k3) that is also our DNS, DHCP, WINS & DATA Server. We
will call "Old DC"
I am Building A New Server to be the DC, DHCP & Wins. Leaving the Data
Server in Service. We will cal it "New DC". Most of our PC's are
Static IP's, but we do have some Laptop that are DHCP. OLD DC's ip is
10.1.1.171. I would prefer to keep using this ip for my New DC,
because of DNS, DHCP & WINS. What step should i take to minimize the
smallest amount of downtime?
Thanks in advance for you help.

PS. I understand what steps to take if it was just a new DC, But the
DNS, DHCP & WINS, I'm not sure about:

For DC
1. Install OS on the new Server. - DONE!
2. Promote the new Server to DC.
3. Transfer FSMO from old DC to new DC.
4. Demote old DC.

Thanks all

Reply to this Message

Kevin D. Goodknecht Sr. [MVP] - 28 Jun 2007 14:24 GMT

Read inline please.

In news:1182974627.177901.312880@q75g2000hsh.googlegroups.com,
larrabee.john@hol-mac.com <larrabee.john@hol-mac.com> typed:

> I have a DC (W2k3) that is also our DNS, DHCP, WINS & DATA Server. We
> will call "Old DC"
[quoted text clipped - 16 lines]
>
> Thanks all

These are the basic steps it's not quite that simple. Make sure you make the
new DC a Global Catalog, if the current DC has ADI zones, they will
replicate automatically to the new DC if the DNS service is installed. Do
not point the new DC to itself for DNS until the zones have replicated.
After you swap Server IPs, run netdiag /fix and dcdiag /fix

For DHCP, use this article to move DHCP to the new server:
How to move a DHCP database from a computer that is running Windows NT
Server 4.0, Windows 2000, or Windows Server 2003 to a computer that is
running Windows Server 2003: http://support.microsoft.com/kb/325473/en-us

For WINS, install WINS on the new server and point it to itself only, set
them up as replication partners, after you demote and remove the other
server from the network, select all WINS records on the new server, delete
the records and choose replicate deletion to other WINS servers, which
forces the new server to take ownership of the records.

Demote the old DC and remove it from the domain before powering it off.

It would really be recommended to keep the other DC, if you only have one
DC. At least two DCs/DNS/WINS servers are recommended.

Signature

Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This Helps

===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
http://message.wftx.us/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================

Reply to this Message

larrabee.john@hol-mac.com - 29 Jun 2007 15:35 GMT

On Jun 28, 8:24 am, "Kevin D. Goodknecht Sr. [MVP]"
<a...@nospam.WFTX.US> wrote:

> Read inline please.
>
[quoted text clipped - 64 lines]
>
> - Show quoted text -

Kevin, Thank you.
The old DC is also a Data Server for users so it will not be going
away. We have 2 more Domains(Different) in this network. I am
considering setting up a secondary Domain on another system, just not
the data server. Again Thanks for your Help

Reply to this Message