Re: Installing New Domin Controller

Would the fact that I am coming from 2000 to 2003 ( not from NT to 2000 as
this cookbook seems to be composed for) have any effect on digesting and
using the methods outlined in this cookbook ??

""Ken Zhao [MSFT]"" wrote:

Hello Dan,

Thank you for using newsgroup!

From your post, for more related information about migration plan and
utilities, I suggest you refer to the following article that describes the
whole process:
Windows 2000 Server Domain Migration Cookbook
http://www.microsoft.com/technet/prodtechnol/windows2000serv/deploy/cookbook
/cookintr.mspx

555549: How to replace single domain controller in domain with a single
domain controller?
http://support.microsoft.com/kb/555549

555040: Common Mistakes When Upgrading a Windows 2000 Domain To a Windows
2003 Domain
http://support.microsoft.com/kb/555040

Upgrading from Windows 2000 Server to Windows Server 2003
http://www.microsoft.com/windowsserver2003/upgrading/w2k/default.mspx

Thanks & Regards,

Ken Zhao

Microsoft Online Support
Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security <http://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.





--------------------
| Thread-Topic: Installing New Domin Controller
| thread-index: Acfxf53OKBB7XwypSr2ZY/UmCRAnWw==
| X-WBNR-Posting-Host: 207.46.19.168
| From: =?Utf-8?B?RGFuIERlQ291cnNleQ==?=
<DanDeCoursey@xxxxxxxxxxxxxxxxxxxxxxxxx>
| References: <28259CF8-78E7-4008-A007-3EAE6B06B9CE@xxxxxxxxxxxxx>
<ff16fb6652f698c9bf81bf754b5d@xxxxxxxxxxxxxxxxxxxx>
| Subject: Re: Installing New Domin Controller
| Date: Fri, 7 Sep 2007 11:48:01 -0700
| Lines: 65
| Message-ID: <B051E222-70D2-4F5E-A55A-5A9AF0A74DD4@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.2826
| Newsgroups: microsoft.public.windows.server.migration
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.windows.server.migration:2057
| NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148
| X-Tomcat-NG: microsoft.public.windows.server.migration
|
| gpprep also ????
|
| "Meinolf Weber" wrote:
|
| > Hello Dan,
| >
| > First you have to upgrade the schema on the 2000 DC, for that use the
2003
| > install disk and use the adprep command from the i386 folder, in your
case
| > adprep /forestprep and adprep /domainprep:
| >
http://technet2.microsoft.com/WindowsServer/en/library/bc5ebbdb-a8d7-4761-b3
8a-e207baa734191033.mspx?mfr=true
| >
| >
| > Install the new one with 2003, promote it to DC and move the FSMO
roles,
| > here about the moving:
| > http://support.microsoft.com/kb/324801
| > In the Event viewer Dircetory services look for a succesful entry for
the
| > moving of the roles and with the moving give it a bit time.
| >
| >
| > Make the new server also a Global catalog:
| > Open Active directory site and services, go to Sites, default first
site
| > name, servers, choose the server, right click NTDS settings, open
properties
| > and checkmark Global catalog (check event viewer after it, in Directory
service
| > you must find event id 1110 and 1119)
| >
| >
| > DNS is easy, is it running as Active directory integrated zone on the
old
| > one? If not make so, then it will replicate automatically to the new
one
| > if you installed DNS on the new server. Make sure the new server is
only
| > pointing to the old server for DNS on the NIC. Give it time for
replication.
| > After replication change the clients settings to the new DNS server,
via
| > DHCP options and also the settings for the old one to the new as pimary
DNS
| > on the NIC.
| >
| > Check with dcdiag and netdiag for errors.
| >
| > For DHCP check this one:
| > http://support.microsoft.com/default.aspx?scid=kb;en-us;325473
| >
| > If everthing runs fine, demote the server with dcpromo to remove it
correctly.
| > It will appear under computers after demotion and then you can safely
delete
| > it. If you just shut it down you will get a lot of replication errors.
| >
| >
| > Best regards
| >
| > Meinolf Weber
| > Disclaimer: This posting is provided "AS IS" with no warranties, and
confers
| > no rights.
| >
| > > Existing DC= Windows 2000 with integraed AD and DNS New Dc = Win2k3
| > >
| > > As of now the Win2k DC is not replicating and is the only DC in the
| > > Domain so it has all roles on the one box...
| > >
| > > I need a roadmap on which utilities to run (in what order) to
| > > "copy/migrate " everything that would be needed to get the new DC to
| > > "take over" in the smoothest possible manner then I will work on
| > > getting some replication in place
| > >
| > > thanks
| > >
| >
| >
| >
|


.

Relevant Pages

  • Re: SBS 2003 and Replication Errors with Remote DC
    ... alpha server as soon as you can to get things going. ... A simple DNS replication test is to create a host record in the SBS server ... Domain Controller Diagnosis ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 and Replication Errors with Remote DC
    ... I did make the changes that you suggested on the DNS of my alpha server and rebooted. ... I did run the simple DNS test that you suggested by adding a host record to my SBS server. ... A simple DNS replication test is to create a host record in the SBS server and wait till it shows up in the remote server. ...
    (microsoft.public.windows.server.sbs)
  • Re: NT Domain to AD migration
    ... Windows 2000/XP always prefer Kerberos authentication, ... Server 2003 Active Directory service, ensure that you have designed a DNS ...
    (microsoft.public.windows.server.active_directory)
  • Re: how do i move primary DC from one machine to another
    ... Test omitted by user request: DNS ... Connecting to directory service on server WIN2003DC. ... Replication Site Latency Check ...
    (microsoft.public.windows.server.general)
  • Re: error 8254 DNS Lookup failure
    ... FYI, I repointed the DNS to one server, deleted the contents of _MSDCS ... > in the same site, Replication has been fine up until yesterday, the ... > Starting test: CrossRefValidation ...
    (microsoft.public.win2000.dns)
Loading