SBS 2011 Standard to Windows 2012 R2 Essentials migration query

I'm currently installing a new Windows 2012 R2 Essentials Server and all I would like to do is make the new Server the new domain controller and keep the internal domain name to save time taking client machines out of the domain and adding them back in again.
Not worried about migrating any other SBS 2011 features otherwise such as Exchange 2010 as I'm moving them onto Office 365 Hosted Exchange.
The technet articles seem to be a bit hazy as it mentions using a migration tool which doesn't exisit on the 2012 R2 DVD.
I've gone ahead and installed 2012 R2 Essentials on the new box and joined it to the existing SBS domain so far.

My question is do I need to uninstall Exchange 2010 from the old SBS still? and should it be just a case of moving the FSMO roles onto the newly installed 2012 R2 essentials Server and DCPROMO the old SBS once I'm ready?
LVL 1
CRL ltdAsked:
Who is Participating?
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:
Note that 2012 and 2012 R2 are considered two different versions. That includes migration documentation. There *is* 2013 R2 migration docs on TechNet, and they cover when to uninstall exchange and how to handle the FSMO roles to keep essentials happy. The essentials post-installationn wizard transfers the roles automatically as I recall in 2012?R2, and skipping that wizard will certainly cause other issues. But if you find and follow the R2-specific docs, you'll be fine.
0
Tony GiangrecoCommented:
Yes, I performed a migration last year for a client with Windows Server 2003 SBS migrating to a Windows 2012 R2 Essentials Server (See Steps below).  Migrating to from SBS2011 should follow just about the same process. You should check the documentation on Microsoft's site but he steps below should be a good start.

The SBS 2003 was the domain server like normal. I setup the 2012 server and joined the same domain and joined it to the domains active directory in the normal manner. after that, I copied the users shares, setup DHCP, uninstalled DPCP on the old server, updated the DNS and a few other settings on the server and workstations and kept the users going.

Now that was a fast run through of the migration process, but there are many migration documents available.

Here is a copy of the steps I went through on that migration. Keep in mind, you may need to made modifications based on your network, applications running and other special items installed on your 2003 server.

1.      Install Windows Server 2012 on new server in network and cancel Configuration Wizard.

2.      Set Server 2012 Time, Date, Time zone, and Stop all other updates.

3.      Start > Run type ncpa.cpl, right click the network connection. Select properties, configure static IPv4 addr. Use the 2003 IP address for DNS and verify they can ping each other.

4.      Update 2003 server pw for 2012 complex requirement

5.      Leave Windows 2012 server in a workgroup
6.      On 2003 server, backup all application SQL databases.
7.      Run final full backup of SBS2003

8.      On SBS 2003, in AD Domains & Trusts, raise Forest Functional & Domain Functional levels to 2003

9.      On 2003, admin.. tools, server mgmt, Internet & Email, Configure remote access – starts remote Aces wizard, select Disable Remote Access, wizard changes config.

10.      Restart and check DHCP IP scheme and scope

11.      Run Connect to the Internet Wizard
a.      Select Broadband
b.      Select I have a router with an IP addr from dropdown
c.      Add DNS names from your ISP & GW addr (router ip)

12.      Make a copy of login script C:\Windows\Sysvol\Sysvol\DomainName\scripts delete SBS_LOGIN_SCRIPT.bat to folder in root for later access

13.      Delete C:\Windows\Sysvol\Sysvol\DomainName\scripts delete SBS_LOGIN_SCRIPT.bat

14.      Delete login script from all user profiles

15.      Restart SBS server

16.      Stop and disable Remote Access in Administrative Tools

17.      Start > Run type ncpa.cpl, right click the network connection. Select properties, configure static IPv4 addr. As a DNS server, use the SBS Server IP address.

18.      Restart WINDOWS 2012 ESSENTIALS

19.      Cancel the Configure Windows Server Essentials wizard
20.      Open the Server Manager (not Dashboard!) and select Add roles and features.
21.      In the Add Roles and Features Wizard, install the Active Directory Domain Services role.
22.      Restart the WINDOWS 2012 ESSENTIALS Server.
23.      On the Configure Windows Server Essentials wizard, press Cancel again and start the Server Manager again.
24.      From Server Manager > Notifications (up right corner) run Promote this server to a domain controller task.
25.      With wizard open, on 1st page select Add a domain controller to an existing domain and enter SBS admin pw. When you confirm, Domain field will fill automatically. Click Next.
26.      Next enter DSRM pw (complex) be careful to check the checkbox of the DNS server! Click Next.
27.      Clear the checkbox on Update DNS delegation and click Next.
28.      In the next few steps click Next. In the Review Options check that all options are OK, click Next once again.
29.      In Prerequisites Check step, you will receive some warnings - not serious. Ready to promote Windows 2012 Essentials as an 2nd DC in SBS domain. Click Install.
30.      During installation, domain schema & forest schema will be automatically upgraded & could take a while. After installation, server will restart.
31.      Logon to the server with the SBS admin domain credentials.
32.      Complete the Configure Windows Server Essentials wizard.
33.      My suggestion: Install DHCP server on WINDOWS 2012 ESSENTIALS. Don’t use router as DHCP server. Check forwarders in DNS server. You have to use only the ISP DNS servers as forwarders or, if you prefer, you could not use any forwarder.
34.      Now WINDOWS 2012 ESSENTIALS is added a 2nd DC in SBS domain. 21 days to complete migration
35.      Run Power Shell Scripts below to Transfer FSMO roles  
36.  Test the network. I suggest waiting a few days before removing the the old server from the domain and shitting it down just in case you find something was missed.

Hope this info helps!
1

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Tony GiangrecoCommented:
Here is an article on how to demote the old server and take it out of the network.

http://terrytlslau.tls1.cc/2012/03/domain-controller-demotion-on-windows.html

I looked back into my notes on that migration and I have to give credit to most of those steps to this Microsoft page.  At that time, I reviewed a ton of migration articles and created a combination of many sites to create one for myself.

On this site, there are multiple Migration Process Summary pages from which I copied steps from to make my condensed plan.

https://technet.microsoft.com/en-us/library/jj200112.aspx

Don't forget, that was from 2003 to 2012. you many need to modify the script.

Hope it helps!
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
SBS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.