RE: Win NT to Win2k3 Upgrade

Hi Amanda, ok followed the route where i made a bdc then upgraded to pdc.
Installed Service pack 6a, installed
IE6. On the box it says : Windows small business server 2003 premium edition
and it has a upgrade sticker on it aswell. I insert CD1, goto i386 dir and
run winnt32.exe. It launches but it does not give me the option to upgrade.
What could be the problem?

"Amanda Wang [MSFT]" wrote:

> Hello,
>
> I'm glad to hear from you.
>
> First, please help me confirm your current demands:
>
> 1. Your old NT4 server's hardware cannot support Win2k3 server and you want
> to install Win2k3 on a new box
> 2. You want to keep the original domain name in new Win2k3 domain
> 3. There are many users and profiles under my current domain name
>
> For the current situation and based on my experience, it is recommended to
> use the upgrade process to achieve the goal, it just like your second
> concern as following and it should be a good way, however you need to make
> sure you have another machine which can support both WinNT and Win2k3
> server.
>
> What if I add a bdc to current domain with pdc (NT4), take the bdc of the
> net and promote it to pdc, upgrade to Win2k3, take the original NT4 pdc of
> the network and add the new win2k3 pdc to the network. Will that also work?
>
> Following are the detailed steps about how to perform upgrade process:
>
> As a kind reminder, please backup the whole system before you take any
> action. Also, it is best if you perform the upgrade process during a
> non-business time such as the weekend.
>
> 1.Install NT 4.0 BDC on the new box.
>
> 2.Promote the BDC to the PDC, which demotes the PDC to a BDC.
>
> 3.Do a full backup of the former PDC and remove it from the network.
>
> 4.Upgrade the new PDC to Windows Server 2003.
>
> 5.Use the Windows Server 2003 Active Directory wizard to turn on the Active
> Directory service. The Active Directory service imports the existing user
> accounts, groups, and other settings from the PDC.
>
> How to Verify an Active Directory Installation
> http://support.microsoft.com/default.aspx?scid=kb;en-us;298143
>
> 6.Run for a test period.
>
> 7.Add the new Windows Server 2003, and bring it online as an Active
> Directory domain controller.
>
> 8.Transfer GC and all Flexible Single-Master Operation (FSMO) roles to the
> new Windows Server 2003 domain controller.
>
> About how to transfer GC and FSMO, please refer to the following articles:
>
> Configure a domain controller as a global catalog server (Windows Server
> 2003)
> http://www.microsoft.com/technet/prodtechnol/windowsserver2003/proddocs/stan
> dard/msmqconcepts/msmq_inst_set_gc.asp
>
> 255690 - HOW TO View and Transfer FSMO Roles in the Graphical User
> Interface:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;255690&Product=win20
> 00#4
>
> 9.Verify all directory information has replicated.
>
> Verify successful replication to a domain controller
> http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/Opera
> tions/00e7f86b-ccd3-4cb8-9a01-bf747241b500.mspx
>
> 10.Demote the first domain controller to a member server, and remove from
> the domain.
>
> 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: Win NT to Win2k3 Upgrade
> >thread-index: AcVsJ5zBSIHCJJ3wTRy/xkRxhXBdug==
> >X-WBNR-Posting-Host: 196.38.71.29
> >From: "=?Utf-8?B?SmVyZW15IEo=?=" <JeremyJ@xxxxxxxxxxxxxxxxxxxxxxxxx>
> >References: <66494CB2-179D-4F04-8A40-2EB15B96B6E0@xxxxxxxxxxxxx>
> <s#mUyYAbFHA.388@xxxxxxxxxxxxxxxxxxxxx>
> >Subject: RE: Win NT to Win2k3 Upgrade
> >Date: Wed, 8 Jun 2005 05:43:03 -0700
> >Lines: 126
> >Message-ID: <1829900E-BCF9-4C63-8771-B38B0C612408@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:10551
> >X-Tomcat-NG: microsoft.public.windows.server.migration
> >
> >Thank you for your quick responce. I have some more qeustions, I
> >dont want to change domain names cause i have alot of users
> >and profiles under my current domain name, or is there a way
> >to move profiles on pc's from one domain to another domain?
> >Another qeustion to this upgrade issue. What if i add a bdc to
> >current domain with pdc (NT4), take the bdc of the net and promote
> >it to pdc, upgrade to Win2k3, take the original NT4 pdc of the network
> >and add the new win2k3 pdc to the network. Will that also work ?
> >
> >
> >"Amanda Wang [MSFT]" wrote:
> >
> >> Hello,
> >>
> >> Thanks for your post.
> >>
> >> I understand you encountered the issue that Win2k workstations cannot
> see
> >> the new Win2k3 PDC. If I have misunderstood, please feel free to let me
> >> know.
> >>
> >> From your description, it seems that you manually entered the users and
> >> computers account into new Win2k3 PDC. Actually, even though the
> recreated
> >> user account has the same name as the original one. However, it has
> fully
> >> different SID. That is to say, in nature it is a different user account
> >> from the original one in Windows NT domain. Therefore, for your current
> >> situation is that original WinNT hardware cannot support Win2k3, I
> >> recommend you perform the following migration steps to achieve the goal:
> >>
> >> Step 1: Install new Win2k3 system
> >>
> >> Step 2: Establish trusts between WinNT and Win2k3 to refer the following
> >> article:
> >> Note: The Windows 2k3 domain has different domain name as the Windows NT
> >> domain.
> >> How To Establish Trusts with a Windows NT-Based Domain in Windows Server
> >> 2003
> >> http://support.microsoft.com/default.aspx?scid=kb;en-us;325874
> >>
> >> Step 3: Use ADMT tool to migrate the resources from old domain to new
> >> domain.
> >>
> >> You can download ADMT from the link below:
> >> Active Directory Migration Tool v.2.0
> >>
> http://www.microsoft.com/downloads/details.aspx?FamilyID=788975b1-5849-4707-
> >> 9817-8c9773c25c6c&DisplayLang=en
> >>
> >> 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
> >>
> >> During migration process, the Recommended Migration Order is listed
> below
> >> for your reference:
> >> 1. Domain Global Group
> >> 2. Domain Local Group
> >> 3. User migration
> >> 4. Computer migration
> >>
> >> For detailed migration order you can refer to the following article and
> pay
> >> more attention to the Figure 9.8:
> >>
> http://www.microsoft.com/technet/prodtechnol/windows2000serv/deploy/cookbook
> >> /cookchp9.mspx
> >>
> >> Step 4: Retire the old WinNT domain.
> >>
> >> 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: Win NT to Win2k3 Upgrade
> >> >thread-index: AcVr9nBAgw4VOBj8SQKNkEO7cHQ2dw==
> >> >X-WBNR-Posting-Host: 196.38.71.29
> >> >From: "=?Utf-8?B?SmVyZW15IEo=?=" <JeremyJ@xxxxxxxxxxxxxxxxxxxxxxxxx>
> >> >Subject: Win NT to Win2k3 Upgrade
> >> >Date: Tue, 7 Jun 2005 23:51:03 -0700
> >> >Lines: 13
> >> >Message-ID: <66494CB2-179D-4F04-8A40-2EB15B96B6E0@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:10545
> >> >X-Tomcat-NG: microsoft.public.windows.server.migration
> >> >
> >> >I have recently upgraded out network from NT4 to Win2k3. The NT Domain
> >> >Controller (DC) is a old P1 machine and is inadequate for Win2k3S. I
> >> >installed it on a P4 machine and disconnected the NT4 DC from the
> network.
> >> >Entered computers and users on Win2k3 machine.
> >> >The Win2k Pro machine does not see the new Win2k3 PDC and defaults to
> >> local
> >> >profile on hdd, no shares work and there's no authentication for these
> >> win2k
> >> >machines.
> >> >All the pc's have static ip's and a gateway and our ISP's dns servers
> >> >settings is used as I connect through dedicated line to our sister
> >> company's
> >> >proxy.
> >> >
> >> >Why cant the Win2k machine's see the new PDC?
> >> >
> >> >
> >>
> >>
> >
>
>
.

