RE: Rollback of failed NT domain upgrade

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

Hi,

By default, Windows 2000/XP clients use only Windows 2000-based domain
controllers in a mixed-mode domain. Therefore, if you remove your only
Windows 2003 domain controller, all the Windows 2000/XP clients cannot log
into the domain.

For the rollback requirement, you may refer to article 284937 to add
NT4Emulator on Windows NT 4.0 PDC. Then upgrade the domain controllers to
Windows 2003 domain controller. In this situation, a Windows 2000/XP client
will no longer receive group policy nor will it do Kerberos authentication.
The Windows 2003 domain controller may just work like a Windows NT 4.0 PDC.
You can roll back the domain without rejoining the workstations into domain.

However, in this situation, if you want to promote a Windows 2003 domain
controller to a new Windows 2003 domain controller, you need to add the
value NeutralizeNT4Emulator. Otherwise, since the member server does not
consider it as a Normal Windows 2003 domain, the promotion may not work.

In addition, this procedure is a temporary solution. If you want to have a
normal Windows 2003 domain, you should remove the NT4emulator registry
value on all the Windows 2000/2003 domain controllers.


Best regards,

Vincent Xu
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 this issue.
======================================================
This posting is provided "AS IS" with no warranties,and confers no rights.
======================================================



--------------------
From: "phatgeezer" <LDunham@xxxxxxxxx>
Newsgroups: microsoft.public.windows.server.migration
Subject: Rollback of failed NT domain upgrade
Date: 14 Aug 2006 10:13:02 -0700
Organization: http://groups.google.com
Lines: 16
Message-ID: <1155575582.439192.178890@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
NNTP-Posting-Host: 216.8.88.3
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
X-Trace: posting.google.com 1155575588 19128 127.0.0.1 (14 Aug 2006
17:13:08 GMT)
X-Complaints-To: groups-abuse@xxxxxxxxxx
NNTP-Posting-Date: Mon, 14 Aug 2006 17:13:08 +0000 (UTC)
User-Agent: G2/0.2
X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1;
..NET CLR 1.1.4322; .NET CLR 1.0.3705),gzip(gfe),gzip(gfe)
Complaints-To: groups-abuse@xxxxxxxxxx
Injection-Info: m73g2000cwd.googlegroups.com; posting-host=216.8.88.3;
posting-account=OAMDXg0AAACTQiDCKuCXhZFtIPe6KxgD
Path:
TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTFEEDS01.phx.gbl!msrnewsc1!
msrtrans!newsfeed.media.kyoto-u.ac.jp!postnews.google.com!m73g2000cwd.google
groups.com!not-for-mail
Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windows.server.migration:24789
X-Tomcat-NG: microsoft.public.windows.server.migration

I am preparing an implementation plan and need help with writing the
rollback procedures.

If I set aside a BDC and in case of upgrade failure put it back online
as PDC that takes care of the server end.

However I read somewhere (and naturally now cannot find it) that if any
of the client boxes have logged into the upgraded domain and
subsequently the decision is made to rollback, there is something that
needs to be done to the client so that they will look for the old NT
domain again--a config setting or registry key or something that is
changed in the client the first time it logs into an Active Directory
domain.

Can anyone help me with that procedure?



.

Relevant Pages

  • Re: Upgrading NT4.0 To Windows Server 2003
    ... When performing an in-place upgrade of a Windows NT 4.0 domain to Windows ... the first domain controller upgraded is the Windows NT 4.0 PDC. ... authentication, the negotiation of the authentication protocol will reveal ...
    (microsoft.public.windows.server.active_directory)
  • Re: Client performance problem windows 2003 server...
    ... In addition, if you have the same problem with non-English client, please ... >Subject: Re: Client performance problem windows 2003 server... ... >>>Deploying Active Directory for Branch Office Environments ... >>>results from not having a domain controller in a particular site. ...
    (microsoft.public.windows.server.networking)
  • Re: Auto Sync Client Time with Server
    ... Should work automaticly if the client is well integrated in the AD-Structure ... Windows 2000 Time Services ... 2000 for the 'loose time synchronization' required by Kerberos. ... requests time synchronization with the domain controller. ...
    (microsoft.public.windows.server.sbs)
  • Re: Windows wont start
    ... when the XP upgrade maintained it was still ... Windows XP logo appeared. ... when windows 98 starts, my display is very poor (16 ... >> I do not know what this Fax Client is and have never used it. ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: XP Installation Problem
    ... > I'm trying to upgrade to Windows XP from ME, ... > upgrading to Windows XP, and will be replaced by the Windows XP ... > uninstall this fax application using Add/Remove Programs in the ... > Program named 'Microsoft Shared Fax Client' among my Add/Remove ...
    (microsoft.public.windowsxp.help_and_support)