Windows Server

ilebovits · Guest

Hi,

I currently have a Windows 2000 Server witch is the only Server on my
network. It's used for file and print sharing, some security, and Terminal
Services. I got a Dell Power Edge 2800 Server with Windows 2003 Server on
it. We have only 15 computers on the network.

Please let me know the EZ way to do this migration, basically we need to
transfer only the Domain Name and the Server Name (if possible) and Data.

Also how should we go about the configuring the Workstations.

Thanks,

Izzy

Jeff Qiu [MSFT] · Guest

Hi ilebovits,

Thanks for posting here.

Based on your description, I have provided the following three plans for
your reference:

(Note: Regarding TS server, I will mention it at the end.)

[Plan I]
==========

0. Fully backup your old win2k server.
1. Join the new win2k3 server to the domain (this will be a little bit
complex since win2k3 server is put in, a forest prepare and domain prepare
is needed).
325379 How to upgrade Windows 2000 domain controllers to Windows Server 2003
http://support.microsoft.com/?id=325379

2. Move all FSMO roles from the old server to the new server.
324801 How To View and Transfer FSMO Roles in Windows Server 2003
http://support.microsoft.com/?id=324801
255504 Using Ntdsutil.exe to seize or transfer FSMO roles to a domain
controller
http://support.microsoft.com/?id=255504

3. Copy all file share from the old server to the new server by robocopy.
4. Reinstall all the printers on the new server.
5. Take the old server offline to test to make sure every client works fine.
6. Demote the old server (optional).

Good points:
------------
This plan will keep the clients untouched during the whole process.
The domain name is unchanged. Just invited a new DC.

Shortcomings:
-------------
The new DC is not using the old name. Thus, the old file share are using
the new server's host name.
The step 1/2 is a little bit complex.

[Plan II]
==========

1. Connect the new server to the network.
2. Copy all file shares without permission settings from the old server to
the new server.
3. Disconnect the new win2k3 server from the network.
4. Rename the server to the same name of the original server.
5. DCPROMO it to the same domain name.
6. Create the users needed.
7. Configure the permission for the file share according to the same
structure to the old server.
8. Reinstall the network printers.
9. Log off all clients and take the old DC offline.
10. Let all the client leave the original domain to a temp workgroup and
then join the new domain.

Good points:
------------
This is a clean installation plan.
It will provide a very clean environment.
The domain name is unchanged.
The DC name is unchanged.
All the file share UNC name should be unchanged.
The original DC and domain is left untouched. If you want, a restore is
very easy.

Shortcomings:
-------------
Steps are a little complex.
Needs to rejoin the clients one by one. (As we only have 15 machines, it
should be fine.)
Needs to reconfigure the permissions.

[Plan III]
==========

1. Clean install the new Windows Server 2003 to a Windows 2000 Server.
2. Use Ntbackup to backup restore the old win2k server to the new win2k
server.
249694 How to move a Windows 2000 installation to different hardware
http://support.microsoft.com/?id=249694
3. Upgrade the Win2k server to Windows Server 2003.

Good points:
------------
This process is simple.
All the original settings are inherited.

Shortcomings:
-------------
NTbackup is not recommended for DC while move to different hardware. There
are potential problems.

Regarding the TS server
=========================
Since the license mode for Windows Server 2003 Terminal Server requires all
the clients to gain a CAL, you may consider it before move to the new
Windows Server 2003 TS. At the same time, put the file server and terminal
server on the same machine is really a bad idea. We suggest put these two
roles on two servers. For example, here we put the file server role on the
new server and keep the TS on the old server.

Summary of Related KB articles:
==================================
-Update/Join win2k server to win2k domain:
325379 How to upgrade Windows 2000 domain controllers to Windows Server 2003
http://support.microsoft.com/?id=325379

-Move FSMO roles:
324801 How To View and Transfer FSMO Roles in Windows Server 2003
http://support.microsoft.com/?id=324801

255504 Using Ntdsutil.exe to seize or transfer FSMO roles to a domain
controller
http://support.microsoft.com/?id=255504

-Move win2k installation to different hardware:
249694 How to move a Windows 2000 installation to different hardware
http://support.microsoft.com/?id=249694

If there is anything else unclear, please feel free to post back.

Hope it helps!

Best Regards,

Jeff Qiu
Microsoft Online Partner Support
MCSE 2k/2k3, MCSA 2k/2k3, MCDBA
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.

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

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