Re: Worse Case Scenerio For In-Place Upgrade

From: Bob Qin [MSFT] (bobqin_at_online.microsoft.com)
Date: 11/17/04


Date: Wed, 17 Nov 2004 00:43:26 GMT

My pleasure!

Regards,
Bob Qin
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.

--------------------
      From: "Peter B" <___deadrattie@hotmail.com>
      Subject: Re: Worse Case Scenerio For In-Place Upgrade
      Date: Tue, 16 Nov 2004 08:12:21 -0500
      Newsgroups: microsoft.public.windows.server.migration

      
      Thanks again Bob.
      
      "Bob Qin [MSFT]" <bobqin@online.microsoft.com> wrote in message
      news:isL9Dm7yEHA.3028@cpmsftngxa10.phx.gbl...
> Hi Peter,
>
> Thanks for your posting here.
>
> Here are the general steps when we upgrade NT domain to Windows 2003
      Active
> Directory.
>
> 1. Perform a full backup for the existing Windows NT PDC.
> 2. Install Windows NT 4.0 BDC on the temp server and apply the
latest
> Service Pack.
> 3. In Server Manager, promote the BDC to PDC.
> 4. In-place upgrade the temp server to Windows Server 2003 and
install AD.
>
> The offline BDC would be nice to use for recovery. In case of
failure, you
> can take out the failed PDC upgrade, bring the old BDC back online.
> Promote the BDC to the PDC and force synchronization of the SAM
database.
> This should bring you back to where you were before the upgrade.
>
> As for the NT4Emulator and NeutralizeNT4Emulator keys, it should
only be a
> temporary solution. When you have sufficient Windows 2003 domain
> controllers, you can remove the NT4emulator registry value on all
the
> Windows 2003 domain controllers or the Windows 2000/XP clients will
no
> longer receive group policy nor will it do Kerberos authentication.
>
> Here are some documents may be helpful
> ===
> HOW TO: Upgrade a Windows NT 4.0-Based PDC to a Windows Server 2003
> http://support.microsoft.com/?id=326209
>
> Upgrading from Windows NT Server 4.0 to Windows Server 2003
>
      
http://www.microsoft.com/windowsserver2003/evaluation/whyupgrade/nt4/nt4tows
> 03-2.mspx
>
> Windows NT Server 4.0 Upgrade Guide
>
http://www.microsoft.com/windowsserver2003/partners/isvs/ntmigrate.mspx
>
> Have a nice day!
>
> Regards,
> Bob Qin
> 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.
>
> --------------------
> From: "Peter B" <___deadrattie@hotmail.com>
> Subject: Worse Case Scenerio For In-Place Upgrade
> Date: Mon, 15 Nov 2004 16:38:44 -0500
> Newsgroups: microsoft.public.windows.server.migration
>
>
> Hi All,
>
> Just curious as we talk about upgrades but never the
pitfalls, on
> what is
> the worse case "diasaster" that can occur with an in-place
upgrade
      to
> w3k.
> the domain as multiple BDC's.
>
> The Nightmare:
> - if it turns into a mess (Ie: dns/ad/wins/dhcp.. freak out or
> something
> goes astray)
> - will xp/w2kpro clients still be able to login ?
> - is it simple enough to backtrack back to NT4 "mode"
>
> How to Rectify:
> - turn off the "w3k box gone wild" ?
> - promote off-line BDC to PDC and try upgrade again ?
>
> should these KB's be implemented on the new server being
upgraded to
> w3k,
> for precautionary measures: ( a 2nd W3k box is on the network,
> waiting for
> the 1st w3k server to come on-line, so the 2nd can be
DCpromo'd into
> it) i
> have a 40-60 mix of W98 xp/w2kpro clients.
>
> 298713 How to Prevent Overloading on the First Windows 2000-
or
> Windows
> http://support.microsoft.com/?id=298713
> Windows 2000-Based Clients Connect Only to the Domain
Controller
      That
> http://support.microsoft.com/default.aspx?scid=kb;en-us;284937
>
> your thoughts or experiences greatly appreciated.
> Thanks
> Peter
>
>
>
>
      
      
      



Relevant Pages

  • RE: Isa problem after installing Windows Updates
    ... >|>Carsyn Gu ... >|>Microsoft Online Partner Support ... >|>your newsreader so that others may learn and benefit ...
    (microsoft.public.isa)
  • Re: xml
    ... please "Reply to Group" via your newsreader so ... >> Bob Qin ... >> Microsoft Online Partner Support ...
    (microsoft.public.windows.inetexplorer.ie6.browser)
  • RE: nt4 in place upgrade to windows 2003 ad
    ... >After I upgrade the first server how long should I wait to upgrade the ... >> MCSE2000 MCDBA CCNA ... >> Microsoft Online Partner Support ...
    (microsoft.public.windows.server.migration)
  • RE: Adprep /Forestprerp Error on line 333
    ... please "Reply to Group" via your newsreader so ... > Bob Qin ... > Microsoft Online Partner Support ...
    (microsoft.public.windows.server.migration)
  • RE: DNS on Root servers in W2k3
    ... please "Reply to Group" via your newsreader so ... > ISP's DNS servers on the internal DNS server. ... > Microsoft Online Partner Support ...
    (microsoft.public.windows.server.migration)

Loading