Relevant Pages

  • RE: migrate from windows nt4 to windows 2003
    ... intend to replace the original NT PDC to a win2k3 DC. ... win2k3 domain, we will set up trusts between the two domains. ... I would like to suggest that we upgrade the NT ... 325857 How To Expand the Boot Partition During a Windows Server 2003 Upgrade ...
    (microsoft.public.windows.server.migration)
  • Exchange 5.5 to Exchange 2003
    ... I will migrate all to a new Active Directory Domain using the following steps: ... 2.Promote the BDC to the PDC, which demotes the PDC to a BDC. ... 4.Upgrade the new PDC to Windows Server 2003. ...
    (microsoft.public.exchange.setup)
  • Re: Suggested reading nt4 to server2003
    ... i will then be migrating the pdc to a fresh win2k3 server with ad. ... compatible with the new pdc until i load up and migrate the new bdc, exchange ... > If you want to perform an in-place upgrade on BDC with Exchg 5.5 installed, ...
    (microsoft.public.windows.server.migration)
  • RE: NT4 --> 2003 , lmhosts?
    ... it is not difficult to perform an in-place upgrade ... if you have PDC and several BDCs ... please upgrade PDC to win2k3 first. ... 325857 How To Expand the Boot Partition During a Windows Server 2003 Upgrade ...
    (microsoft.public.windows.server.migration)
  • Re: Update from NT4 to Server 2003 domain
    ... There are two DCs in the existing NT4 domain (PDC and BDC). ... To minimize this loss, you could periodically turn the safe BDC on and off during the upgrade process, to update its safe copy of the directory. ... Windows 2000-based clients connect only to the domain controller that was upgraded from Windows NT 4.0 in a mixed-mode domain ...
    (microsoft.public.windows.server.active_directory)