RE: nt4 appserver migration

Tech-Archive recommends: Speed Up your PC by fixing your registry

Hi David,

Thanks for your post.

I understand your mainly concern is you want to migrate a NT4 PDC to Win2k3
server with AD but the ERP software on NT4 don't support Win2k3 and so you
need to keep the NT4 server.

You provided the detailed steps about how to perform the migration and they
are feasible. However, I wonder why not introduce the new Windows 2003 box
directly(To make it a BDC and promote it as PDC, then afterwards upgrade to
Windows 2003 DC.). Whether the new hardware doesn't support the Windows
2003?

Then I will answer your two more questions regarding it:

1. Now the former PDC which is NT4 server is a BDC now in 2003 domain. You
want to demote the BDC to be a member server.

First, I assume that you want to demote BDC to be a member server because
you are afraid that the client will make authentication with the BDC. If
the OS of the Workstations are Windows 2000 or above version, please do not
worry about that. They will authenticate with Windows 2003 directly with
Kerberos. In addition, the Windows 2003 DC should act as PDC role in the
Windows 2003 Domain.

Based on my knowledge, NT has not utility to demote to member server. There
is a 3rd party product that can called Upromote that will do it.

For more information about the Upromote, please refer to:

http://utools.com/UPromote.asp

Note: The third-party product discussed is manufactured by a vendor
independent of Microsoft; we make no warranty, implied or otherwise,
regarding this product's performance or reliability.

2. Please don't worry the NS record because after you have performed AD
integrated, AD offers multimaster update and enhanced security. For
example, DNS zones are replicated and synchronized to new domain
controllers automatically whenever a new DC is added to an Active Directory
domain. In addition, directory replication is faster and more efficient
than standard DNS replication.

More information, You can refer to the following KB regarding this:

Active Directory integration
http://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/p
roddocs/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/stan
dard/proddocs/en-us/sag_dns_und_activedirintegration.asp

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.

=====================================================================

--------------------
>Date: Thu, 28 Apr 2005 14:50:35 +0200
>From: David Preuss <d.preuss@xxxxxxxxxxx>
>User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-AT; rv:1.6)
Gecko/20040113
>X-Accept-Language: en-us, en
>MIME-Version: 1.0
>Subject: nt4 appserver migration
>Content-Type: text/plain; charset=us-ascii; format=flowed
>Content-Transfer-Encoding: 7bit
>Message-ID: <uFgvhD$SFHA.3056@xxxxxxxxxxxxxxxxxxxx>
>Newsgroups: microsoft.public.windows.server.migration
>NNTP-Posting-Host: dummy-ns-kddi.de.kddi.com 195.82.35.209
>Lines: 1
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP14.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.migration:9907
>X-Tomcat-NG: microsoft.public.windows.server.migration
>
>Dear readers,
>
>I have to migrate a very simple network with only one nt4 pdc to windows
>2003 server with ad. My question is related to the fact that on the nt4
>server an erp software is running. From the vendor I got the information
>that until now 2003 is not supported. So one of the basic requirements
>is to keep the nt4 server alive.
>
>The question is how can I achieve this task?
>
>Is it possible to do the following:
>
>1. add a temporary bdc to the network (utilising Virtual PC).
>2. promote the bdc to pdc (which should make the former pdc to bdc).
>3. update the temp bdc with server 2003.
>4. install 2003 server on the new hardware and add to domain.
>5. dcpromo on the fresh 2003 server.
>6. transfer all fsmo roles to the new 2003 server.
>7. demote the temp server.
>
>If this approach would be OK then there are two more questions:
>
>1. what happens to the former pdc which was demoted to bdc after the
>upgrade? It will be a kind of bdc (if it is assumed that the 2003 server
>will have the PDC Master role), but can I demote the bdc to be only a
>member server?
>
>2. What about DNS? When upgrading the temp pdc to 2003AD DNS is a must.
>Therefor also the NS entries in the zone will be pointing to the temp
>dc. When I now install the final dc with dns (which will be ad
>integrated) what about the zone entries? How to set the correct ns
>entries for the final dc? From my point of view they will be generated
>automatically with all related entries (like dc,gc etc). Then demoting
>the temp dc will remove all the entries for that in the zone file
correctly?
>
>If the approach is not the right way, please let me know. Also if you
>have good hints on the above mentioned dns and dcpromo-like questions
>please let me know.
>
>Thanks for the support,
>
>David Preuss
>

.

Relevant Pages

  • Re: Second Trust
    ... Will the Trust be there when I change my current PDC and make my new ... server a PDC? ... you'll have AD with the NT4 server as a BDC" Why would it be a BDC and ...
    (microsoft.public.win2000.active_directory)
  • Re: NT 4.0 to windows 2003 AD in place upgrade.
    ... PDC that I make a BDC is the one I will take offline before I do the ... Exchange server the PDC, allow to SYNC. ...
    (microsoft.public.windows.server.migration)
  • Re: PDC/BDC problem
    ... Did your BDC got all the FSMO rules after takeover? ... Seems that it is missing one of the roles after you take out the broken server and cleanup your metadata. ... The PDC arrived last Monday. ... everything to reestablish the trust. ...
    (microsoft.public.win2000.networking)
  • Re: BDC DCDIAG Problem
    ... PDC and BDC are obsolete terms, ... I am looking through my DNS entries and I am only able to find SRV records ... server Security Configuration Wizard on this server perhaps? ...
    (microsoft.public.windows.server.sbs)
  • Re: Steps For Upgrading From NT4
    ... NT4 domain to an single 2003 AD domain. ... The PDC is the ONLY computer which can upgrade an NT domain. ... Install an NT4 BDC on newhardware that will support Windows ... Server ...
    (microsoft.public.windows.server.active_directory)