Home » Exchange Server » Installing Exchange Server 2016

Installing Exchange Server 2016

After you’ve prepared a Windows Server with the Exchange Server 2016 pre-requisites you can proceed with the installation of Exchange Server itself.

In this tutorial we’ll cover:

  • Preparing Active Directory for Exchange Server 2016 installation
  • Installing the Exchange Server 2016 Mailbox server role on a new server

Before you start there are a few things to be aware of:

  • Installing Exchange Server 2016 requires an Active Directory schema update. We’ll look at that in more detail shortly.
  • Aside from the schema update installing Exchange Server 2016 makes other irreversible changes to your Active Directory forest. If you’ve never backed up your Active Directory, or you’ve never heard of a forest recovery, here’s some reading for you.
  • If you’re installing Exchange into the forest for the first time you will be choosing an organization name. The Exchange organization can’t be renamed at a later date, so choose a name you’re happy with keeping forever.

Preparing Active Directory

A new installation of Exchange Server 2016 involves applying an Active Directory schema update, as do most Exchange Server cumulative updates, as well as preparing the Active Directory domains where Exchange Server 2016 and any mail-enabled objects will be located. In an Active Directory forest with a single domain this can all be performed as one task.

The Active Directory schema update will automatically apply when you run Exchange Server 2016 setup on the first server in your environment. A Windows Server 2012 R2 server with the Exchange Server 2016 Mailbox server role pre-requisites installed doesn’t quite meet the requirements (you’ll need to add the RSAT-ADDS feature as shown below). A domain controller will have RSAT-ADDS installed already, but may also need the .NET Framework version shown below to be installed first.

Whether you’re running the schema update from an Exchange server or a separate server (some organizations do it as a separate task due to change control reasons, or because of different teams having different administrative responsibilities in the environment) then the following requirements apply:

  • The forest functional level must be at least Windows Server 2008
  • The account used to run the schema update and Active Directory preparation must be a member of Enterprise Admins and Schema Admins. These are high privilege groups I recommend you plan to remove your account from the groups when you’re done with this task. Note, if you’ve just added yourself to these groups you’ll need to log out and back in to the server for the new group membership to take effect.
  • The server you’re running the schema update from must be located in the same Active Directory site as the Schema Master. You can identify your Schema Master by running my Get-ADInfo.ps1 script, or by using the Get-ADForest PowerShell cmdlet.

Now we’re ready to run the Active Directory schema update and and preparation.

If you’ve already got Exchange Server running in your environment you can check the current Exchange schema version before applying the update, so that you can see what the before and after version numbers are.

In PowerShell run the following one-liner created by Exchange Server MVP Michael B Smith:

Note, in my example above there is no existing Exchange server installed, hence no Exchange schema version to report.

Extract the Exchange Server 2016 setup files into a folder, open a command prompt window, and then navigate to the location where the Exchange setup files were extracted.

To apply only the schema update run the following command:

After applying the schema update we can check the version number again.

To prepare Active Directory run one of the following commands. Note this will also apply the schema update if you did not perform that step already.

If you do not already have an Exchange organization you’ll need to provide a name for the organization now, for example:

If you’re installing Exchange Server 2016 into an existing Exchange organization you do not need to specify the organization name, for example:

Remember, you can’t change the Exchange organization name later, so choose a name you’ll be happy to live with forever. Also, after installing Exchange Server 2016 as a new organization you will not be able to install any earlier versions of Exchange into the same organization.

If you have additional domains in your forest that you need to prepare (any domain that will host an Exchange server or mail-enabled objects) follow the guidance on TechNet here.

Installing the Exchange Server 2016 Mailbox Server Role

The Mailbox server role contains all of the components required to run an Exchange Server 2016 server. There is also an Edge Transport role, but that is not a mandatory role and is not covered in this tutorial.

After installing the Exchange Server 2016 pre-requisites on a server you can install the Exchange Server 2016 Mailbox server role by running the following command from an elevated command prompt.

Next Steps

After setup has completed restart the server before you continue with configuring Exchange Server 2016.

