NT 4.0 to Win 2003, EXCH 5.5 to 2003 in a Netware environment...

Discussion in 'Server Migration' started by RMani, Aug 3, 2004.

  1. RMani

    RMani Guest

    I am planning to upgrade Exchange 5.5 to Exchange 2003.

    Current setup:

    The File and authentication server is a NetWare 6 server.
    All user documents (files and folders) are stored on the
    NetWare server. There is a Windows NT Server 4.0 Primary
    Domain Controller and one Backup Domain Controller, which
    is also the EXchange 5.5 Server.There is only one Domain
    and one Exchange Site in our organization.

    There are about 100 Client workstations running either
    Windows 2000 Professional SP4 or Windows XP Professional
    SP1 with Novell Client installed. Outlook 2003 is the e-
    mail client on all workstations.

    There are a few database servers that are configured as
    member servers running Windows NT Server 4.0 or Windows
    2000 Server that are part of the NT domain.

    IPX/SPX and TCP/IP are the protocols used in our network.

    There are roughly, 150 user accounts and an equal number
    of mailboxes on the Exchange 5.5 server. There is a DNS
    server in place and IP addresses are being assigned
    manually to all the hosts on the network.

    There is just one NDS partition on the NetWare server. NDS
    for NT is installed on the Domain controllers so user
    account information is synchronized between NDS and the NT
    Domain. Users authenticate with the NDS tree for File and
    Print Services and the NT domain for their mailbox access.
    Password Synchronization is enabled.

    Desired Setup:

    Since the NetWare server is currently used only for File
    and Print services, and given the fact that our messaging
    system is Microsoft's Exchange, I want to move away from
    the present mixed environment (NetWare + Windows NT) to a
    rather homogenous Windows NT environment.

    I want to upgrade Exchange 5.5 to Exchange 2003. I
    understand one of the important prerequisites is that an
    Active Directory domain environment be present to achieve
    this. That means I upgrade Windows NT 4.0 domain to either
    Windows 2000 or Windows 2003 Active Directory. I want to
    upgrade to Windows 2003. I want Windows 2003 to be the
    File and authentication server as well.


    What is the best approach to deal with this rather complex

    Can I move the Windows NT 4.0 domain to Windows 2003 AD
    domain first, upgrade Exchange 5.5 to Exchange 2003 next
    and THEN migrate NetWare 6 to Windows 2003?

    If I where to do the above, what is required so that
    NetWare 6 and Windows 2003 can co-exist?

    Is it realistic to do all of this in one shot, over a

    I do plan to create a test environment to simulate the
    current setup and test the upgrade and migration before I
    do it on the live environment.

    Has anyone done a similar migration?

    Can you please share your thoughts, experiences and ideas?

    Thank you all in advance.

    RMani, Aug 3, 2004
    1. Advertisements

  2. Hi RMani,

    Thanks for your posting here.

    I would like to suggest that you upgrade the NT 4.0 domain/Exchange 5.5 to
    Windows 2003 AD with Exchange 2003 first, then migrate from NetWare to
    Windows 2003 AD.

    You can try Microsoft? Directory Synchronization Services (MSDSS) to
    synchronize AD with NDS.

    MSDSS Technical Overview

    MSDSS Deployment: Implementing Synchronization and Migration

    In addition, there are some documents for the Service for NetWare (SFN)
    includes the information about migrating NetWare NDS :

    Microsoft Windows Services for NetWare 5.03

    NetWare to Windows Server 2003 Migration Planning Guide

    274279 How to Migrate or Deploy a Novell NetWare Environment to Windows

    For a complete solution on this kind of issue, 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:


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


    Hope this helps.

    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 4, 2004
    1. Advertisements

  3. Hello RMani,

    this is a fairly complex endevour you are planning for and I'm interested in
    whether the documentation that you were referred to is helpful or not. We
    are in the midst of updating some of this technical guidance and would
    appreciate your feedback on what's currently available to assist you with
    this migration. Please feel free to email me direclty at

    Tom Ford [MSFT], Aug 10, 2004
    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.