NT 4.0 to Windows 2003

Discussion in 'Server Migration' started by specialk, Aug 5, 2004.

  1. specialk

    specialk Guest

    I have a large school district network. I have currently and Nt 4.0 Network - 1 PDC (doing WINS/DHCP/PRINTERs/File Sharing), and 2 BDC's (FILE/Print Sharing). And via Fiber Channels - 9 BDC's At every school doing DHCP/FILE/PRINTERs.

    I recently setup a dummy BDC. I will promote that to PDC and Upgrade that to Windows 2003. After that I will install 2 new windows 2k3 servers (at the main location) and start transfering roles/data and unplugging the old systems. Eventually getting to each school and replacing those 9 with 9 new Windows 2003 Servers.

    ~~~~
    My questions are.

    1. During the first upgraded BDC - and I install Active Directory. I want to keep my Domain name. "abc". What do I have to do during the "New Domain Name Wizard Page" and it wants me to enter a FULL DNS name for the "new domain". I want to have zero downtime/ be able to keep in contact with all BDC's/ have the same name, etc. I want to keep both Microsoft, DNS, BDC's and my users happy.

    2. Can I bring back after the upgrade- an unplugged BDC Server (That I will unplugg during the upgrade for recovery purposes)? Will it just be able to go on the domain with no problems? ( I.E the Upgrade to the PDC - How does that effect the BDC's)

    3. What Should I do in the "big picture" as far as the 9 Domain Controllers over Fiber - in regards to DNS Servers (they will all be running DNS Servers for they will be DC's) - How should I handle the load - as far as sync/Primary DNS/Secondary/Forward/Reverse - etc.

    4. What about the load with the Global Catalog Server?

    5. I have a couple of Windows 2000 Member servers acting as Print Servers. Since I plan to get rid of these (eventually) I can still choose the Windows Server 2003 interim forest functional level - correct?

    6. Finally I believe I read this somewhere else(but just to make sure) - I can upgrade the domain to Windows2003 and as long as I leave the old servers up I will be fine as far as home directorys and scripts until I move those things over?

    Thanks to everyone who took the time to read it - especially those who helped...
     
    specialk, Aug 5, 2004
    #1
    1. Advertisements

  2. specialk

    specialk Guest

    I have found out that for my question #1.

    "1. During the first upgraded BDC - and I install Active Directory. I want to keep my Domain name. "abc". What do I have to do during the "New Domain Name Wizard Page" and it wants me to enter a FULL DNS name for the "new domain". I want to have zero downtime/ be able to keep in contact with all BDC's/ have the same name, etc. I want to keep both Microsoft, DNS, BDC's and my users happy."

    I will leave "abc" as the net bios name - and I can then create a new FQDN. And everything should still work is this correct?
     
    specialk, Aug 5, 2004
    #2
    1. Advertisements

  3. Hello,

    Thanks for your posting here.

    First, I would like recommend that you add NT4Emulator registry on the
    Windows NT 4.0 PDC before it is upgraded to Windows 2003. It will make your
    whole network works like before and we can remove the registry after all
    the BDC are upgraded to Windows 2003. Please refer to the following
    documents for the detailed information.

    Windows 2000-Based Clients Connect Only to the Domain Controller That
    http://support.microsoft.com/default.aspx?scid=kb;en-us;284937

    How to Prevent Overloading on the First Domain Controller During Domain
    http://support.microsoft.com/?id=298713

    As for your questions:

    1. Yes, you are right. There is no conflict between domain DNS name and
    NETBIOS name.

    2. You can rollback after upgrade. You can take the backup BDC online then
    promote to be PDC. It will not affect other BDCs and clients in the domain
    if you have set the NT4Emulator registry.

    3. You can upgrade these BDCs one by one. In Windows 2003, you can install
    AD-integrated Zone and the DC to itself. It will not cause too much network
    traffic. In addition, you can also create remote sites for these schools.
    Here is very useful document.

    244368 How to Optimize Active Directory Replication in a Large Network
    http://support.microsoft.com/?id=244368

    4. It is recommend that you put one GC in one site. You can also refer to
    the article of 244368.

    5. Domain and Forest Functional Levels only affect the DCs. It will not
    affect the member server. For more information about Windows 2003 domain
    and forest function levels, please refer to the following documents.

    322692 HOW TO: Raise Domain and Forest Functional Levels in Windows Server
    2003
    http://support.microsoft.com/?id=322692

    6. The users will keep their home folder. As for the logon script, logon
    scripts are put in the following location on the Windows 2000/2003 domain
    controller by default:

    %SystemRoot%\SYSVOL\sysvol\<DOMAIN>\Policies\<GUID>\USER\Scripts\Logon

    If the clients are Windows 2000/XP, you can assign the script by domain
    level Group Policy in Active Directory Users and Computers.

    We cannot use Group Policy for NT4 clients. So if you have any Windows NT
    clients, we have to enter the name of the logon script into the Profile tab
    in the properties for each user account and place the logon script in the
    NETLOGON share.

    %SystemRoot%\sysvol\sysvol\<domain DNS name>\scripts

    You can also refer to the following articles:

    322241 How to assign scripts in Windows 2000
    http://support.microsoft.com/?id=322241

    198642 Overview of Logon, Logoff, Startup, and Shutdown Scripts in Windows
    2000
    http://support.microsoft.com/?id=198642

    321707 HOW TO: Automatically Run Programs When Users Log On to Windows 2000
    http://support.microsoft.com/?id=321707

    At last, for such a complete solution on this kind of migration project,
    please feel free to consult with our MCS group (Microsoft Consultancy
    Services) who provide support and consultancy services for such issues that
    are unique to a customer's environment. More information can also be found
    at:

    http://www.microsoft.com/business/services/mcs.asp/

    Please use the link below to Reach MCS in the U.S: Contact a Microsoft
    District Office:

    http://www.microsoft.com/usa/offices/

    Hope this helps.

    Regards,
    Bob Qin
    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.
     
    Bob Qin [MSFT], Aug 6, 2004
    #3
  4. specialk

    specialk Guest

    Thanks for Responding.

    I thought that the NTEmulator would only be used if there where a lot of
    Windows 2000/XP Clients? To help with the load.

    There are; but during the migration process they will not be loging on until
    all the data has been transfered and all BDC's replaced.

    <In case you still recommend I do this: I add the registry to the NT 4.0
    PDC, prior to the upgrade>

    Is there and easy way to migrate large amounts of data (home directorys),
    with Permissions/shares/rights/etc. I want to keep everything in tact just
    transplant it to a new Server.

    Thanks
    Keith
     
    specialk, Aug 6, 2004
    #4
  5. Hi Keith,

    If you will upgrade all the BDCs to Windows Server 2003 before clients
    logon, then you do not need the registry.

    To more the shared resources to a new server with permissions, you can try
    robocopy.exe with the "/SEC" switch, or try the File Server Migration
    Toolkit.

    http://www.microsoft.com/windowsserver2003/upgrading/nt4/tooldocs/msfsc.mspx

    Have a nice day!

    Regards,
    Bob Qin
    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.
     
    Bob Qin [MSFT], Aug 9, 2004
    #5
  6. Hi There,

    My answers are inline.

    --
    --
    Brian Desmond
    Windows Server MVP
    12.il.us

    Http://www.briandesmond.com
    to Windows 2003. After that I will install 2 new windows 2k3 servers (at the
    main location) and start transfering roles/data and unplugging the old
    systems. Eventually getting to each school and replacing those 9 with 9 new
    Windows 2003 Servers.
    to keep my Domain name. "abc". What do I have to do during the "New Domain
    Name Wizard Page" and it wants me to enter a FULL DNS name for the "new
    domain". I want to have zero downtime/ be able to keep in contact with all
    BDC's/ have the same name, etc. I want to keep both Microsoft, DNS, BDC's
    and my users happy.
    You can and should (must to support the BDCs) leave the NETBios name as-is.
    The DNS name, if you have a namespace for your school (like Chicago Public
    Schools is cps.k12.il.us), I would recommend setting something in that
    namespace - e.g. netbiosnamehere.cps.k12.il.us. You'll need to make sure
    this is sealed off from your public DNS. If you don't have a k12.il.us
    namespace, just do whateveryouwanthere.local - whateveryouwant might be the
    netbios name.
    will unplugg during the upgrade for recovery purposes)? Will it just be able
    to go on the domain with no problems? ( I.E the Upgrade to the PDC - How
    does that effect the BDC's)
    Controllers over Fiber - in regards to DNS Servers (they will all be running
    DNS Servers for they will be DC's) - How should I handle the load - as far
    as sync/Primary DNS/Secondary/Forward/Reverse - etc.

    They don't all ahve to run DNs but it would make sense for them to. Setup
    DHCP such that at each site, the local DC is primary DNS, and one of your
    central office DCs is secondary DNS. The reverse zones can just be stored in
    AD as well and will be replicated with the fwd zone. Everything in that
    neighborhood is automatic - replicates with AD.
    Since you only have one domain, just make all the DCs GCs, as there is no
    additional GC data to replicate. If you're going to have multiple domains,
    it's a different story.
    Since I plan to get rid of these (eventually) I can still choose the Windows
    Server 2003 interim forest functional level - correct?

    Yes. You can have member servers running any version of Windows you want in
    a 2003 Native/Interim/Whatever domain. The functional level pertains ONLY to
    the operating system of the domain controllers.
    can upgrade the domain to Windows2003 and as long as I leave the old servers
    up I will be fine as far as home directorys and scripts until I move those
    things over?
     
    Brian Desmond [MVP], Aug 11, 2004
    #6
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.