RE: Migration of XP users from NT 4.0 domain to Windows Server 2003 AD domain

anonymous_at_discussions.microsoft.com
Date: 05/05/04 

Date: Wed, 5 May 2004 11:16:20 -0700

William,

As an MCSE, I thoroughly agree with your direction. I
wish I were permitted to perform this job the right way.
However, even when I presented my supervisor with the
knowledge that an upgrade can be performed, I was told to
perform the installation as a new install anyway.

I don't see it as much of a problem as far as my
engineering knowledge is concerned. I am simply trying to
minimize downtime. Had our mutual feeling on this job
been heeded, downtime would indeed have been minimalized
even more. Alas, that is not the case.

This would appear to be a case of the blind leading the
seeing.

Thank you for your quick response anyway. It is truly
appreciated.

Kevin Kerns

>-----Original Message-----
>Hi Kevin,
>
>I suggest that you follow the instructions given by
>the KB article 326209 to replace the NT4 PDC with a
>Windows 2003 DC. That is the supported way.
>
>You can follow these steps:
>
>1. Install Windows NT Server 4.0 on the new server.
>During the installation, specify the options to make
>the new computer a backup domain controller.
>
>2. In Server Manager, promote the backup domain
>controller to a PDC.
>
>3. Make sure that there are no errors in the event
>logs and that SAM replication is completing
>successfully.
>
>4. Insert the Windows Server 2003 CD-ROM into the
>CD-ROM drive on the PDC. The Windows Server 2003
>Installation Wizard starts.
>
>5. Click Install Windows Server 2003.
>
>6. When the wizard prompts you to either upgrade or
>create a new installation, click Upgrade, and then
>click Next.
>
>7. Accept the license agreement, and then click Next.
>
>8. Type the product installation key, and then click
>Next.
>
>9. After Setup copies system files and restarts, the
>rest of the upgrade process runs automatically.
>
>10. After the upgrade is complete, the server
>restarts, and then the Active Directory Installation
>Wizard starts automatically. In the wizard, specify
>the appropriate Active Directory options.
>
>For more information please refer to the following
>article:
>
>326209 HOW TO: Upgrade a Windows NT 4.0-Based PDC to
>a Windows Server 2003-Based Domain Controller
>http://support.microsoft.com/?id=326209
>
>As a technical support, I'm not sure what kind of
>licensing problem might occur when performing the
>above procedure. For licensing issues, you can call
>1-800-426-9400 (select option 4), Monday through
>Friday, 6:00 A.M. to 6:00 P.M. (PST) to speak
>directly to a Microsoft licensing specialist.
>Worldwide customers can use the Guide to Worldwide
>Microsoft Licensing Sites
>http://www.microsoft.com/licensing/index/worldwide.asp
> to find contact information in their locations.
>
>If anything is unclear please don't hesitate to let
>us know.
>
>Sincerely,
>
>William Wang
>Microsoft Online Support Engineer
>
>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.
>--------------------
>>Content-Class: urn:content-classes:message
>>From: "Kevin Kerns" <kkerns@s-t-s-d.com>
>>Sender: "Kevin Kerns" <kkerns@s-t-s-d.com>
>>Subject: Migration of XP users from NT 4.0 domain to
>Windows Server 2003 AD domain
>>Date: Mon, 3 May 2004 08:08:34 -0700
>>Lines: 34
>>Message-ID: <774a01c43120$81130b80$a401280a@phx.gbl>
>>MIME-Version: 1.0
>>Content-Type: text/plain;
>> charset="iso-8859-1"
>>Content-Transfer-Encoding: 7bit
>>X-Newsreader: Microsoft CDO for Windows 2000
>>X-MimeOLE: Produced By Microsoft MimeOLE
>V5.50.4910.0300
>>Thread-Index: AcQxIIETG+JaYWabRtC61kXQtq0Gtw==
>>Newsgroups: microsoft.public.windows.server.migration
>>Path: cpmsftngxa10.phx.gbl
>>Xref: cpmsftngxa10.phx.gbl
>microsoft.public.windows.server.migration:10269
>>NNTP-Posting-Host: tk2msftngxa12.phx.gbl 10.40.1.164
>>X-Tomcat-NG:
>microsoft.public.windows.server.migration
>>
>>I have an unusual project on my hands. I am
>replacing an
>>NT 4.0 domain with only one server with a new server
>>running Windows Server 2003 AD. The existing
>>workstations, about 25 in number, mostly use Windows
>XP
>>Professional. The kicker is that Microsoft
>Licensing
>>indicated that an upgrade could not be done, while
>>Microsoft's technical documents indicate it can. At
>the
>>direction of my supervisor, I installed Windows
>Server
>>2003 Standard Edition on the new server fresh. I
>named
>>the server the same name as the old server
>(NTSERVER) and
>>the domain's NetBIOS name is the same as the old
>server
>>(HAC). The new domains DNS name is hac.lan.
>>
>>On the Windows XP machines, I am planning on
>shutting down
>>the old server, bringing up the new server, then
>>refreshing everyone's IP address via DHCP so the DNS
>>address is the address of the domain controller.
>Then, I
>>plan to go into the Computer Name Changes dialog box
>in
>>System Properties and simply substituting HAC with
>hac.lan
>>to allow the switch to occur. I had been thinking
>about
>>renaming the domain I setup (I have already added
>users
>>and changed group policies), but this would involve
>>setting up a Windows Server 2003 member server and
>several
>>other steps which would not be time-efficient for
>just a
>>one server deployment.
>>
>>Is this a good plan or is there some caveats I
>should be
>>aware of before I attempt this? As with any
>network, I
>>wish to minimize downtime for the conversion.
>>
>>Any thoughts you could share would be greatly
>appreciated.
>>
>>Thanx,
>>Kevin Kerns
>>
>
>.
>

Relevant Pages

  • W2k3 to W2k8 upgrade, clean SCCM 2007 installation
    ... W2k3 to W2k8 upgrade, clean SCCM 2007 installation ... I have a 2003 Server that has been upgraded to W2k8. ...
    (microsoft.public.sms.setup)
  • Re: Real simple NT to Server 2003 replacement
    ... Meanwhile, if you want to upgrade NT to 2k3, you need to use Windows 2003 ... The new box in step4 is an additional server. ... The new box in step7 is the final Windows Server 2003 PDC that you want to ... installation of Windows Server 2003, and bring it online as an Active ...
    (microsoft.public.windows.server.migration)
  • RE: NT clients after 2K3 server upgrade
    ... it seems that the NT clients cannot find ... The following article describes how to install a WINS server on Win2k3 ... I would like give you the detailed upgrade ... 5.Use the Windows Server 2003 Active Directory wizard to turn on the Active ...
    (microsoft.public.windows.server.migration)
  • RE: W2k Advanced DC to 2003
    ... I will give the general steps about how to upgrade from Win2k DC to Win2k3 ... necessary to support the Windows Server 2003 Active Directory environment. ... operation master domain controller of each domain in the forest being ...
    (microsoft.public.windows.server.migration)
  • RE: Migration of XP users from NT 4.0 domain to Windows Server 2003 AD domain
    ... >knowledge that an upgrade can be performed, ... >perform the installation as a new install anyway. ... Install Windows NT Server 4.0 on the new server. ... For licensing issues, you can call ...
    (microsoft.public.windows.server.migration)
Loading