RE: NT4 dom -> 2003 AD: Strategy questions
- From: v-jasont@xxxxxxxxxxxxxxxxxxxx (Jason Tan (MSFT))
- Date: Thu, 14 Jul 2005 06:02:03 GMT
Hi Rich,
Thanks for posting!
Based on your description, I would like to provide you with the following
suggestion:
In your scenario, you want to migrate from a tiny Windows NT domain to
Windows 2k3 domain. Based on my experience, in-place upgrade is a best
practice to maintain the domain name since migration using ADMT need to be
performed between two different domain.
Generally, we do not perform the in-place upgrade on the current Windows NT
PDC. You have two choices based on the brand new hardware.
1. If the brand new hardware supports both Windows NT and Windows 2k3, See
the below:
You may install Windows NT on the new hardware and make it a BDC on the
domain. Make the BDC box up to date and promote it to the PDC, doing this
will demote the current PDC to a BDC automatically. Ensure the replication
is working properly. Take the PDC off the network. For now your network
will be running without a PDC. This keeps your network intact so you can
easily fall back to the original configuration. Upgrade the PDC to Windows
2k3 DC and later put the server back on the network.
2. If the brand new hardware does not support both Windows NT and Windows
2k3, you may use a upgrade box. So I recommend that you find a slightly
older box that meets Windows Server 2003 requirements and also has NT 4.0
drivers available. Please refer to the following information.
Upgrade to Windows 2003 with hardware that does not support Windows NT 4.0.
http://spaces.msn.com/members/wilwol/PersonalSpace.aspx
=================================================
This response contains a reference to a third party World Wide Web site.
Microsoft is providing this information as a convenience to you. Microsoft
does not control these sites and has not tested any software or information
found on these sites; therefore, Microsoft cannot make any representations
regarding the quality, safety, or suitability of any software or
information found there. There are inherent dangers in the use of any
software found on the Internet, and Microsoft cautions you to make sure
that you completely understand the risk before retrieving any software from
the Internet.
Hope the information helps. If there is anything that is unclear, please
feel free to let me know.
Thanks & Regards,
Jason Tan
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.
--------------------
| Reply-To: "Rich Roller" <rich@*REMOVE-THIS*r2c.com>
| From: "Rich Roller" <rich@*REMOVE-THIS*r2c.com>
| Subject: NT4 dom -> 2003 AD: Strategy questions
| Date: Wed, 13 Jul 2005 14:10:16 -0400
| Lines: 37
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.2527
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527
| X-RFC2646: Format=Flowed; Original
| Message-ID: <OXpggY9hFHA.3912@xxxxxxxxxxxxxxxxxxxx>
| Newsgroups:
microsoft.public.windows.server.migration,microsoft.public.windows.server.ac
tive_directory
| NNTP-Posting-Host: ool-4356307b.dyn.optonline.net 67.86.48.123
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windows.server.active_directory:32221
microsoft.public.windows.server.migration:11232
| X-Tomcat-NG: microsoft.public.windows.server.migration
|
| A tiny company (1 NT4 server + 6 users) wants to upgrade to a new
| WS2003 server & AD domain. The NT4 server is a fairly simple File & Print
| server. But it is old! (Jan.2001, Pentium 3/866Mhz?, 256MB RAM, 25GB disk
| free) I'm considering options for them.
|
| I'm NOT preferring to do an in-place upgrade, but if I did, it would just
be
| temporary so as to retain the old domain name, etc.. Then make the new
| WS2003 box the DC for AD, migrate svcs/data to it, and kill the NT4 box.
| But if I change my mind and go this way...
|
| Q1: Is that old box likely to take WS2003 easily? I'm concerned that I
may
| get stuck in limbo with the server no longer working as NT4 DC nor fully
| functional as an AD DC because of compatiblility, drivers, etc.
|
| Q2: Would in-place upgrade allow me to keep the same netbios domain name,
| and allow the users to keep their old local profiles or would those
profiles
| still need to be copied/migrated?
|
| Q3: It is NOT possible/easy to avoid having to recreate each user's
mappings
| to server shares & printers, right? The only way I could imagine this
would
| be for the new server to have the same name as the old one, but that would
| be more trouble than it's worth I figure.
|
| Otherwise, I'm thinking about leaving the NT4 domain/server as is, and
doing
| a side-by-side migration to a clean new WS2003 box, using trusts, ADMT,
| local profile migrations, etc. Then once AD is fine, killing NT4. If I
go
| this way...
|
| Q4: With only 6 users, perhaps it would be easiest and/or most successful
to
| just go to every PC and copy their local profile through the GUI ("System
| Properties")? Rather than using ADMT, MoveUser or whatever?
|
| TIA,
|
| Rich
|
|
|
.
- Prev by Date: Demoting First Domain Controller
- Next by Date: RE: Running adprep
- Previous by thread: Demoting First Domain Controller
- Next by thread: FSMT: Remove User Access to Shared Folders Question
- Index(es):
Relevant Pages
|
