Join David Elfassy for an in-depth discussion in this video Preparing the Exchange Server 2010 organization, part of Migrating from Exchange Server 2010 to 2013.
- When thinking about migrating from Exchange Server 2010 to Exchange Server 2013, the most important thing to start with is preparations. We really need to prepare appropriately for our migration to ensure that the experience will be smooth both for the administrators and for the end users. We wanna minimize the impact on the users as much as possible. The assumption for most migrations to Exchange 2013 is that there will be a period of coexistence. Coexistence between 2010 and 2013 will mean that the two environments will have to live together harmoniously on the network.
So let's first start with a very high-level approach of what steps you will have to perform in order to have that smooth coexistence in migration to 2013. First, we'll have to prepare the infrastructure. And in this course, we'll discuss all the steps that are required to prepare the infrastructure to ensure that you can introduce Exchange Server 2013 on the network. Preparing the infrastructure means preparing things from Active Directory to Exchange 2010 to your client computers. Lots of things need to be done. Then once we've prepared the infrastructure appropriately, we'll be ready to deploy Exchange Server 2013.
Now, when I say deploying Exchange Server 2013, I'm talking about everything from the installation to all the configurations that are required. And don't worry, we'll discuss all those things in this course. Then, we'll perform some client re-directions. That's right, before we move our data from 2010 to 2013, we actually need to redirect all our client computers and all our client connectivity to Exchange 2013. Once that's done, we'll get ready to move our mailboxes and public folders. Essentially all of our data from 2010 to 2013.
And then our last step will be to remove 2010 from the network. It sounds straightforward, but there's actually a lot of configuration steps that need to be done. The important thing here is that they need to be performed in the correct order. So, what are we gonna need to modify on our network? Well the first thing we're gonna do is we're gonna have to prepare Exchange Server 2010. And to do that, we'll have to make sure that our organization is completely clean of Exchange Server 2003 servers. 2007 and 2010 servers can coexist with 2013, but Exchange Server 2003 servers, which are no longer in support by Microsoft, cannot coexist with 2013.
So if you still have those old legacy servers, you need to completely remove them from your network. And removing them from your network doesn't only mean removing the physical servers from the network, but also removing references of those servers from your Exchange organization. Then we'll need to install the latest Exchange updates on Exchange 2010 servers. And that means Service Pack 3. Active Directory will have to be prepared as well. When you're getting ready to install Exchange Server 2013, you will have Active Directory schema updates that will have to be applied to your Active Directory forest.
Once that's done, you need to ensure that the Active Directory schema updates have properly replicated across all domain controllers on your network. And the last thing you need to verify is your Outlook client. Now, many organizations out there are still using Outlook 2003. You need to ensure that Outlook 2003 clients are out of your network because those will not be able to establish connections to mailboxes on Exchange Server 2013. The primary reason for that is that Exchange Server 2013 no longer uses RPC client connections.
It now only supports HTTPS connections and that is a major architectural change in Exchange Server 2013 and one change that will not function with Outlook 2003. Now, although Outlook 2007 will theoretically work with Exchange Server 2013, I don't recommend you keep those Outlook 2007 clients on the network. You need to have Outlook 2010 with Service Pack 1 at least in order to connect to 2013. The reason why I don't recommend Outlook 2007 is that, even though it's officially supported by Microsoft, with the many migrations I've done, I've encountered lots of problems with Outlook 2007.
And you want to get rid of those headaches and move to Outlook 2010 at a minimum in order to minimize the impact on the users. So what should you know before you start your migration to Exchange Server 2013? Well, really, there's a lot of changes both architecturally and in functions with Exchange 2013 as opposed to Exchange Server 2010. Hopefully you're quite familiar with Exchange Server 2010, and now in your migration to 2013, there's some things that you need to prepare yourself in order to ensure that that process is going to be as smooth as possible.
First thing that you really need to know properly are certificates. Certificates have been introduced since Exchange Server 2007 as a very important element of an Exchange Server deployment. An Exchange Server 2013 that is no less important. If your Exchange Certificates are not properly configured with the proper names and the appropriate trusts, then you'll have lots of trouble in your deployment of Exchange 2013. We'll get a chance to talk about which names need to be inputted into your certificates during your certificate request later on in the course.
Client connection protocols. As I mentioned briefly earlier, client connection to Exchange 2013 no longer supports RPC. And now the Outlook clients connects over HTTPS. Well, that is a major architectural change and also means that there are some new dependencies on HTTPS for Exchange Server 2013. All the client connection protocols which connect over IMAP, POP3, Exchange ActiveSync connectivity method, Outlook, or others, really are an essential part of your client experience with your Exchange 2013 environment and you really need to understand how those works.
And of course we'll be talking about lots of them in this course. High availability was really modified in Exchange 2010 as opposed to previous versions of Exchange. The database availability groups have been an integral part of your Exchange Server deployment. And most organizations really depend on that high-availability functionality of Exchange to ensure that users don't experience any downtime during fail-overs of databases from one server to the next during maintenance periods or if you have any type of service failures or hardware failures.
So understanding the high availability components is a real important functionality of your knowledge in preparing for Exchange 2013. PowerShell. You've heard about PowerShell. PowerShell was introduced in Exchange Server with the 2007 version, and back then, if you actually tried to perform any type of management tasks from the graphical interface, you realize that most of the graphical interface wasn't even built for Exchange 2007. Little by little, as we move now to Exchange 2013, we now have a fully-functional graphical interface with, I'd say about 85 to 90 percent of the tasks that can be performed from the graphical interface.
However, there are still very important reasons to use PowerShell, and there's a lot of value in using PowerShell both to automate management tasks, but also to perform some one-off tasks that cannot be performed from the graphical interface. And we'll talk about some of those in this course. Especially in migration, we have quite a bit of PowerShell that we need to use. And of course we've got DNS. As you know, you've got a chain of dependencies in Exchange Server. Exchange Server depends on Active Directory. Active Directory depends on DNS.
If your DNS infrastructure is not stable, is not properly configured, and your names have not been chosen correctly, you will have problems during your migration, and you'll have to troubleshoot that during your migration, which means that an in-depth understanding of DNS functionalities becomes a key component of a stable Exchange Server 2013 migration.
- Building a migration task list
- Understanding Exchange Server 2013 roles
- Namespace planning
- Verifying an Exchange Server installation
- Creating mailbox databases
- Modifying DNS records
- Moving mailboxes
- Removing Exchange Server 2010 from the network