RE: NT 4.0 to windwos 2003 network



Hello,

Thanks for your post.

I understand you want to know the following two questions and I will answer
them separately:

1. In the existing setup both site have their own set of users on their own
domain, I would like the setup with win2003 do I need to create multiple
and forests or one domain with two child domains.
Depends on your real environment, you only can use one forest, whether to
use two trees depends on your existing DNS. If you want to maintain the
original DNS name in these two companies, you need to use two trees.
Otherwise, you can use child/parent domains. If you want to use
maxis.com.my for two domains, you can use child/parent domain.
For the structure of tree and forest, please refer to the following article
and pay more attention to the figure 1.7:

Active Directory Logical Structure
http://www.microsoft.com/resources/documentation/Windows/2000/server/reskit/
en-us/Default.asp?url=/resources/documentation/windows/2000/server/reskit/en
-us/distrib/dsbb_act_uzlw.asp

2. What is the best way to migrate to win2003 and exchange 5.5 and we
prefer the migration to be in stages?

First, I want to know if you want to restructure Domain and forest and use
the new server machines. If so, we always use ADMT to migrate to Win2003.
If you want to keep the original structure, I think upgrade is a good
solution.

You need to established two way trust between Dom1 and new Dom3, Between
Dom2 and new Dom4, therefore, you only need to migrate Dom1 to Dom3 and
Dom2 to Dom4 to achieve the goal by using ADMT.

About how to migrate from NT to 2003 by using ADMT, please refer to:

Migrating from Windows NT Server 4.0 to Windows Server 2003
http://www.microsoft.com/downloads/details.aspx?FamilyID=e92cf6a0-76f0-4e25-
8de0-19544062a6e6&DisplayLang=en

Migrating from Windows NT Server 4.0 to Windows Server 2003
http://www.microsoft.com/seminar/shared/asp/view.asp?url=/Seminar/en/2003032
4TNT1-74/manifest.xml

You can download ADMT from the link below:
Windows 2000 Active Directory Migration Tool
http://www.microsoft.com/windows2000/downloads/tools/admt/default.asp

Active Directory Migration Tool Overview
http://www.microsoft.com/windows2000/techinfo/planning/activedirectory/admt.
asp

With regards to the Exchange migration, please post all Exchange related
question to microsoft.public.exchange so that the exchange expert can
provide more accurate information for you.

HTH!

Thanks & Regards

Amanda Wang [MSFT]

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.

=====================================================================

--------------------
>Thread-Topic: NT 4.0 to windwos 2003 network
>thread-index: AcVg/K8wv51VTXq/SfiXjPIeikUiyg==
>X-WBNR-Posting-Host: 202.179.106.114
>From: =?Utf-8?B?cmF0dGxl?= <rattle@xxxxxxxxxxxxxxxxxxxxxxxxx>
>Subject: NT 4.0 to windwos 2003 network
>Date: Wed, 25 May 2005 00:38:03 -0700
>Lines: 22
>Message-ID: <3A1AAA0B-17A9-4113-AE47-3AAF0A4C2D6B@xxxxxxxxxxxxx>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.windows.server.migration
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.migration:10365
>X-Tomcat-NG: microsoft.public.windows.server.migration
>
>We have a two domain (dom1 and dom2) network with one NT40 server (PDC)
and
>(BDC) at each
>site. Both domain are configured to trust each other.The reason for
>two domain is because of two different companys in one group. Our registed
>domain name with isp is maxis.com.my for example.
>
>We are also running exchange 5.5 on this two domain with all the exchange
>server belong to the same site.
>
>Our network Users are using windows nt 4.0 workstation, windows 2000 pro
>and xp pro client.
>
>Question
>
>1. What is the best way to migrate to win2003 and exchange 5.5 and we
> prefer the migration to be in stages?
>
>2. In the existing setup both site have their own set of users on their own
> domain, I would like the setup with win2003 do I need to create multiple
> and forests or one domain with two child domains.
>
>3.
>

.



Relevant Pages

  • RE: Transfer roles
    ... fresh copies of windows 03 and exchange on one of them. ... because migration is more complex. ... The only valid business cases for installing Exchange Server on a DC that I ...
    (microsoft.public.windows.server.migration)
  • RE: DST update for Exchange 2003 and Outlook 2003
    ... The Ldp GUI tool is included when you install Windows Server 2003 Support ... Microsoft CSS Online Newsgroup Support ... DST update for Exchange 2003 and Outlook 2003 ...
    (microsoft.public.exchange.admin)
  • Re: Error DHCP Windows 2008 R2, DHCP client is not a reserved clie
    ... This results in windows 2008 R2 in the error message: The specified DHCP ... Migration with netsh has worked. ... Migrating DHCP using the Windows Server 2008 R2 Migration Tools ...
    (microsoft.public.win2000.networking)
  • RE: DST update for Exchange 2003 and Outlook 2003
    ... Majority of my users connect to Terminal Server and ... I also have users running on stand-alone PC's (Windows XP) ... run the Outlook Time Zone Data Update Tool or the Exchange calendar tool? ... 926666 Update for daylight saving time changes in 2007 for Exchange 2003 ...
    (microsoft.public.exchange.admin)
  • Re: Error DHCP Windows 2008 R2, DHCP client is not a reserved clie
    ... This results in windows 2008 R2 in the error message: The specified DHCP client is not a reserved client. ... Migration with netsh has worked. ... Migrating DHCP using the Windows Server 2008 R2 Migration Tools ...
    (microsoft.public.win2000.networking)