Windows Server

Guest

Hi,
I have a simple (one server) WIN2K network with 15 workstations.
The DC server manages DNS and DHCP. AD is installed on the server.
I want to move everything to a new Win2K3 machine, and remove the Win2K
machine.

I have researched and followed all the steps for this type of
migration, including moving the FMSO roles to the new server. Both DC
are in the AD now, and all is OK to this point.

I would like to know what is the best way to move the DNS and DHCP
roles? Do I have to re-enter the DNS information manually on the new
server ?

As far as DHCP goes, I found a detailed step-by-step on moving the DHCP
database, but I am wondering about the actual steps on each server.
Any input would be appreciated,

Thank you,

Frank

Frank · Guest

Update...
I have checked the properties of the msjfb2000.local (that's the name)
zone, and it says <AD Integrated> for both servers.
So if this means that they are synched, what are the steps to pull the
w2k DNS role off-line, so I can continue <tearing it down>?
Next step will be moving DHCP, then Exchange...

Frank

Frances [MSFT] · Guest

Hello Frank,

Good to hear from you.

According to your message, I assume your main concern is the best way to
move DNS and DHCP.

Do you have an AD-integrated zone in the target win2k3 domain now? What is
the zone in your source win2k domain? Is it AD-integrated?

We have several methods to seamlessly migrate DNS zones from a Windows 2000
server to Windows Server 2003.

If the source DNS zones are AD-integrated, we can setup the AD-Integrated
DNS zones on the new server directly as these zones have been synchronized
via AD replication. If you manually add some information in the source DNS
zone, which you need to have in your target DNS zone, you can create a
secondary zone on the win2003 domain for the zone on the win2000 DNS server
to replicate those information.

If the source DNS zones are primary, use either methods below:

Method 1. Zone Transfer:
==================

1.1) Create a secondary zone on the Windows Server 2003 system for the zone
on the existing 2000 DNS server.

1.2) Transfer the zone over to the Windows Server 2003 system

1.3) Change the secondary zone on the Windows Server 2003 system to a
Standard Primary Zone

Method 2. Copy the DNS zone file from the current DNS server:
============================================

2.1) Copy the DNS zone file (*.dns) from form the Windows 2000 DNS server
in the following location:

%SystemRoot%\system32\DNS

2.2) Put the *.dns file in the %SystemRoot%\system32\DNS folder on the
Windows Server 2003 system

2.3) Try to create a new primary zone by using the wizard. When you are
asked if you want to crate a new zone file, please select the radio box
"Use this existing file" and specify the file name.

More information can be accessed at the following link:

814591 HOW TO: Install and Configure DNS Server in Windows Server 2003
http://support.microsoft.com/?id=814591

As for DHCP, do you find the article below? As I have followed the steps in
this article to move DHCP database from win2k to win2k3 and it works
greatly.

The snippet "Export the DHCP database from a server that is running Windows
NT Server 4.0 or Windows 2000" addressed how to export:

The snippet "Import the DHCP database" addressed how to import:

325473 HOW TO: Move a DHCP Database from Windows NT 4.0 Server to Windows
Server 2003
http://support.microsoft.com/?id=325473

Hope this helps. If you have any further questions don't hesitate to get in
touch!

Best regards,

Frances He

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

=====================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Frank · Guest

Good morning Frances,

Thank you for your response. Let's tackle DNS first.
I am not sure I understand what you mean by <Do you have an
AD-integrated zone in the target win2k3 domain now>.
I have DNS role installed but NOT CONFIGURED on the new w2k3 machine.
If I start DNS manager (on either old or new machine), I can see both
servers, and the information is identical for both (Forward and reverse
folders are there).

This is a simple network, and I have a forwader (to my ISP's DNS)
defined on my w2k machine for external address resolution. This is what
I want to transfer to the new machine.

If I launch <configure DNS> on the new machine, it asks me if I want to
create zones... I can also launch directly <create zone> from the menu,
which is what you seem to propose. Should I configure DNS first, and if
so, do I tell it to create the zones (there is an option to NOT create
the zones...)

It would appear that some kind of integration has happenned, since I
can see both servers from the DNS manager. One thing appears certain,
it is that I have to configure DNS on the new server.

Thanks for your help,

Frank

Frances [MSFT] wrote:

	Windows Server Forum Index -> Migration	All times are GMT
Page 1 of 1