Migrating to 2003 Server

Ok here is my scenario. We currently have 2 Windows 2000 Server DC's. One
acts as our File Server, DHCP, DNS & WINS. The other is our Exchange 2000
server. We recently bought a new server with Windows 2003 and I would like
to start migrating the AD & file portion to the 2003 server. I dont plan on
demoting the older 2000 DC's because one will still act as the DHCP, WINS &
DNS server and the other I am waiting until I receive a new 2003 server for
Exchange 2003. What is the best scenario to get this done that will have the
least amount of impact on the user.

Steve

Hi Steve,

Microsoft has a good step-by-step guide on how to upgrade Windows 2000 to
Windows 2003 domain.

Upgrading Windows 2000 Domains to Windows Server 2003 Domains
http://www.microsoft.com/resources/d...n_overview.asp

In general, you have to prepare the forest and domain (adprep /forestprep
and adprep /domainprep) and then run a dcpromo on your new Windows 2003
server.

Pay specialy attention to this part of the guide...
Windows Server 2003 adprep /forestprep Command Causes Mangled Attributes in
Windows 2000 Forests That Contain Exchange 2000 Servers
http://support.microsoft.com/kb/314649

Before you remove Windows 2000 domain controller make sure that you move all
FSMO roles and global catalog to any new domain controller.

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

How to view and transfer FSMO roles in Windows Server 2003
http://support.microsoft.com/?id=324801

How To Create or Move a Global Catalog in Windows 2000
http://support.microsoft.com/?kbid=313994

To move file information I usually do a backup of all files using ntbackup.
After the backup is done, I transfer *.bkf file to the new server and I do a
restore.
The reason for this is that ntbackup restore procedure will also restore
NTFS permissions. Depending on number of shares created, you can also export
all share information (with permissions) and import them back on new server
(these information is stored in the registry).

Migrating DNS, DHCP and WINS should not be a problem -- if you wish to move
these services.
My recommendation is, that new server is also DNS server. Since you use DHCP
it should not be a problem to reconfigure the clients (IP of new DNS and
WINS server).

I hope this helps,

--
Mike
Microsoft MVP - Windows Security

"Steve" <(E-Mail Removed)> wrote in message
news:C09B3B7C-C2E3-4F91-A098-(E-Mail Removed)...
> Ok here is my scenario. We currently have 2 Windows 2000 Server DC's.
> One
> acts as our File Server, DHCP, DNS & WINS. The other is our Exchange 2000
> server. We recently bought a new server with Windows 2003 and I would
> like
> to start migrating the AD & file portion to the 2003 server. I dont plan
> on
> demoting the older 2000 DC's because one will still act as the DHCP, WINS
> &
> DNS server and the other I am waiting until I receive a new 2003 server
> for
> Exchange 2003. What is the best scenario to get this done that will have
> the
> least amount of impact on the user.
>
> Steve
>