Windows 2000 Server ->Windows 2003 migration

Hi,

What is the simplest way to migrate a Windows 2000 Server to a Windows
2003 Server? User, policy, etc need to be preserved after migration.
Can I migrate using ADMTv2 if the domain name is the same? Or is there
any more simple way?

Thanks.

Hi,

Is this server domain controller? Will you also replace the hardware?

If yes to both questions, there is more simple way. Add Windows 2003 server
to existing Windows 2000 domain. Prepair Windows 2000 domain for new Windows
2003 domain controller by running ADPrep /forestprep and ADPrep /domainprep
on Windows 2000 DC, but for this part you will need Windows Server 2003
installation CD. You only have to do this once (only for the first Windows
Server 2003 DC).
Once this is done, run dcpromo on Windows 2003 and it will be promoted to
domain controller. All policies, users etc, will be replicated between both
servers.

If you want to remove the old server now, you will have to:
- make new server a global catalog (GC)
- make sure that DNS is replicated to the new server
- move FSMO roles to the new server
- update clients with e.g. new IP address for DNS server

--
Mike
Microsoft MVP - Windows Security

"ping" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) oups.com...
> Hi,
>
> What is the simplest way to migrate a Windows 2000 Server to a Windows
> 2003 Server? User, policy, etc need to be preserved after migration.
> Can I migrate using ADMTv2 if the domain name is the same? Or is there
> any more simple way?
>
> Thanks.
>

Hi,

Thanks for your valueble reply.

How do I make sure DNS is replicated to new server? The old server will
be demoted to standalone server. Is it allright if I change the IP of
new Windows 2003 server as well as the DNS server service on it to the
IP of old server. If I do so, do I need to change the DNS entries of
each client? Is there specific settings need to be changed in Win2k03
client? I am quite a newbie here.

Thanks.

Hi,

Best way to replicate DNS is to use Active Directory Integrated zone. You
set this on DNS MMC if you right click your zone -- there you have a choice
to set it to AD Integrated. This way it comes part of AD replication.

Yes, you can change the IP address of the server. First give your old DNS
server new IP address and don't forget to change preferred DNS settings on
the server. Point it back to itself -- to its new IP address. Restart
NetLogon service.
Now change the IP address on your new Windows 2003 Server to IP address of
your old server. Again pay attention to preferred DNS settings on new
server. You can either point it back to itself (its real IP number) or
loop-back address -- that is 127.0.0.1. Once you make this change restart
NetLogon service and check that everything works (e.g. restart one of the
clients and try to logon...). Check Event logs for and errors...

--
Mike
Microsoft MVP - Windows Security

"ping" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) oups.com...
> Hi,
>
> Thanks for your valueble reply.
>
> How do I make sure DNS is replicated to new server? The old server will
> be demoted to standalone server. Is it allright if I change the IP of
> new Windows 2003 server as well as the DNS server service on it to the
> IP of old server. If I do so, do I need to change the DNS entries of
> each client? Is there specific settings need to be changed in Win2k03
> client? I am quite a newbie here.
>
> Thanks.
>