Join David Elfassy for an in-depth discussion in this video Verifying an installation of Exchange Server 2013, part of Migrating from Exchange Server 2010 to 2013.
- Through the magic of video, we've started out with an organization that had just Exchange Server 2010 and I've actually deployed an Exchange 2013 server into this organization. We're not going to go through the set up steps of deploying an Exchange Server 2013 server because that's a whole other course and this course really is focused on migrating from Exchange 2010 to Exchange 2013. So I've deployed the server. Took quite a bit of time, but it's really not a very complex task. What's important is that once the Exchange Server 2013 server has been deployed, that we need to verify that that installation function correctly.
So there's various steps that I perform after I install an Exchange server to verify that all of the installation performed with success. One of the things that I'm going to do is I'm going to go into PowerShell and just verify that my server is integrated fully into the organization. To do that, I'm just going to run the get-exchangeserver command. When I run the get-exchangeserver command, I actually get the same result of what you see behind in the Exchange admin center. Now note that the Exchange admin center in the background runs PowerShell commands.
When you are performing various tasks from the Exchange admin center, you're actually modifying objects in your act of director database and objects in your Exchange databases by using PowerShell. So a little tip here when you're using PowerShell and you don't always know exactly what the command is that you want to type. You know where you're going in terms of you know what type of object you want to modify, but you don't know the exact syntax, the best thing to use always is the tab complete.
I want to get information about logons. Well I can do get-logon, but I'm sure that's not the command. If I just press tab, then I see that these commands are auto-completing. If I press tab multiple times and there's multiple commands that start with Get-Logon, I will cycle through all of those available commands. Let me show you the same thing with get-mailbox. If I type mail and then I type the tab key, I go through Get-Mailbox, there's also other commands that start with Get-Mailbox.
So just by, you don't see this, but I'm pressing the tab key, I'm cycling through all of these Get-Mailbox options. The one I actually want to get to is Get-MailboxDatabase. This one will list all the databases that I have on my Exchange server. Note that it's only showing me the databases that I have on my Exchange 2013 server. That's because I cannot manage my Exchange 2010 databases from my Exchange 2013 server. So I know that my database has been created correctly, I know that my server has been integrated properly into my Exchange 2010 organization.
One of the next things that I want to verify is am I able to send an email from a user in my Exchange 2013 server to a user that has a mailbox on the Exchange 2010 server. So to do that, I'm going to log on to Outlook Web App. So I've logged into Outlook Web App and I'm going to try to send an email to another user. When I click on new email, I know that I have a username Michael, but I don't remember his last name. Just going to type Michael and do a control k, just like I'm able to do in Outlook.
Outlook Web App has recognized that there's a user named Michael Jones in my organization. So I'm going to say, hello, Michael. I'm going to click send. Now again, through the magic of video I'm going to go into Outlook Web App for Michael Jones and go verify that he's received that email. Now I'm in the Outlook Web App version of Michael Jones' mailbox.
So I see that I received an email from John Smith, so obviously my communication between my mailboxes that are on my 2013 server and my mailboxes that are on my 2010 servers is working just fine. The server was integrated into the organization properly, I'm able to exchange mail between users, and I can see both servers from the management tools. So now that we've verified that the organization is integrated and is a hybrid co-existence organization between Exchange 2010 and Exchange 2013, we can move on to the next steps of configuring our 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