RE: w2k to win 2003 servers

From: Frances [MSFT] (v-franhe_at_microsoft.com)
Date: 03/01/05 

Date: Tue, 01 Mar 2005 11:59:11 GMT

Hello Linda,

Good to hear from you.

According to your post, I understand your goal is to move FSMO roles, DHCP,
Wins, and user folders to the new 2003 server and leave the win2k server as
Exchange 2000 server and DNS server. Is this correct?

I suggest that you move GC and FSMO roles first. Then move DHCP, Wins and
so on. It is best to let the win2k3 server be the DNS server and resolve
the domain FQDN. Why do you want the win2k server to be the DNS server?

Please follow the steps below to achieve your goal.

1. Install AD-integrated DNS on 2k3, this process will auto replicate DNS
from 2k to 2k3.
If you want the win2k3 DNS server to resolve the domain FQDN, you can
change the clients to point to win2k3 server for their preferred DNS
server. Also change the win2k server to point to win2k3 server. On the
win2k3 server, point it to itself.

2. Move Global Catalog to win2k3 server.

Refer to the following article.
816105 HOW TO: Create or Move a Global Catalog in Windows Server 2003
http://support.microsoft.com/?id=816105

3. Switch FSMO Roles to win2k3 server.

Refer to the following article.
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

4. Move DHCP to win2k3 server.

Refer to the following KB:
130642 How to Move a DHCP Database to Another Windows Server
http://support.microsoft.com/?id=130642

5. WINS Migration
WINS migration is simple too. Generally we can use the following methods:

193820 How to Move a WINS Database to Another Server
http://support.microsoft.com/?id=193820

6. No need to migrate users.
When you promote the win2k3 server to be a DC, the user information is
automatically imported to the win2k3 server.

7. Move file server from win2k to win2k3.
I understand you want to migrate the files on win2k to win2k3. Is this
correct?

If this is the case, you can use the following two methods:

7.1 robocopy
Use robocopy to copy the files with NTFS permissions. Please use
robocopy.exe with the "/SEC" switch to copy the folders with their NTFS
permissions.

RoboCopy Syntax
http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/techre
f/en-us/Default.asp?url=/Resources/Documentation/windowsserv/2003/all/techre
f/en-us/robocopy_syntax.asp

7.2 FSMT

The following articles are for your reference.

Microsoft File Server Migration Toolkit
http://www.microsoft.com/windowsserver2003/upgrading/nt4/tooldocs/msfsc.mspx

Overview of the Microsoft File Server Migration Toolkit
http://www.microsoft.com/windowsserver2003/upgrading/nt4/tooldocs/msfst_over
view.mspx

Frequently Asked Questions About File Server Migration
http://www.microsoft.com/windowsserver2003/upgrading/nt4/tooldocs/msfst_faqs
.mspx

As for authentication, there is no need to set the clients authenticate
with the win2k3 DC. If you do want to do so, you can create another site,
and a subnet, and then associate the subnet with the site. Then put the
win2k3 server and all the clients into the subnet. The clients will by
default authenticate with the DC in the same site.

Refer to the following article for more details.

Designing and Deploying Directory and Security Services
http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/deploy
guide/en-us/Default.asp?url=/resources/documentation/windowsserv/2003/all/de
ployguide/en-us/dssbd_topo_wbyg.asp

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.

Relevant Pages

  • Re: Domain Controller Issue - Urgent Help
    ... On the running DC check with dcdiag and netdiag for errors first. ... DNS server as well. ... FSMO roles and is the Global Catalog as well. ...
    (microsoft.public.win2000.active_directory)
  • Re: Domain Controller Issue - Urgent Help
    ... DNS server as well. ... The other machines that are the new hardware I was trying ... FSMO roles and is the Global Catalog as well. ...
    (microsoft.public.win2000.active_directory)
  • Re: Adding a win2003 DC to win2k forest
    ... Thanks for those links and it looks pretty easy to move the FSMO roles. ... our primary AD server. ... clients will not be able to find any domain controller. ... > Another thing to consider is IP address for preferred DNS server. ...
    (microsoft.public.windows.server.general)
  • Re: Adding a win2003 DC to win2k forest
    ... Thanks for those links and it looks pretty easy to move the FSMO roles. ... our primary AD server. ... clients will not be able to find any domain controller. ... > Another thing to consider is IP address for preferred DNS server. ...
    (microsoft.public.windows.server.general)
  • Re: Adding a win2003 DC to win2k forest
    ... Thanks for those links and it looks pretty easy to move the FSMO roles. ... our primary AD server. ... clients will not be able to find any domain controller. ... > Another thing to consider is IP address for preferred DNS server. ...
    (microsoft.public.windows.server.general)