How to introduce a Windows 2012 R2 server into a Windows 2008SBS environment.

Hello,

I am prepping to migrate an SBS 2008 to a Windows 2012R2 (DC/File Share/Print Services) + Windows 2012R2 (Exchange 2013).

My first phase requires me to introduce Windows 2012 R2 to the domain.  Then to make it an additional domain controller.  I have some questions.

1.I understand that once Active Directory roles have been moved to the Windows 2012 server, SBS will start complaining and will start shutting itself down.  
 At which point would it start doing this?  
 I plan on moving AD related roles AFTER Exchange 2013 is in place and all dependencies have been moved over.  
 In order to begin the Exchange 2013 process, is there anything I should or should not do when I add the Windows 2012R2 to the domain & add it as an additional domain controller?

2.I understand I will need to run adprep /forestprep and adprep/domainprep before I can promote the Windows 2012R2 server as a domain controller.  Is this correct?

Any additional gotchas or guidance would be greatly welcome.

Thanks,
Rudy
realtimerAsked:
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.

David Johnson, CD, MVPRetiredCommented:
Cliff GaliherCommented:
1.I understand that once Active Directory roles have been moved to the Windows 2012 server, SBS will start complaining and will start shutting itself down.  
  At which point would it start doing this?

Moving the FSMO roles can be the very last thing you do before decommissioning SBS. So I'd do it as late in the game as possible, so the countdown is a non-issue.
 
I plan on moving AD related roles AFTER Exchange 2013 is in place and all dependencies have been moved over. In order to begin the Exchange 2013 process, is there anything I should or should not do when I add the Windows 2012R2 to the domain & add it as an additional domain controller?

Make a backup. Always make a backup. Also, I hope you don't plan on installing Exchange on your additional DC. The choice of wording makes that ambiguous, but hinting that you may be considering it. DON'T.

 
2.I understand I will need to run adprep /forestprep and adprep/domainprep before I can promote the Windows 2012R2 server as a domain controller.  Is this correct?

The 2012 wizard will do this for you. While technically that process will still be run, you no longer need to do so manually. Simply run the wizard.

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
realtimerAuthor Commented:
Cliff - thanks for your clear structured response.  

Yes, I am planning to move FSMO roles right at the end.  I understand then that it is at this time that SBS will start complaining, and not when the new Windows 2012 is promoted to DC role, correct?

Yep.  I'll ensure we have a good image backup and additional System State backup in place.

No, there will be a separate Windows 2012 R2 that will be setup with Exchange 2013.

Thanks!!
Your Guide to Achieving IT Business Success

The IT Service Excellence Tool Kit has best practices to keep your clients happy and business booming. Inside, you’ll find everything you need to increase client satisfaction and retention, become more competitive, and increase your overall success.

Cliff GaliherCommented:
Correct. As long as you don't create a child domain, or any type of cross-domain trust, and don't move the FSMO roles, you can keep an additional DC on SBS indefinitely. This is perfectly acceptable both legally and technically.
it_saigeDeveloperCommented:
A couple of things that were not touched upon.

First, ensure that your current environment does not have any problems, run a DCDIAG and FRSDIAG (especially the FRSDIAG as it is extremely common for the FRS database in 2003/2008 to become corrupted).

A corrupted FRS database will not prevent the process of promoting the new server to a DC from running, but it will prevent the process from completing properly.  This is because the new server will not be able to complete a replication cycle which is a fail-safe used by AD to ensure that a server can act as a domain controller.

Secone, ensure that you make your new server a Global Catalog.

-saige-
realtimerAuthor Commented:
Thank you very much!!
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
Exchange

From novice to tech pro — start learning today.