Checklist for migration from Win 2003 Server to Win 2016 Server for HQAD1

hi,

Anyone can advice how to prepare a checklist to migrate win server 2003 R2 to win server 2016?

Tks.

Lucky
Lucky ThamFreelancerAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Cliff GaliherCommented:
There is no direct migration pathfor any of the native roles. The gap is just too wide. Which means you are often looking at a two-stage migration for most things, and then it gets role-specific. Meaning there is no simple checklist to be offered.
0
kevinhsiehCommented:
It would help if you list what your current 2003 server is doing.
0
Lucky ThamFreelancerAuthor Commented:
Win server 2003 R2 Std Edition Version 5.2 R2 (Build 3790.srv03_sp2_qfe.150316-2035: SP2)
0
IT Pros Agree: AI and Machine Learning Key

We’d all like to think our company’s data is well protected, but when you ask IT professionals they admit the data probably is not as safe as it could be.

Lucky ThamFreelancerAuthor Commented:
Purpose

The purpose of this document is to provide the prerequisites that must be in place prior to starting a DC migration along with some post installation steps

Prerequisites:

1.      User in the source domain with membership of “Domain Admins” & “Local Admins” that would be used throughout the migration.

2.      Communication between the old (source) DC and new (target) DC.

3.      As a precaution, complete a full backup of your existing server

4.      Check the Schema version of AD DS (Before adprep) by running regedit, navigating to Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\NTDS\Parameters and noting the current Schema version.

5.      Install and configure the general application on the new DC such as Antivirus, SCCM, SCOM, Fire Eye.

Migration preparations:

a.      Ensure DNS has been configured on the target DC
b.      Create a conditional forwarder from source (domain) DNS and target (domain) DNS (AD integrated) to forward DNS queries from each other domains.
c.      Install Active Directory and promote (Server 2016)
d.      Confirm Replication & DNS in Server 2003 and 2016
e.      Transfer FSMO roles to the new server (Server 2016)
f.      Remove Windows Server 2003 DC as a Global Catalog
g.      Uninstall Old DC (Server 2003)
Example:-From source AD DNS (old domain controller)  From Target AD DNS (new domain controller)

Before begin the migration:

Audit our servers and plan the migration 2003 R2 to 2016.

Audit the servers: In a typical environment, Will have quite a few different server types. There will be role-oriented servers, which focus on Windows Server roles such as Domain Controller, Active Directory, IIS, Exchange, DNS, and DHCP. The more common group, however, are application and file servers, which run the actual business applications and store the company data. They typically outnumber the role-based group.
Migration is done in a different way for these two. Roles are migrated manually, or with utility tools.
In the planning stage and need to prepare a list of servers in the environment, and figure out what each of them is responsible for.
Schedule migration time slot: Migrations take time, and during that time, users may be affected to some extent. If possible, try and schedule the actual migration to be performed after hours or during a weekend. Note that we don’t actually have to stay there self at that time: application migration can be performed remotely or launched in advance in unattended mode
Verify backups are up to date, and are actually restorable: Any major upgrade may go wrong, and without a valid up-to-date backup, its risk losing everything we have had on the server. Make sure to verify that the backup we have is not damaged and ready to be restored if needed!
Decide on replacement type: Once have decided to replace a server, if we have several options regarding what the replacement will be. It may be a physical Windows 2016 server, a virtual server running on premise, or a Cloud-based server running off premise (such as migration to Azure or migration to Amazon AWS).

Preparing the Domain
Before Windows Server 2016 DCs can be added to the existing Windows Server 2003 domain, and will need to meet some prerequisites and perform a few recommend health checks.
Update Windows Server 2003
Let’s check that Windows Server 2003 is running Service Pack 2. Log in to the Windows Server 2003 DC with a domain administrator account, and following the instructions below:
•      Click Start, and select Run… from the Start menu.
•      In the Run box, type winver and press ENTER.
•      Click Start, and select Command Prompt from the Start menu.
•      In the command prompt window, type wuauclt /detectnow and press ENTER.
•      If there are any available updates, a yellow shield will appear in the system tray. Double click it and follow the instructions for installing the available updates. You may need to wait a few minutes for the icon in the system tray to be updated.
1
Lucky ThamFreelancerAuthor Commented:
Is there a way to collect all the AD 2003 Information for my preparation of the migration 2016 such as

1. AD Domain & Trusts
2. AD Sites and Services
3. AD Users and Computers
4. Cert Authority
5. DNS
6. Other


Tks.
0
Lucky ThamFreelancerAuthor Commented:
Q1: Why is important to Check the Schema version of AD DS (Before adprep) by running regedit, navigating to Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\NTDS\Parameters and noting the current Schema version?

Q2: What is the Schema Version 0x000000057(87) for win 2003?

Tks
0
kevinhsiehCommented:
I don't know why the document you got asked to check the schema version. The schema gets automatically updated as part of the process of adding a 2012 or newer DC. In earlier versions, you had to manually run the command to update the schema.

Checking the forest functional level and domain functional level makes sense to me, as those both need to be at least 2003 before you can add a 2016 domain controller.

What is the overall project, and your role in it? If this this a large complicated project, you don't seem at all qualified to do it. If this is a smaller project, you seem to be asking questions that would normally only be for larger environments.

You still haven't mentioned what the server or servers are actually doing. Each service or role has different steps.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2016

From novice to tech pro — start learning today.