Hi,
Thanks for posting here.
Yes, as you analyzed, if we plan to migrate to Windows server 2008, there
are lots of works to do.
If the target environment is large and we do not have a comprehensive
roll-back plan, it may cause some problems, such as SID changing, domain
object loss, user profile loss etc. Only in the situation that we have to
change domain name, such as company merge etc, we need to use domain
migration.
To consider time-efficiency and convenience, I suggest the first method. I
list the general steps below for your reference:
Domain Transaction:
===============================
1. Verify the new server's TCP/IP configuration has been pointed to the
current DNS server.
2. Make the new server become a member server of the current Windows Server
2003 domain first.
3. Upgrade the Windows Server 2003 forest schema to Windows Server 2008
schema with the "adprep /forestprep" command on old server.
Please run the "adprep.exe /forestprep" command from the Windows Server
2008 installation CD on the schema master. For example:
Drive:\CMPNENTS\R2\ADPREP\adprep.exe /forestprep
4. Upgrade the Windows 2003 domain schema with the "adprep /domainprep"
command on old server.
Drive:\CMPNENTS\R2\ADPREP\adprep.exe /domainprep
5. Run "dcpromo" on new server to promote it as an additional domain
controller in existing Windows 2003 domain, afterwards you may verify the
installation of Active Directory.
6. Verify the new server's TCP/IP configuration has been pointed to current
DNS server.
7. Insert Windows Server 2008 Installation Disc in the new server.
8. Run "dcpromo" on new server to promote it as an additional domain
controller in existing Windows 2003 domain.
9. Install DNS component on new server and configure it as a new DNS Server
(Active Directory Integrated-Zone is preferred). All the DNS configuration
should be replicated to the new DNS server with Active Directory
Replication.
To gradually remove old windows server 2003 server, here is some extra
steps we should do:
================
1. Enable Global Catalog on new server and manually Check Replication
Topology and afterwards manually trigger replication (Replicate Now) to
synchronize Active Directory database between 2 replicas.
Please note: It will some time to replicate GC between DC, please wait some
time with patience.
2. Disable Global Catalog on DC2.
3. Make all the clients change TCP/IP configuration to point to new server
as DNS.
4. Transfer FSMO roles to the new server.
How to view and transfer FSMO roles
http://support.microsoft.com/kb/324801
5. Please check whether everything works normally with the new server. If
so, you can run DCPROMO to demote old DC.
To migrate files to the new server:
========================
You can use Robocopy tool to migrate files from old server to the new
server with windows server 2008 without losing NTFS permissions.
More information about Robocopy:
http://technet2.microsoft.com/window...6e8e9-fcb3-4a4
a-9d04-2d8c367b63541033.mspx?mfr=true
Sincerely
Morgan Che
Microsoft Online Support
Microsoft Global Technical Support Center
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.
--------------------
--->Thread-Topic: AD 2008 conversion strategy
--->thread-index: AcjzV2dq4Fz6j4qjQ9CuYgmGCarYOw==
--->X-WBNR-Posting-Host: 207.46.193.207
--->From: =?Utf-8?B?RENT?= <>
--->Subject: AD 2008 conversion strategy
--->Date: Thu, 31 Jul 2008 14:50:10 -0700
--->Lines: 21
--->Message-ID: <69633BA6-57AC-4391-9E6D->
--->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.3119
--->Newsgroups: microsoft.public.windows.server.migration
--->Path: TK2MSFTNGHUB02.phx.gbl
--->Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.windows.server.migration:4134
--->NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148
--->X-Tomcat-NG: microsoft.public.windows.server.migration
--->
--->I'm building out several new servers with Win2008 and would like to
replace
--->my existing domain. The current domain has many excess users, groups,
--->computers, DNS issues, etc. which can be left behind.
--->
--->I'm considering two different options:
--->
--->1. Build new Win2008 DC's join them to the domain, demote the old
Win2003
--->DC's, and continue with the existing domain. This is easier.
--->
--->2. Build new Win2008 DC's in a new domain+forest, create a trust
--->relationship with the old domain, and gradually migrate users,
computers,
--->etc. to the new domain. This seems like more work, but should result
in a
--->cleaner, better defined/understood/etc. AD.
--->
--->I haven't done any domain migrations since an NT4 to Win2k conversion -
--->mostly I've been running mixed Win2k+Win2k3 DC's.
--->
--->Any suggestions? Best practices? Good books? I'd take a class, but I
--->don't have time for that.
--->
--->-dcs
--->
Similar Threads
Linear Mode
