Solved

2003 SBS to 2012 Standard

Posted on 2013-06-26
4
547 Views
Last Modified: 2013-06-27
Hello,

   I had a previous question answered regarding a client migration I'm doing. I'm doing some testing with VMs of the client servers in my test network for the migration in a few months.

I've read some conflicting instructions and I'm hoping someone can clear up the confusion.

The 2003 SBS box is running at the 2000 forest and domain functional levels. I had to raise them to the 2003 to allow the 2012 box to join as a DC. The only change I made was in the AD Users and Computers and the AD Domains and Trusts on the 2003 SBS box. I right-clicked and selected to raise both levels to 2003. After that, it allowed me to DCPROMO the 2012 Standard box. It appears to have worked,  but now I'm reading that I should've run ADPREP to upgrade the schema before even promoting the 2012 to a DC.

http://blogs.technet.com/b/infratalks/archive/2012/09/07/transition-from-small-business-server-to-standard-windows-server.aspx

I'm just curious if this is the case for the upgrade process? If so, have I already made a mistake in running the DCPROMO on the 2012 box? The SBS 20003 box is running exchange, which will be going away as they are transitioning to Office 365. I have read several articles on that and everyone recommends uninstalling exchange and then DCPROMOing the 2003 SBS box out of the network.

Any help would be greatly appreciated. Thank you!
0
Comment
Question by:Jharrisonsnbs
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
4 Comments
 
LVL 58

Accepted Solution

by:
Cliff Galiher earned 500 total points
ID: 39279639
Well, first we'll get something simple out of the way. That blog post was written for 2008 R2, not 2012. And in 2012, things have changed significantly.

Now for the slightly more complicated part, because your question implies something that can't be correct.

In 2012, there is no more dcpromo. In fact, if you try that command, it will kindly tell you to use server manager instead. So when you say you successfully dcpromo'ed 2012...that leaves me wondering what you've actually done.

Now if I were to speculate, and guess that you succeessfully added the ADDS role, then you are fine. The 2012 role wizard runs the schema updates as part of the role process. ADPrep is no longer a required added step. Which illustrates why using a 2008 R2 blog post would cause you problems.

For future reference though, even in 2008 R2 you wouldn't have broken anything. If you run dcpromo on 2008 R2 and you have *not* run ADPrep yet, dcpromo fails. So a domain controller can only be promoted if the schema is up-to-date. In older OSes that was a manual step. In 2012, it is automated as part of the role.

So in summary:

In 2012, there is no dcpromo.
In 2012, there is no need for ADPrep.
Since 2003, the DC process checks the schema before promoting, so you can't inadvertently break things.
0
 

Author Comment

by:Jharrisonsnbs
ID: 39279998
cgaliher,

    Yes, I did see that it was for 2008, but I saw the blurb in the first paragraph about this article being applicable to 2012 as well as 2008. It was wrong to assume on my part.

"These steps are applicable for transition from all the versions of Small Business Server to Windows Server 2008/ 2008 R2/ 2012."

Yes, I did add the ADDS role and after that finished, I ran the "Promote this server to a domain controller. Haven't had much experience with 2012 and saying 'DCPROMO' is a force of habit.

Followed this article:

http://social.technet.microsoft.com/wiki/contents/articles/12370.step-by-step-guide-for-setting-up-windows-server-2012-domain-controller.aspx

So, the prep is now handled by 2012 when you install the role? When I'm ready to decommission the 2003 box, I should just be able to transfer the FSMO roles off that to the 2012 DC, remove exchange from the 2003 box and remove it from the domain, correct? Just want to make sure I'm not missing any steps. Thank you!
0
 
LVL 58

Assisted Solution

by:Cliff Galiher
Cliff Galiher earned 500 total points
ID: 39280028
Mostly correct. Remove Exchange *before* doing any other DC changes though. Exchange really doesn't like things disappearing out from under it (including FSMO roles) and can cause the uninstall to fail.
0
 

Author Comment

by:Jharrisonsnbs
ID: 39281119
Got it. Thank you so much for the help!!!
0

Featured Post

Free eBook: Backup on AWS

Everything you need to know about backup and disaster recovery with AWS, for FREE!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Last week, our Skyport webinar on “How to secure your Active Directory” (https://www.experts-exchange.com/videos/5810/Webinar-Is-Your-Active-Directory-as-Secure-as-You-Think.html?cid=Gene_Skyport) provided 218 attendees with a step-by-step guide for…
This article demonstrates probably the easiest way to configure domain-wide tier isolation within Active Directory. If you do not know tier isolation read https://technet.microsoft.com/en-us/windows-server-docs/security/securing-privileged-access/s…
This tutorial will walk an individual through the process of configuring basic necessities in order to use the 2010 version of Data Protection Manager. These include storage, agents, and protection jobs. Launch Data Protection Manager from the deskt…
Are you ready to implement Active Directory best practices without reading 300+ pages? You're in luck. In this webinar hosted by Skyport Systems, you gain insight into Microsoft's latest comprehensive guide, with tips on the best and easiest way…

752 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question