Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
?
Solved

Migrating SBS 2008 to Windows Server 2012 with Exchange 2013

Posted on 2013-05-21
1
Medium Priority
?
1,050 Views
Last Modified: 2013-07-02
I have a client who is expanding rapidly and needs to migrate from a SBS 2008 to a Windows Server 2012 STD running Exchange 2013.  

Does anyone know of any good reference guides available that focus on this migration?

Thank you in advance.
0
Comment
Question by:RJCCTS
1 Comment
 
LVL 60

Accepted Solution

by:
Cliff Galiher earned 2000 total points
ID: 39185901
You aren't going to find one. SBS migration documents were (relatively) easy to write because the architecture was necessarily limited in scope. When you get to enterprise products, things change drastically.

For example, you say the reason you need STD is because the client is expanding rapidly. That means you need to seriously consider distributing workloads. Do you run DNS on your fileserver or do you split them up? Do you run the certificate authority on your DHCP server? In an environment that heavily uses BYOD and you want to use certificate authentication, isolating the CA is a good idea.

There are dozens of combinations and moving parts and thus there is no one-size-fits-all (or even one-size-fits-most) architectures at that size. In the SBS sized world, Essentials is still the way to go and they have an official migration doc. But at larger sizes, you need to start making serious decisions about where workloads go and how many you choose to coexist based on security, I/O, CPU, virtualization, and licensing considerations.

If Essentials and its accompanying migration doc isn't good enough then you will want to migrate per-role, not a whiz-bang all-at-once migration. Like building a house, you want to blueprint your network first. Have a good idea of how many OS installs you will have (physical and virtual) and where each role will live. Then migrate one role at a time until your final network matches your blueprint.

TechNet has excellent documentation on migrating roles. You just follow each role migration individually. This includes designing and migrating Exchange. Maybe you want the CAS and Mailbox server collocated. Maybe you need to split them up. Maybe you plan to use UM. These must also be mapped, planned, and then follow the Exchange migration guidance, per role, not all at once.

I know it isn't a simple "go here" answer, but it is the most accurate one.
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

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

There can be many situations demanding the conversion of Outlook OST files to PST format and as such, there is no shortage of automated tools to perform this conversion. However, what makes Stellar OST to PST converter stand above the rest? Let us e…
This article will help to fix the below errors for MS Exchange Server 2016 I. Certificate error "name on the security certificate is invalid or does not match the name of the site" II. Out of Office not working III. Make Internal URLs and Externa…
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…
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…
Suggested Courses

578 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