RE: NT to W2k3 fears and questions

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Joe Wu [MSFT] (joewu_at_online.microsoft.com)
Date: 03/01/04


Date: Mon, 01 Mar 2004 14:57:32 GMT

Hello,

Thank you for your post and I am glad to hear that you have benefited from
our posts.

As I understand it, you are planing to upgrade from Windows NT domain to
Windows Server 2003, and you would like to know what will be affected on
both the server and the clients.

Actually, Windows NT domains save the accounts information in SAM database,
while AD domains save data in AD database. When upgrading a Windows NT PDC
and promoting it to an AD domain, the domain information in SAM database
will smoothly be migrated to the AD database. Therefore, the current domain
will be kept.

The local accounts on each clients will also be intact. Actually, the
domain upgrade will not change the client during this process.

In addition, I would like to provide several additional suggestions:

1. Set up a test environment in a lab and test your migration plan.

We can establish a similar lab environment and use it to check the upgrade
plan.

After you have thoroughly tested your upgrade steps, and restoration
processes. Make sure that everything worked as expected. Only after you are
fully satisfied with the success of the test upgrade, should you begin a
full migration in the production domain.

The test also gives you an opportunity to accumulate experience and check
your time estimates for the whole upgrade plan.

2. As always, please perform full backups for the domain controllers and
the file server which keeps the roaming profile. We are able to restore the
network if a unexpected issue occurs during the migration.

I hope the above information helps. Please do not hesitate to let me know
if anything is unclear. Have a great day!

Regards,
Joe Wu
Product Support Services
Microsoft Corporation

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: NT to W2k3 fears and questions
|thread-index: AcP9/0Ji0XQRxVKPSjesn8PCCZmYLQ==
|X-Tomcat-NG: microsoft.public.windows.server.migration
|From: =?Utf-8?B?TURI?= <anonymous@discussions.microsoft.com>
|Subject: NT to W2k3 fears and questions
|Date: Sat, 28 Feb 2004 05:32:06 -0800
|Lines: 1
|Message-ID: <2723D37C-97F6-4976-BB29-3C8D2793F522@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
|Path: cpmsftngxa06.phx.gbl
|Xref: cpmsftngxa06.phx.gbl microsoft.public.windows.server.migration:8337
|NNTP-Posting-Host: tk2msftcmty1.phx.gbl 10.40.1.180
|X-Tomcat-NG: microsoft.public.windows.server.migration
|
|Seems like many have had either a bad experience (which I fear) or
premonitions of bad experience (which I have) in upgrading / migrating to
W2K3 from NT. I have learned much by reading this newsgroup - especially
from Joe Wu, but I have what seems like a very naive set of questions I
hope someone can answer for me: **Tremenous** amount written about what
happens at the server side of W3K3 upgrade/migration/install. In trying to
prepare, I have not seen anything **detailed** about what happens to the
client side physically; i.e., when rebooting and logging on from my XP-Pro
client will the logon automatically recognize the loss of the NT network
and the appearance of the W2K3 one, and the "pushed" group policies which
govern it? Will the local logons to the client machine still exist and be a
potential pitfall for unwary users? Should they (the local logons to the
client machines) be deleted so that only the net logons persist? Can they
be? How? What about the previously innate / added accounts, such as
Administrator, Power User, User on the local machine - how do they figure
in - if they weren't included in the new Users list, or OU, or groups, etc.
at the server, should they be deleted? can they be? Hope I'm getting my
point across and thanks in advance. It probably will be much simpler to
just do it - but I'm trying to pre-prepare and liken it to my NT learning
curve and it doesn't make sense.
|



Relevant Pages

  • Re: Upgrading from NT4 to SBS2003 Premium
    ... > install SBS 2003 on a new hardware; refer to the following white paper to ... > do a migration of the user and computer accounts. ... Migrating from Small Business Server 4.5 or Windows NT ... > an In-Place upgrade. ...
    (microsoft.public.windows.server.sbs)
  • Re: Upgrading from NT4 to SBS2003 Premium
    ... perform an in-place upgrade to w2k3 Standard Server from the NT4. ... This newsgroup only focuses on SBS technical issues. ... possible to do an In-Place upgrade to w2k3 Standard and then an In-Place ... |> do a migration of the user and computer accounts. ...
    (microsoft.public.windows.server.sbs)
  • RE: Upgrading from NT4 to SBS2003 Premium
    ... the In-Place upgrade path from NT4 to SBS2003 is not ... install SBS 2003 on a new hardware; refer to the following white paper to ... do a migration of the user and computer accounts. ... Migrating from Small Business Server 4.5 or Windows NT ...
    (microsoft.public.windows.server.sbs)
  • Re: URGENT - Migration Strategy
    ... period of time, and then promote the win2k3 to be a DC, migrate everything ... Comparing with migration and upgrade plan, I would like to list the ... configuration management, for example, for a server where high availability ... Your migration plan seems good and safety and you can see the reasons to ...
    (microsoft.public.windows.server.migration)
  • Re: upgrade w2k to w2003 running Exchange 2003
    ... The client wants to upgrade to Windows 2003 Server on the box ... > while keeping Exchange Server and Active Directory intact. ... Any advise on the upgrade is welcome.. ...
    (microsoft.public.windows.server.setup)