RE: NT4 upgrade to 2k3 Server with WAN
From: glennw (glennw_at_discussions.microsoft.com)
Date: 11/09/04
- Next message: glennw: "Is this a good migration method?"
- Previous message: Eric: "RE: NT to 2003 Migration and changing the domain name"
- In reply to: Rebecca Chen [MSFT]: "RE: NT4 upgrade to 2k3 Server with WAN"
- Next in thread: Rebecca Chen [MSFT]: "RE: NT4 upgrade to 2k3 Server with WAN"
- Reply: Rebecca Chen [MSFT]: "RE: NT4 upgrade to 2k3 Server with WAN"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 9 Nov 2004 11:59:06 -0800
I'm in a very similiar situation. However I was trying to keep the same
domain as teh old since I didn't want to have to touch each machine to join a
new domain. That isn't a big deal. Our NT4.0 servers are very outdated and
I have the new machine loaded with 2k3 but I haven't made it a domain
controller yet of a new forest. I have a couple of questions, can I add ADS
without it being plugged into the network and just shutdown the old NT4.0
servers. I'm creating new accounts and shares to clean up some old legacy
junk anyway. I have new exchange 2k3 ready to be installed and will import
the .pst from each users (only 48 users total). Is this a good method of
going about it or should I do a migration to a new domain? I can back all of
the data up to a computer then copy it back down once it's in place. I have
2 days to make this work and am now trying to read up on what needs or should
or could be done. Thanks.
"Rebecca Chen [MSFT]" wrote:
> Hello,
>
> You can use the migration or upgrade method to win2k3 domain.
>
> Migration would be a better choice if you don't want to continue to use the
> original domain name.
>
> The migration process will go like:
> 1. Setup a new Windows Server 2003 DC in the new domain.
>
> 2. Create the trust relationship between the two domains.
>
> 3. Use the ADMT to migrate data from the old domain to the new domain. Run
> win2k3 for a period of time to make sure the network can be functional.
>
> 4. Remove the original NT 4 domain.
>
> 5. Use FSMT to migrate file server.
> http://www.microsoft.com/windowsserver2003/upgrading/nt4/tooldocs/msfsc.mspx
>
> 6. Moving Windows NT Server 4.0 and Windows 2000 applications to Windows
> Server 2003, see "Moving Windows NT Server 4.0 and Windows 2000
> Applications to Windows Server 2003" at
> http://www.microsoft.com/windowsserver2003/techinfo/serverroles/appserver/mo
> vingnt4.mspx.
>
> Before you migrate, I strongly suggest that you download and read the
> following documents about migrating from Windows NT 4.0 to Windows 2003:
>
> 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
>
> with the exchange migration, please post this question to the
> microsoft.public.exchange.setup newsgroup since the Exchange guy will give
> the appropriate suggestions.
>
> HTH!
>
> Best regards,
>
> Rebecca Chen
>
> MCSE2000 MCDBA CCNA
>
>
> 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.
> --------------------
> >Thread-Topic: NT4 upgrade to 2k3 Server with WAN
> >thread-index: AcTGBEr/Kt542dFISkecxi+HF62Vhw==
> >X-WBNR-Posting-Host: 66.143.37.69
> >From: "=?Utf-8?B?RXJpa002NA==?=" <erikm64@hotmail.com>
> >Subject: NT4 upgrade to 2k3 Server with WAN
> >Date: Mon, 8 Nov 2004 18:32:01 -0800
> >Lines: 10
> >Message-ID: <1B04FC2E-A2D6-48B3-A46A-ACAE8F18DE2B@microsoft.com>
> >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.1.29
> >Path: cpmsftngxa10.phx.gbl!TK2MSFTNGXA03.phx.gbl
> >Xref: cpmsftngxa10.phx.gbl microsoft.public.windows.server.migration:15101
> >X-Tomcat-NG: microsoft.public.windows.server.migration
> >
> >I am currently looking to upgrade a WAN with 3 locations to 2k3 Server
> from
> >NT4. I am unable to upgrade the NT4 servers because of legacy hardware
> that
> >is not compatible with 2k3 such as SCSI controllers. I was thinking about
> >creating a new domain with new servers and moving all the workstations
> over
> >to the new domain but was wondering if there was a way to do the upgrade
> >easier or even allow a way to create a trust between the two domains to
> allow
> >workstations on the old domain to access info on the new domain. There is
> >currently a PDC, app server and exch server running at the main location.
> >Does anyone know of a way to do this as seamless as possible? Thanks in
> >advance
> >
>
>
- Next message: glennw: "Is this a good migration method?"
- Previous message: Eric: "RE: NT to 2003 Migration and changing the domain name"
- In reply to: Rebecca Chen [MSFT]: "RE: NT4 upgrade to 2k3 Server with WAN"
- Next in thread: Rebecca Chen [MSFT]: "RE: NT4 upgrade to 2k3 Server with WAN"
- Reply: Rebecca Chen [MSFT]: "RE: NT4 upgrade to 2k3 Server with WAN"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
