In the sixth part of our Exchange lab series we:
In the final part of our Exchange lab series we:
- Move test users via the Exchange Admin Center
- Move test users via PowerShell
- Outlook on the Web (formerly Outlook Web App)
Let’s get started!
Move test users via the Exchange Admin Center
Now that we have our database situated let’s move some users.
Log in to the Exchange Admin Center and select Migration from the Recipients tab.
Select the New () button then Move to a different database.
On the New Local Move Request dialog we can either select the user we want to move from a directory lookup or, we can import those users from a CSV file. For this example, we will just pick a couple of users from the directory. In this case, pick Select the users that you want to move and click the Add () button.
On the Select a Mailbox dialog, pick the mailboxes you wish to move. Then click Add. To remove a mailbox click the [remove] link to the right of its name. Once you have all the desired mailboxes click OK.
In our example, we will just be moving two users but you can select as many as you like.
On the Move Configuration screen, give your migration batch a descriptive name. This will help you identify it later. On this screen, you can also identify whether you want to move just the primary mailbox, just the archive mailbox, or, both. In our case, we will keep everything together and select Move the primary mailbox and the archive mailbox if one exists. As you can see from the description this option is fine even if your users do not have an archive.
You can also specify a target primary mailbox database and target archive database by clicking the respective Browse button. In our lab, this will only yield one resulting database so selecting this is redundant. If you had multiple databases and left these fields blank Exchange would do its best to balance the mailboxes evenly between the databases.
Bad item limit determines how many corrupted items you are willing to accept during the move. The default is 10. I often set this as high as 100.
On the Start the batch screen, click the Browse button to select which recipients will receive a report via email when the batch is complete.
You can also set whether to Automatically start the batch right away, or, Manually start the batch later. The latter is useful if you don’t want to start moving as soon as you complete the wizard.
You can also choose to Automatically complete the migration batch which will cut the user over to the new server as soon as their data copy completes. Otherwise, if you select Manually Complete the batch the migration performs the initial seed of the mailbox but keeps the user checking in to the old server until you choose to finalize the move.
In our lab, we will set these both to automatic.
When ready click New.
From the migration tab, you can monitor the progress. You can also stop and delete a move. For more details click the View Details link under Mailbox Status. The View Details dialog allows you to download a migration report for each user. This report is especially useful for troubleshooting purposes.
When the move is finalized the status column will show as Complete.
Move test users via PowerShell
If you prefer to move users with PowerShell we utilize the New-MoveRequest cmdlet. For example, to move a single user we could simply type the following:
C:\> New-MoveRequest -Identity "Rory Williams"
In this command user, Rory Williams is moved to a database on Exchange 2016. Without the target database parameter set Exchange will balance the mailbox between any available 2016 databases in the environment, irrespective of where the command was actually run. That said, Rory could be balanced to a database on an entirely different 2016 server. If you need a little more control over the destination then you can use the -TargetDatabase parameter. For example:
C:\> New-MoveRequest -Identity "Rory Williams" -TargetDatabase "Doctors Companions"
If the request is accepted we will receive the below response.
C:\> New-MoveRequest -Identity "Rory Williams" -TargetDatabase "Doctors Companions" DisplayName StatusDetail TotalMailboxSize TotalArchiveSize PercentComplete ----------- ------------ ---------------- ---------------- --------------- Rory Williams Queued 119.5 KB (122,360 bytes) 0
To check the status of the move we could just run Get-MoveRequest.
C:\> Get-MoveRequest DisplayName Status TargetDatabase ----------- ------ -------------- Rory Williams InProgress Doctors Companions Rose Tyler InProgress Doctors Companions
I prefer a little more detail. You can get this by piping Get-MoveRequest to Get-MoveRequestStatistics.
C:\> Get-MoveRequest | Get-MoveRequestStatistics DisplayName StatusDetail TotalMailboxSize TotalArchiveSize PercentComplete ----------- ------------ ---------------- ---------------- --------------- Rory Williams InitialSeeding 119.5 KB (122,360 bytes) 0 Rose Tyler InitialSeeding 41.18 KB (42,165 bytes) 0
To get a detailed report we would add the -IncludeReport parameter. This is great for troubleshooting a move request, or, to see what is going on under the hood. The output of this parameter can be quite lengthy so I will skip posting that here. But, definitely check it out.
C:\> Get-MoveRequest "Clara Oswald" | Get-MoveRequestStatistics -IncludeReport | fl
Note: There is a lot more to the New-MoveRequest command than we give credit. You can certainly get creative when piping it with other commands. We’ll be sure to cover New-MoveRequest in greater detail in a future article. For more information on New-MoveRequest check out this article from Microsoft.
Outlook on the Web (formerly Outlook Web App)
If you are an Office 365 user then the new Outlook on the Web might have a striking resemblance to what you have seen in the cloud. Using one of your migrated users let’s log into Outlook on the Web and take a quick peek at what has changed.
Note: This is a really good time to test mail flow between the users you just moved to Exchange 2016 and the legacy servers in your lab.
The URL is still the same. In our case, we point our browser to https://webmail.exchangeservergeek.com/owa. We will log in as Clara Oswald.
As you can see the interface looks much more feature-rich. Let’s take a closer look.
It looks like Clara received an email from Martha. Martha is still on Exchange 2013. Martha posted a link to a YouTube video in her email. To Martha, all she saw was the link. But Clara gets a rich snippet of the video. Not only does it pull the title and description from YouTube, but it also pulls a thumbnail. Rich snippets work on any web content, whether it be a blog post, or, a product page from a retail site.
When Clara clicks on the video it launches right from within Outlook on the Web instead of navigating her away and interrupting her workflow.
Clara hits the inline reply button and sends a promotional poster back to Martha. The responsive design of Outlook on the Web means the image will look great on any screen size. This eliminates any unnecessary scrolling. If Clara increases the size of her browser window the image stretches until it reaches its original size.
With side by side view, you can review a document while you collaborate in an email. In this screenshot, Amy and Clara are reviewing a t-shirt design.
Navigation in Outlook has also shifted from the top-right to the top left of the screen. You will recognize this navigation style from Office 365 and Outlook.com. This bar will populate as you add more apps to your on-premises solution.
The options screen has been massively redesigned. Should you prefer the old options click OTHER at the bottom left.
Outlook on the Web is a massive improvement over its predecessors. The interface is faster, more responsive and, more feature-rich. Outlook on the Web could entice a subset of users towards the web client eliminating the need for a costly Office desktop license.
Note: We barely scratched the surface of Outlook on the Web. We will be sure to cover it in greater detail in future articles.
Where do we go from here?
That is it for this series. You have accomplished a great deal. Congratulations!
But, this is only the beginning. There is still plenty more to discover. More buttons to press. More commands to run. Stick with us and let’s explore Exchange 2016 together.
Be sure to check out our other Exchange 2016 articles.
- What Ignite taught us about Exchange 2016
- Create an IP-less DAG (No Administrative Access Point)
- Exchange 2016 public preview released
Join the conversation on Twitter @SuperTekBoy.