RE: Migrating small domain 2000 to 2003

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



Hi Charles,

I think your steps sounds good and your preparation about the reference is
plentiful. However, I'd like to provide following article for you:

Upgrades in a domain containing Windows 2000 domain controllers
<http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/Serv
erHelp/8b42cf90-1e72-4579-b0ad-2e2b948ce31c.mspx>

I think it is a good idea to build a lab before you peform the migration or
upgrade. If you happens to any problem, feel free to let me know. I will be
glad to be of ass assistance.

Best regards,

Vincent Xu
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security


--------------------
>>From: "Charles_B" <charles.a.braun.spam@xxxxxxxxx>
>>Subject: Migrating small domain 2000 to 2003
>>Date: Thu, 18 Aug 2005 10:21:01 -0700
>>Lines: 44
>>X-Priority: 3
>>X-MSMail-Priority: Normal
>>X-Newsreader: Microsoft Outlook Express 6.00.2900.2527
>>X-RFC2646: Format=Flowed; Original
>>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527
>>Message-ID: <#52j1kBpFHA.2156@xxxxxxxxxxxxxxxxxxxx>
>>Newsgroups:
microsoft.public.windows.server.active_directory,microsoft.public.windows.se
rver.migration
>>NNTP-Posting-Host: 204-89-11-x-cityofpasadena.net 204.89.11.103
>>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP14.phx.gbl
>>Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windows.server.migration:11712
microsoft.public.windows.server.active_directory:35248
>>X-Tomcat-NG: microsoft.public.windows.server.migration
>>
>>We are in the planning stages of migrating our DMZ domain from 2000 to
2003
>>and I am looking for information on the best method for completing the
>>migration with as few headaches as possible.
>>
>>Our DMZ domain is currently configured as:
>>1DC on old hardware running Windows 2000.
>>This is the only DC in the DMZ domain so naturally it has all the FSMO
roles
>>and it is running in native mode.
>>This machine also hosts our external DNS.
>>This machine is a DHCP server
>>There are 15 other servers in the domain and about 30 users so it is a
small
>>domain in that sense
>>This machine does all the backups for the domain (Backup Exec 8.6 to
locally
>>attached DLT autoloader)
>>
>>The new DCs (There will be 2) will be on new hardware and Windows 2003
>>Standard with SP1.
>>We will keep the same domain name
>>1 of the new DCs will take over all the roles as far as DNS (There is
>>already a secondary DNS that will remain as is), DHCP, backups for all
DMZ
>>systems etc
>>
>>My thoughts are:
>>Extend the schema (Do all the forest and domainprep on the existing DC)
>>Build and DCPromo the new 2003 DCs
>>Allow replication
>>Transfer FSMO roles
>>Pull DNS Zone info
>>Reinstall Backup Exec and associated Hardware
>>DCPromo the old DC and shut it down
>>Go to native mode on the new DCs
>>
>>To help me prepare for this, I have read:
>>http://support.microsoft.com/?id=324801
>>http://support.microsoft.com/kb/325473/
>>http://support.microsoft.com/kb/325379
>>http://support.microsoft.com/default.aspx?scid=kb;en-us;555040
>>http://support.microsoft.com/kb/331161
>>
>>Does anyone know of anything else that I should read or do prior? We are
>>planning on doing this in a lab environment first but would naturally
like
>>as few bumps as possible.
>>
>>
>>

.



Relevant Pages

  • Re: Installing SBS2008
    ... I'm going to address the DNS and DHCP cleanup first, ... then later installing the server at the production location (your ... enough disk space to do preparation of the server for the migration. ...
    (microsoft.public.windows.server.sbs)
  • Re: Migrating NT domain to AD
    ... The W98 machines do not have to have AD client to be in the new domain, ... ONLY AD domain controllers are listed as preferred dns servers for your computers via ... The downside is that I believe some of the better migration tools ... require that the migration be to a native mode domain. ...
    (microsoft.public.win2000.security)
  • RE: NT4.o to WIn2003 Domain MIgration DNS configuration
    ... one thing more i want to point out that the primary dns suffix is not there ... that to change automatically upon migration. ... I am migrating these clients from nt4.0 domain to win2003 and this message ... Microsoft Online Partner Support ...
    (microsoft.public.windows.server.migration)
  • RE: NT4.o to WIn2003 Domain MIgration DNS configuration
    ... We suggest you point all the clients machines to the new Windows 2k3 DNS ... and perform the migration. ... | nt4.0 domain dns which is in my dhcp settings. ...
    (microsoft.public.windows.server.migration)
  • Re: Over-the-Wire Migration Plan
    ... I'd set your DHCP leases down to about 2 hours on the Linux box. ... Then I'd build out your DC1 server, but not dcpromo it just yet. ... Add DNS services to your DC1 server. ... WITH Dynamic updates (not secure dynamic updates - do that post migration). ...
    (microsoft.public.windows.server.active_directory)