Windows Server -- 2003 to 2012 R2

finance_teacher used Ask the Experts™
Does anyone have a GOOD step-by-step checklist
like the below when I replace my two 2003 32bit
DC, AD, DNS, DHCP, GP, file, and print servers,
one server at each location, with newer
2012 64bit servers ?

 1. add new 2012 64bit servers to domain
 2. use "Windows Server 2012 Migration Tools",
    Microsoft's ROBOCOPY or XCOPY, etc to do the below
       ** copy files and security
       ** copy assocaited user and security
       ** copy DC, AD, DNS, DHCP, GP, RAID, etc settings
       ** install 32 and 64 bit NETWORKED printers
       ** deal with any Deprecated features
 3. make sure EqualLogic SAN connections and
    old site #2 2003 DC can still be replicated/etc
 4. promote them at the same time to avoid
 5. change a few CLIENTS primary DNS server
    to be new 2012 64bit servers' IP
 6. test both locations
 7. demote old servers
 8. change new 2012 64bit servers' IP address to old
    servers' IP so remaining clients get new server
 9. setup "file server resource manager"
    on new server to move to OLD folder if
    "last file access time"
    is over 365 days ago
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Do not forget to move your FSMO Roles.

How many DomainControls do you have?

Do you have any Certification Authority?

After remove all Win 2003 DC, is a nice idea to Raise your Domain/Forest Level. Check the compatibility with other applications based on AD (Exchange Server for Example)
In Step 4. After promote the new Windows 2012 as DC, move all FSMO roles and be sure to wait to AD replication be complete before remove Domain Controll role from Windows 2003 Server.

I had 2 Windows 2012 (Not R2) as Domain Controllers running togheter with 4 Windows 2003 Domain Controllers for sometime (~ 2 months) and I didn't had issues.
Distinguished Expert 2018
You aren't going to find such a checklist. There are just too many variables. Roles and features, LOB apps, network topologies, storage topologies, and more would make a good checklist for one site meaningless for another. Really the only good way to do this is to do a full site survey and then work through the discovery process and build a migration plan that is site specific using TechNet for MS roles and LOB vendors documentation to cover their products. I find using OneNote or evernote to make an outline and then start adding web links to each step works well. But I do roughly 3 migrations a month and haven been for years and in that time, no two have been so similar that I recreated the same document.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial