[2 days left] What’s wrong with your cloud strategy? Learn why multicloud solutions matter with Nimble Storage.Register Now

x
?
Solved

WIndows 2008 SBS MIGRATION

Posted on 2013-05-30
4
Medium Priority
?
620 Views
Last Modified: 2013-05-30
Hello,

My present environment:
Single server Windows 2008 SP2 SBS, 25 users,
Exchange is not used in the SBS since we migrated to Office 365 some monthes ago

We need to add a new Windows 2012 standard edition server. AD will me migrated also
We will keep the SBS 2008 server online, but all data will be migrated to the new Windows 2012 server. SBS will become a spare server for AD replication

QUestions:

Is WIn 2012 similar to Windows 2008 regarding installation and migration of AD?
WIll I have to migrate to 4 FSMO roles to 2012? what will happens if I do not do it?
Would I be able to keep W8K SBS as a second AD after migrating FSMO roles?

I do want to migrate AD to the new server 2012 but I do NOT want to migrate all specific SBS GPOs , Scripts, ect...is it possible?

Is there a document describing this migration ?

Thank you
0
Comment
Question by:gadsad
[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 59

Expert Comment

by:Cliff Galiher
ID: 39206903
Your questions, each in order:

Yes, 2012 is similar to 2008. AD replicates and thus, if done appropriately, can be migrated.

If you plan on keeping the SBS server online (which I do not recommend given your planned environment) then you *CANNOT* migrate any of the FSMO roles. SBS licensing still applies and you must keep them on the SBS server.

Given that you are not using Exchange and will need to buy Server 2012 CALs anyways, I see no benefit to keeping SBS 2008 online at all though, so you'd be better served retiring it.

Yes, you *can* keep the SBS 2008 server as a second AD server, but NOT after migrating the FSMO roles. The only way to have two or more domain controllers in an SBS domain is to keep the FSMO roles where they are. The 2012 server can be a second DC and can be a global catalog server.

It is not possible to "migrate" (or more accurately replicate) Active Directory to a new domain controller and NOT have the GPOs and any associated GPO scripts replicate as well. They are a part of Active Directory and therefore will replicate with the rest of it. You don't get to pick and choose.

There is no documentation describing such a migration that is encompassing and SBS specific. The standard ADDS documentation is about what you are looking at, and except for keeping the licensing limitations of SBS 2008 in mind, the enterprise documentation is what you will want to reference.
0
 

Author Comment

by:gadsad
ID: 39206924
Thank you for your prompt answers

If I decide NOT to migrate FSMO roles and keed them on the SBS box, both AD servers will be OK without time limitation?

What is the limitation or drawback of keeping the FSMO roles on the SBS box?

Will I be able, after adding the 2012 AD box, to manually disable or delete specific SBS GPO and rules?

THank you again
0
 
LVL 59

Accepted Solution

by:
Cliff Galiher earned 2000 total points
ID: 39206937
As long as you stay within the SBS licensing guidelines (all FSMO roles stay on SBS, no cross domain trusts, no child domains, etc) then yes both AD servers will be okay and there are no time limits.

Keep in mind that SBS CALs do *not* cover 2008 R2 or 2012 Servers though, so you must buy new CALs regardless of whether you keep SBS or not.

There is no real limitation to keeping the FSMO roles on the SBS server. The drawbacks are a reduced amount of resiliency, but that is true already since SBS already holds all roles.

Yes, you can manually edit or disable specific group policies. You can do it now, before joining the 2012 server. You can do it after joining the 2012 server. Doesn't really matter. SBS doesn't care. They were created at install time, but there is no enforcement there. AS always, edit with care though. It is rather inconvenient to lock yourself out of your servers because of a bad edit. In most cases, while the GPO's have "SBS" in their names, they are best practice group policies that most sysadmins would end up enabling on their own anyways.
0
 

Author Closing Comment

by:gadsad
ID: 39206945
Thank you very much
Everything clear now for me
0

Featured Post

Visualize your virtual and backup environments

Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.

Question has a verified solution.

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

For anyone that has accidentally used newSID with Server 2008 R2 (like I did) and hasn't been able to get the server running again because you were unlucky (as I was) and had no backups - I was able to get things working by doing a Registry Hive rec…
This article provides a convenient collection of links to Microsoft provided Security Patches for operating systems that have reached their End of Life support cycle. Included operating systems covered by this article are Windows XP,  Windows Server…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…
This tutorial will walk an individual through the process of installing the necessary services and then configuring a Windows Server 2012 system as an iSCSI target. To install the necessary roles, go to Server Manager, and select Add Roles and Featu…

649 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