Paul is a Microsoft MVP for Office Servers and Services. He works as a consultant, writer, and trainer specializing in Office 365 and Exchange Server. Paul is a co-author of Office 365 for IT Pros and several other books, and is also a Pluralsight author.
Category: Exchange Server

66 comments

  1. Sunil says:

    Hi Paul,

    If you are in a position where you have an existing Exchange 2010 deployment and are now considering a migration to a newer version of Exchange is it worth waiting for Exchange 2016 or go with a stable version of Exchange 2013?

    I am of the opinion to hold of and wait for 2016 but thought I would ask your opinion.

    Thanks,

    Sunil

  2. Michael says:

    Thank you very much for the article, Paul!

    One easy question: why doesn’t just run GUI setup and does not type any commands into PS? Is there any benefit in installing Exchange “manually” over from GUI?

    • In the command line I can type one command and sit back and let it run. Command line can also be built in to deployment scripts for automating deployment.

      In graphical mode I have to click through a wizard with many steps and questions and it takes longer. And graphical mode can’t be automated.

      So I prefer command line.

  3. Silvio says:

    Help please…

    Change TCP congestion window to size 16 within datacenter to optimize for network latency on Windows 2012 servers
    $computerVersion = [System.Environment]::OSVersion.Version;
    if(($computerVersion.Major -eq 6) -and ($computerVersion.Minor -eq 2))
    {
    $p = Get-NetTCPSetting;
    Write-ExchangeSetupLog -Info ($p);
    foreach ($a in $p)
    {
    if($a.SettingName -eq “Custom”)
    {
    $s = Set-NetTCPSetting -SettingName Custom -InitialCongestionWindowMss 16 -MinRtoMs 300 -CongestionProvider CTCP -InitialRtoMs 400 -DelayedAckTimeoutMs 10;
    $t = New-NetTransportFilter -SettingName Internet -LocalPortStart 443 -LocalPortEnd 443 -RemotePortStart 0 -RemotePortEnd 65535;
    $n = New-NetTransportFilter -SettingName Custom -LocalPortStart 0 -LocalPortEnd 65535 -RemotePortStart 444 -RemotePortEnd 444;
    Write-ExchangeSetupLog -Info ($s + ” ” + $t + ” ” + $n);
    break;
    }
    }
    }

    [11/08/2015 20:00:56.0993] [1] The following 1 error(s) occurred during task execution:
    [11/08/2015 20:00:56.0993] [1] 0. ErrorRecord: Não é possível converter ‘System.Object[]’ para o tipo ‘System.String’ necessário para o parâmetro ‘Message’. Não há suporte para o método especificado.
    [11/08/2015 20:00:56.0993] [1] The previous errors were generated by a non-critical task and will be ignored.
    [11/08/2015 20:00:56.0993] [1] Setup will continue processing component tasks…
    [11/08/2015 20:00:56.0993] [1] Processing component ‘FrontendTransport PostSetup’ (Finalizando a Instalação da função de Caixa de Correio: Serviço de Transporte de Front-End).
    [11/08/2015 20:00:56.0993] [1] Executing:
    start-SetupService -ServiceName MSExchangeFrontendTransport

      • pete says:

        I can’t read the errors either. Google translate says:

        08/11/2015 20: 00: 56.0993 ] [1 ] 0. ErrorRecord : Can not convert ‘ System.Object []’ to type ‘ System.String ‘ required for the ‘ Message ‘ parameter . There is no support for the specified method. [ 08/11/2015 20: 00: 56.0993 ] [1 ] Processing component ‘ FrontendTransport PostSetup ‘ ( Finishing the Installation Mailbox function: Front End Shuttle Service ) .

  4. Md Shaifullah Mozide Palash says:

    Hi Paul,
    You are my exchange boss. i follow you for long time and thanks a million once again for this Article

  5. Jon says:

    Greetings Paul,

    Thanks for the always great tutorials. No matter when we search for online help topics your articles always seem to appear and shed light!

    We just rolled out a new Exchange 2016 installation on a new server. We then went to configure connection filtering and discovered it only appears to be available on Edge transport servers. If that assumption is correct, we did not include on this install.

    Do we have an option to add this role or are we SOL?

  6. Milton Lopez says:

    Hi Paul. Thanks for the great articles. Since it’s 2016 I’d like to pose again the question asked some time ago by Sunil. For a small organization wishing to upgrade form a single Exchange 2010 server, would you deploy 2013 or 2016? Conventional wisdom may tell us to wait for more CUs, but some Exchange experts have called 2016 “2013 SP2”, which would seem to indicate it is a better choice.

    Your thoughts will be much appreciated, as always.

    M.

  7. Phil Goldwasser says:

    Hi Paul. I have installed three Exchange 2016 servers and I am a little confused on some of the config. When I got to Mail Flow > Send Connector I see three different send connectors. Shouldn’t I only need one? Or do I need three of everything since each server has to have the ability to send and receive email since at some point two of the three servers could conceivably fail? I am guessing that last question is correct.

    I also have an existing Exchange 2010 server that is live and I want to configure the DAG and load balancing with these three machines so when I am ready to move mailboxes to my new databases everything will be all set. Is it possible to do this?

    When I am setting my namespaces on the three servers, do I set them all the same? I would imagine that all three servers will have the same namespace set because the load balancer can at any point send the request to any of the servers.

    Amy I making sense?

    Finally, in terms of a CAS array, is there still such a thing in 2016? Or is the load balancer going to take care of all of this?

    Thanks again, and I hope to ease up on my questions to you soon! This is my biggest Exchange project and I do not foresee anything like this in the near future (thank God!)

    • Phil Goldwasser says:

      Correction, there are only two send connectors, one on my production 2010 server and one for my new 2016 servers. There are however, Receive connectors for all three of the new servers.

    • You only need one Send Connector, especially if it’s just one site. If you want some redundancy you can add multiple source Transport servers to that connector.

      There’s no CAS Array in 2016 (or 2013) like there was in 2010. Clients connect with Outlook Anywhere, even internally. So you just need to load balance the CAS namespaces (OA, OWA, ActiveSync, Autodiscover, etc). Yes they should all be the same within a single site.

      It also means all the servers can use the same SSL cert.

      Here’s some relevant articles:
      http://practical365.com/exchange-server-2016-client-access-namespace-configuration/

      http://practical365.com/exchange-2013-client-access-server-high-availability/

      • Phil Goldwasser says:

        Thanks! I had actually figured most of it out on my own already mostly from your website! I have the new 2016 infrastructure pretty much working. Email from a 2016 mailbox to a 2010 mailbox is working. Mail between databases in 2016 is working. Mail to and from the internet on both 2010 and 2016 is working, So it looks good!

        I configured the KEMP load balancer (appliance, not virtual) using their template and a tutorial that I found on the internet. That looks good, but once I changed my firewall to point to the load balancer (using a different public ip from my production email servers) I was able to browse to the sign in page in Exchange 2016, but when I enter the username and password, it just brings be right back to the login page. I changed the namespaces on all three servers using your script which worked great.

        I added the certificate to the KEMP, but I have not added to the servers. That may be the issue. I set the KEMP for HTTPS Reencypted, which means that I need to have the cert on my servers as well. What is your opinion about full SSL offloading, so that the communication between he KEMP and the email servers are not encrypted? This was my first thought, but I did not want to spend the time last night learning how to enable ssl offloading on the servers just for testing. So I will put the cert on the servers as well and see what happens. I would like to get your opinion though. SSL offloading should take a little strain off of the servers I would think?

        Thanks again!

  8. Phil Goldwasser says:

    One more thing! I promise 😉

    Suddenly when trying to start EMS on any of my servers, I am getting the following:

    New-PSSession : [fnymail2.nii.local] Connecting to remote server fnymail2.nii.local failed with the following error
    message : Access is denied. For more information, see the about_Remote_Troubleshooting Help topic.
    At line:1 char:1
    + New-PSSession -ConnectionURI “$connectionUri” -ConfigurationName Microsoft.Excha …
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
    gTransportException
    + FullyQualifiedErrorId : AccessDenied,PSSessionOpenFailed

    Then it attempts to connect to each of the other servers, including the 2010 server and fails on each of them. Finally, it gives me the opportunity to enter in the fqdn of a server, but again it fails. Have you seen anything like this? After a while, it will work again, but it is random and not specific to any of the three servers.

    The following will sometimes work in a regular PS shell (with a securestring file containing an encrypted password):

    $username = “NIIAdministrator”
    $password = cat D:Adminsecurestring.txt | convertto-securestring
    $cred = new-object -typename System.Management.Automation.PSCredential `
    -argumentlist $username, $password
    $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri ‘http://FNYMAIL1.NII.LOCAL/PowerShell/’ –Credential $cred -Authentication Kerberos

    Import-PSSession $Session -AllowClobber -DisableNameChecking | Out-Null

    This is getting to be troublesome and I want to make sure it is straightened out before going live.

  9. Darryl says:

    Thanks for a great guide. Like Andre, I cannot log into the EAC or OWA with administrator or a new user/admin credentials. EAC says username or password wrong, and OWA accepts it but gives me a blank screen.

    New 2012 R2 server with new Exchange 2016 installed. Nothing else done yet.

    I also tried using the URL to EAC that contains the server name so that the SSL would work without errors as “localhost” causes SSL errors in the browser.

    Advice why we can’t log into EAC?

    • John says:

      No one on the internet is taking the time to respond to the EMS login problems. It’s frustrating. I set up a new 2012 R2 server then installed Exchange 2016. Couldn’t log in and couldn’t find many solutions.

      I enabled Basic and Windows authentication for the PowerShell virtual directory in IIS to get EMS working.

  10. Scott says:

    HI Paul

    Thanks for a great article – I have successfull prepped the Schema and AD but get all these errors when trying to run the setup:

    C:ScottExchange>setup /Mode:Install /Role:Mailbox /IAcceptExchangeServerLicens
    eTerms

    Welcome to Microsoft Exchange Server 2016 Unattended Setup

    Copying Files…
    File copy complete.
    Setup will now collect additional information needed for
    installation.

    Languages
    Management tools
    Mailbox role: Transport service
    Mailbox role: Client Access service
    Mailbox role: Unified Messaging service
    Mailbox role: Mailbox service
    Mailbox role: Front End Transport service
    Mailbox role: Client Access Front End service

    Performing Microsoft Exchange Server Prerequisite Check

    Configuring Prerequisites COMPLETED
    Prerequisite Analysis FAILED

    This computer requires Windows Media Audio Voice Codec. Install the Media
    Foundation feature via Server Manager.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.160)/ms.
    exch.setupreadiness.LonghornWmspdmoxNotInstalled.aspx

    The World Wide Web (W3SVC) service is either disabled or not installed on this
    computer. You must exit Setup, install the required component, and then restart
    Setup.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.160)/ms.
    exch.setupreadiness.W3SVCDisabledOrNotInstalled.aspx

    The ‘IIS 7 Dynamic Content Compression’ component is required. Install the
    component via Server Manager.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.160)/ms.
    exch.setupreadiness.LonghornIIS7HttpCompressionDynamicNotInstalled.aspx

    The ‘IIS 7 Static Content Compression’ component is required. Install the
    component via Server Manager.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.160)/ms.
    exch.setupreadiness.LonghornIIS7HttpCompressionStaticNotInstalled.aspx

    The ‘Windows Process Activation Service Process Model’ component is required.
    Install the component via Server Manager.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.160)/ms.
    exch.setupreadiness.LonghornWASProcessModelInstalled.aspx

    The ‘IIS 7 Basic Authentication’ component is required. Install the component
    via Server Manager.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.160)/ms.
    exch.setupreadiness.LonghornIIS7BasicAuthNotInstalled.aspx

    The ‘IIS 7 Windows Authentication’ component is required. Install the component
    via Server Manager.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.160)/ms.
    exch.setupreadiness.LonghornIIS7WindowsAuthNotInstalled.aspx

    The ‘IIS 7 Digest Authentication’ component is required. Install the component
    via Server Manager.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.160)/ms.
    exch.setupreadiness.LonghornIIS7DigestAuthNotInstalled.aspx

    The ‘IIS 6 WMI Compatibility’ component is required. Install the component via
    Server Manager.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.160)/ms.
    exch.setupreadiness.LonghornIIS6WMICompatibility.aspx

    The ‘ISAPI Filter’ component is required. Install the component via Server
    Manager.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.160)/ms.
    exch.setupreadiness.LonghornISAPIFilter.aspx

    The ‘Client Certificate Mapping Authentication’ component is required. Install
    the component via Server Manager.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.160)/ms.
    exch.setupreadiness.LonghornClientCertificateMappingAuthentication.aspx

    The ‘Directory Browsing’ component is required. Install the component via
    Server Manager.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.160)/ms.
    exch.setupreadiness.LonghornDirectoryBrowse.aspx

    The ‘HTTP Errors’ component is required. Install the component via Server
    Manager.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.160)/ms.
    exch.setupreadiness.LonghornHttpErrors.aspx

    The ‘HTTP Logging’ component is required. Install the component via Server
    Manager.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.160)/ms.
    exch.setupreadiness.LonghornHttpLogging.aspx

    The ‘HTTP Redirection’ component is required. Install the component via Server
    Manager.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.160)/ms.
    exch.setupreadiness.LonghornHttpRedirect.aspx

    The ‘Tracing’ component is required. Install the component via Server Manager.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.160)/ms.
    exch.setupreadiness.LonghornHttpTracing.aspx

    The ‘Request Monitor’ component is required. Install the component via Server
    Manager.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.160)/ms.
    exch.setupreadiness.LonghornRequestMonitor.aspx

    The ‘Static Content’ component is required. Install the component via Server
    Manager.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.160)/ms.
    exch.setupreadiness.LonghornStaticContent.aspx

    The ‘Web-Mgmt-Service’ component is required. Install the component via Server
    Manager.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.160)/ms.
    exch.setupreadiness.ManagementServiceInstalled.aspx

    The Windows component NET-WCF-HTTP-Activation45 isn’t installed on this
    computer and needs to be installed before Exchange Setup can begin.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.160)/ms.
    exch.setupreadiness.WcfHttpActivation45Installed.aspx

    The Windows component RSAT-Clustering isn’t installed on this computer and
    needs to be installed before Exchange Setup can begin.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.160)/ms.
    exch.setupreadiness.RsatClusteringInstalled.aspx

    The Windows component RSAT-Clustering-Mgmt isn’t installed on this computer and
    needs to be installed before Exchange Setup can begin.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.160)/ms.
    exch.setupreadiness.RsatClusteringMgmtInstalled.aspx

    The Windows component RSAT-Clustering-PowerShell isn’t installed on this
    computer and needs to be installed before Exchange Setup can begin.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.160)/ms.
    exch.setupreadiness.RsatClusteringPowerShellInstalled.aspx

    The Windows component RSAT-Clustering-CmdInterface isn’t installed on this
    computer and needs to be installed before Exchange Setup can begin.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.160)/ms.
    exch.setupreadiness.RsatClusteringCmdInterfaceInstalled.aspx

    This computer requires the Microsoft Unified Communications Managed API 4.0,
    Core Runtime 64-bit. Please install the software from
    http://go.microsoft.com/fwlink/?LinkId=260990.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.160)/ms.
    exch.setupreadiness.UcmaRedistMsi.aspx

    The Windows component Web-Net-Ext45 isn’t installed on this computer and needs
    to be installed before Exchange Setup can begin.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.160)/ms.
    exch.setupreadiness.WebNetExt45NotInstalled.aspx

    The Windows component Web-ISAPI-Ext isn’t installed on this computer and needs
    to be installed before Exchange Setup can begin.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.160)/ms.
    exch.setupreadiness.WebISAPIExtNotInstalled.aspx

    The Windows component Web-ASP-NET45 isn’t installed on this computer and needs
    to be installed before Exchange Setup can begin.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.160)/ms.
    exch.setupreadiness.WebASPNET45NotInstalled.aspx

    The Windows component RPC-over-HTTP-proxy isn’t installed on this computer and
    needs to be installed before Exchange Setup can begin.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.160)/ms.
    exch.setupreadiness.RPCOverHTTPproxyNotInstalled.aspx

    The Exchange Server setup operation didn’t complete. More details can be found
    in ExchangeSetup.log located in the :ExchangeSetupLogs folder.

    C:ScottExchange>

    Any ideas? Thanks

  11. Fernando says:

    Installing 2016 using the GUI I ran into a error:


    The following error was generated when “$error.Clear();
    BinCmdletExtensionAgentsScriptingAgentConfig.xml’.”” —>

    Setup was unable to continue. After renaming the file from .xml.config to .xml Setup was able to continue.

    I ran a test instalation and it worked fine, on the production instalation this error shows up.

    Is there a reason for this?

    Best Regards, you articles are great.

  12. Joe says:

    Hi Paul,

    first Thx for your Article.
    But, I llowing your steps and in final phase of Exchange ManagementTools installation I got the Error ‘ The User has not the right Privilege for this Task. (Set-LocalPermissions).

    Is this a know Error or waht can I do?

    Thx in Advance

    Joe

  13. Keith Rickett says:

    Just wanted to add that UCMA must be installed before attempting to install Exchange 2016 otherwise it will halt at the prereqs stage 😉

  14. Lowell says:

    Paul, thanks for the article. We are having a company migrate our Exchange 2007 to Exchange 2016. I believe we have to first go to Exchange 2013 and then to Exchange 2016. When they quoted us a price they said that they’re running Exchange on two boxes so if one fails the other picks up immediately and then there is a Witness server which is to monitor the two to make sure they are sync’d and running properly. Any thought on this? Thanks.

    • Correct on the 2007 -> (2010 or 2013) -> 2016 migration path, as 2007 can’t go direct to 2016.

      For the other point, what they’re referring to is a “database availability group” (DAG), which is the high availability model for Exchange (think cluster, but different). The witness they’re referring to is the File Share Witness (FSW), which comes into play for “quorum voting” for the DAG when a failure occurs.

      The FSW doesn’t actively monitor the other two servers as you describe, that is incorrect. The DAG has it’s own internal smarts for monitoring itself, called Managed Availability, and will try to take its own correct actions to resolve problems, but that is still not a replacement for monitoring. There’s third party monitoring suites that can keep an eye on a DAG for you (as well as the rest of your network), or you can run PowerShell scripts such as my Test-ExchangeServerHealth.ps1 (Google that) script to keep an eye on things for you.

      Hope that helps.

  15. dlb says:

    May be good to note that the .NET version listed above is not the latest but is still the correct version to use. .NET 4.6 is not officially support and has known problems. I found that out the hard way when installing in a new environment. I followed your site to install 2016. But after I installed .NET, I ran Windows Update to get it to the latest. I’m having to downgrade it now.

  16. Enis says:

    Hi

    Thanx a lot for this article!
    However, if I want to run hosted exchange how do i proceed? I want to have several organizations and several domain names. How do I do than? what is the difference?

    • It got held in moderation because you posted a large amount of raw error/log information. I’m not going to approve it because it’s just a big dump that makes me suspect you haven’t read the few lines of information in it that are most important. It also makes a mess of the page layout if I approve the comment.

      Read your error message and research it, you’ll find lots of information available with suggested fixes.

  17. Tom Andrews says:

    Paul,
    Thanks for the clear and concise information.
    I used your articles when I deployed Exchange 2013 and now again when going to 2016.
    I have not been able to find steps for the actual migration from 2013 to 2016 though and wondered if you had published anything (mailbox migration, connectors, etc.)
    Thanks for what you do.

  18. marc matthes says:

    Looking for any suggestions someone might have on a very hands on how to exchange server book i could use for teaching two technical students?

  19. John says:

    If I want to created a 2 MBX server DAG with Exchange server 2016, what would be the steps to install Exchange 2016 on the 2nd server? Would it be the same steps in this article for the 2nd server?

  20. vardges says:

    Hi,
    How can I reinstall MS Exchange 2016 on new server. I’ve 2servers in DAG, and and they are corrupted. I’ve tried all kind of recovery actions, even my Backup files are corrupted. So i decide to setup new server(VM) on same domain. The only thing I’m thinking about, is AD. I don’t know what kind of problems can I have if I install new server, with same domain alongside same AD.
    Can you assist me to understand possible problems?

    Thank you in advance.

    • I suggest you contact a consultant or open a Microsoft support case, since it sounds like you’re in quite a mess and don’t understand how to get out of it. There’s a lot that can go wrong, including making the problem worse, so a support case is highly recommended.

  21. David Walsh says:

    Paul,

    Great article, could you possible help. I’m trying to install Exchange 2016 to a virtual machine,
    I have run all the prerequisites and they all completed with no issues including /PrerareSchema, /PrepareAD and /PrepareAllDomains
    When I run the install process I get to the installing of the Mailbox Role: Transport Service at which point the install fails (at 93%) with the below error message

    Any assistance is appreciated

    Dave

    Exception has been thrown by the target of an invocation. —> System.InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.

    • Please don’t post long log files or error output into comments, it breaks the layout of the page.

      I’ve edited your post down to just the exception message that was thrown. A Google search suggests that the error may occur if the local security policy of the server requires FIPS compliant algorithms.

      • David Walsh says:

        Paul,

        Thanks for your assistance, I checked the FIPS settings in Local Security policy and found that it was enabled, once I changed this to disabled for this machine, Exchange installed with no problems, again thanks for your assistance

  22. Nuwan Ranawaka says:

    Hi paul

    I have two exch 2010 servers in my organization & both updated with latest RU 15 _ (ProductVersion FileVersion

    14.03.0319.002) . I am trying to install exch 2016 in to same organization & getting readiness check error ” All Exchange 2010 servers in the organization must have Exchange 2010 Service Pack 3 or later installed. The following servers don’t meet this requirement: “.

    did try to update schema from command prompt & still same error .

    ProductVersion FileVersion FileName
    ————– ———– ——–
    14.03.0319.002 14.03.0319.002 C:Program FilesMicrosoftExchange ServerV14binExSetup.exe

    and AD rangeUpper 14734

    I already fulfill pre req : exch 2010 SP3 & running UR 15
    confirmed in control panel installed updates showing update rollup 15 for exchange installed already

    I cannot think what I am missing , thx

      • Nuwan Ranawaka says:

        Paul , Thank in advance
        I have very small setup no DAG or Edge there is only ( one CAS & one Mailbox server , ) & 2016 setup warning about only internet facing CAS server but not mailbox server . They both are up to date & running exch2010 SP3 RU15

        Thx

        • Maybe there’s an AD replication issue. Or maybe the update didn’t apply successfully. There’s not much I can suggest since I can’t see your environment. Perhaps you should open a Microsoft support case.

          • Nuwan Ranawaka says:

            Paul , Thank You

            yes, I will open Microsoft support case, Appreciates quick response as always & proud to be a fan of you / practical365.com since 2012 .

            thx

            by the way that pluralsight video ” Migrating to Exchange server 2016 ” is superb ….

  23. Eslam Refaei says:

    Hi, Paul
    thanks a lot for this helpful post
    i have a question please, i want to create another owa for serving specific users. is it possible and how ?

  24. Ahmad Mazhar says:

    Setup can’t use the domain controller because it belongs to Active Directory site ”. Setup must use a domain controller in the same site as this computer

    while installing Fresh exchange 2016 on windows server 2012 R2

    Please help

  25. Gump Yi says:

    Hi Paul,
    There is one scenario on my environment, i removed the exchange server from its Domain and join into the same domain again. Exchange ECP opened with error, and then i use “setup /PrepareAD /OrganizationName:”Exchange Lab” /IAcceptExchangeServerLicenseTerms” to generate Exchange Security Group. After i finished prepare ad job, another error happens when i open ECP again. Error Message Listed below:
    No Minimal Required Number of Suitable Directory Servers Found in Forest velaskec.local Site Default-First-Site-Name and connected Sites.

    Should i update the schema first? Thanks!

Leave a Reply

Your email address will not be published. Required fields are marked *