This website is originally written in the Czech language. Most content is machine (AI) translated into English. The translation may not be exact and may contain errors.
Migrating Exchange organization 2010 to 2016
I was migrating an organization from Exchange Server 2010 to Exchange Server 2016. The whole process was quite demanding and long (it took me 4 months even with my studies). In the process, I came across a number of problems, errors and shortcomings (even in the official documentation). I am creating this series from my notes. This is not a complete guide to the transition, but highlights and mentions of issues I encountered. Individual articles describe different areas of Exchange Server 2016, so it is not only a transition from an older version, but also suitable for a new installation or administration.
Exchange Server 2016 Namespaces - service addresses
Before deploying an Exchange server, or migrating from an older version, it is a good idea to plan the internal and external addresses (names) for each service used. Today it is best to simplify and unify the addresses as much as possible, in the extreme to a single domain name. Similarly, we should plan at the outset how many Exchange servers we will deploy and how they will be distributed across sites.
07.03.2019 | Samuraj - Petr Bouška | Microsoft admin | 8 602x | Comments [2]
Exchange Server 2016 installation and basic configuration
It doesn't matter whether we are performing a new Exchange Server deployment or migrating from an older version, we always perform a clean installation of the new server. We have to meet some prerequisites and requirements. The actual installation is then simple using a wizard. In Exchange 2016, everything has been simplified again, because we only have two roles (and the second one is the Edge server), so the installation is quite uniform.
13.03.2019 | | Microsoft admin | 19 714x | Comments [6]
Exchange Server 2016 Database Availability Group
Electronic mail has long been an important communication channel for companies. Therefore, we need to ensure high availability of this service. The solution is to deploy multiple servers and deal with their redundancy, i.e. actually create a cluster. The Database Availability Group technology that came with Exchange 2010 helps us to do this. This technology creates passive copies of the mailbox database, replicates its contents and allows you to switch activity to the copy.
17.03.2019 | | Microsoft admin | 14 526x | Comments [0]
Exchange Server 2016 Client Access
On Exchange Server 2016, the Client Access services is part of the Mailbox server (it is no longer a separate role). It provides authentication and proxy services for internal and external client connections. The client can connect to any Mailbox server, and the request is proxied to the server where the database for its mailbox is active. In some cases, it can redirect to another server. Access is possible in different ways and protocols, for example from Outlook, a mobile device or a web browser.
27.03.2019 | | Microsoft admin | 16 486x | Comments [10]
Exchange Server 2016 Mail Flow - Mail Routing and Connectors
Mail is transferred between servers within the organisation, but also externally across the Internet and to other organisations, using the Simple Mail Transfer Protocol (SMTP). The transfer and routing of mail is referred to as Mail Flow. Exchange uses the Transport Pipeline, which is a collection of services, connections, components and queues. The objects that we need to configure in order to transmit mail are primarily Receive Connectors and Send Connectors.
03.04.2019 | | Microsoft admin | 19 284x | Comments [1]
Exchange Server 2016 DSN, Message Tracking and Messaging Analytics
In practice, we often need to confirm that a message has been delivered, or look for problems as to why it has not been delivered. Last time we set up Protocol Logging and Message Tracking. Now let's see how to use these logs for tracking message delivery and Troubleshooting. Unfortunately we no longer have the Tracking Log Explorer so we have to use the Exchange Management Shell.
15.04.2019 | | Microsoft admin | 23 211x | Comments [0]
Exchange Server 2016 Public Folders coexistence
If we are migrating from Exchange 2010 to Exchange 2016 and we are using Public Folders (PF), we need to set up public folder coexistence before moving the first mailboxes. Otherwise the folders will not be available to the migrated users.
07.05.2019 | | Microsoft admin | 7 860x | Comments [0]
Exchange Server 2016 moving mailboxes and OAB
When migrating an Exchange server from an older version, one of the essential steps is to move (or migrate) mailboxes from the original server to the new one. We must have services running on both the original and the new Exchange server that are members of the same organization. Then we can move the mailbox group to the database on the new server.
12.05.2019 | | Microsoft admin | 13 400x | Comments [0]
Exchange Server 2016 Public Folders and their migration
Since Exchange 2013 we have Modern Public Folders, which are stored in special mailboxes inside the standard Mailbox Database. We will briefly describe the properties of these public folders and then we will look at migrating Legacy Public Folders from the old 2010 server to the new one.
24.05.2019 | | Microsoft admin | 11 969x | Comments [0]
Exchange Server 2016 removing version 2010 servers
The moment we have migrated mailboxes, public folders and services to new servers. All traffic is routed to Exchange 2016 and we have done sufficient testing that everything works. We can proceed to decommission the original Exchange 2010 servers. The servers must be removed correctly, i.e. Exchange must be uninstalled.
07.06.2019 | | Microsoft admin | 7 230x | Comments [0]
Exchange Server 2016 migration from version 2010
In previous articles we have discussed the different areas of migrating from an older version of Exchange Server to a new one. Now we will bring everything together for a comprehensive (but concise) migration procedure. The basic idea of migrating from Exchange Server 2010 to 2016 is pretty simple, but the more complex the environment, the more challenging the migration. We install new servers into an existing organization. On them we will create databases, configure services and move mailboxes. The migration can be done on the fly, when the coexistence of the old and new versions will work for some time.
10.06.2019 | | Microsoft admin | 9 720x | Comments [2]
Outlook connection issues on Exchange 2016 (ThrottlingPolicy)
After switching to Exchange 2016, I had a problem for a long time that sometimes MS Outlook 2016/2019 could not connect to Exchange Server 2016 on the same local network. If I let it run, it would connect after some time (estimated 10 minutes). This problem occurred if Outlook ran correctly, then closed and restarted repeatedly. Or if the user was switching between different networks (wired and wireless) with Outlook running. Eventually I found that this was probably caused by the RcaMaxConcurrency limit, which defaults to 40.
28.07.2020 | | Microsoft admin | 9 523x | Comments [0]