How to install Exchange 2010 (SP3) on Windows Server 2012

Server 2012 and Exchange 2010

EDIT: This is one of my most popular posts, if you find it useful please comment or share the post. Thanks.

Now Microsoft Exchange 2010 SP3 has been released it provides support for Windows Server 2012 as the host operating system. In this blog we’ll run through the installation process.

The demo environment I am using includes a Server 2012 DC and a Server 2012 member server.

As this is a virgin demo environment as part of the installation the Exchange 2010 setup will upgrade the AD Schema, if this is an additional server in a migration scenario then the following won’t be necessary. To upgrade the Schema you have two options.

Option 1: Run the Exchange 2010 SP3 setup command with the PrepareAD and OrganizationName switches on the domain controller.

setup /preparead /organizationName:oxfordsbsguy

Then on the member server follow the instructions below to install Exchange 2010 SP3.

Exchange 2010 setup preparead

Option 2: Install the Remote Server Administration Tools (RSAT) onto the member server you are installing Exchange onto so that the ldifde.exe is in the correct location that the Exchange setup expects it to be.

Install RSAT AD DS Tools

With that done, on to the install.

1. On a Server 2012 member server, run PowerShell as Administrator.

Run Powershell as Administrator

2. Run the following command to install the prerequisite Rolls required for a typical Exchange 2010 installation. (Source: Exchange 2010 Prerequisites)

Rolls required for Exchange 2010

Add the roles required for Exchange 2010

3. Wait for the rolls to be completed. On my test server this took about 4 minutes. The server will restart automatically.

Prerequisite Rolls for Exchange 2010 Progress

4. Download Microsoft Exchange 2010 SP3, Microsoft Office 2010 Filter Pack, and Microsoft Office 2010 Filter Pack SP1

Download Exchange 2010 SP3Download Microsoft Office 2010 Filter PackDownload Microsoft Office 2010 Filter Pack SP1

5. Install the Microsoft Office 2010 Filter Pack.

Install Microsoft Office 2010 Filter Pack

6. Install the Microsoft Office 2010 Filter Pack SP1.

Install Microsoft Office 2010 Filter Pack SP1

7. Run and extract Exchange 2010 SP3.Run Exchange 2010 SP3

8. Browse to the location you extracted the files to and run Setup.exe, then click on Step 4: Install Microsoft Exchange.

Exchange 2010 SP3 Installation

9. Read the introduction and click Next.

Microsoft Exchange 2010 Introduction

10. Accept the license agreement, and click Next.

Exchange 2010 Installation - License

11. Enable Exchange Error Reporting, and click Next.

Exchange 2010 Installation - Error Reporting

12. Select the Installation Type. In our example we will use the Typical Option, deselect “Automatically install Windows Server roles and features required for Exchange”, click Next.

Exchange 2010 Installation - Installation Type

13. Enter the Organization Name, I’ve changed mine from the default First Organization in the picture below to OxfordSBSGuy.

Exchange 2010 Installation - Specify the Name of this Organization

14. Select the appropriate client settings, click Next.Exchange 2010 Installation - Client Settings

15. Enter an external domain name to use with Exchange, click Next.

Exchange 2010 Installation - Client Access

16. Opt in/out of the Customer Experience Improvement Program, click Next.Exchange 2010 Installation - Customer Experience

17. Resolve any errors, you should have none! Note Organization Prerequisites, this refers to the Schema upgrade highlighted at the start of this article. Click Next.

Exchange 2010 Installation - Readiness check

18. Watch the progress bars (or go and make a cuppa) as Exchange is installed. You can see it if fairly quick at just under 20 minutes. Click Finish to complete the installation.

Exchange 2010 Installation - Completion

19. Run WSUS or Windows update to install any patches that have been release since SP3. The latest Update Rollup for Exchange 2010 SP3 is UR 12. See the post Exchange 2010 SP3 Update Rollup 12 released and installation tips for installation tips and advice.

20. Reboot the server to complete the installation.

21. Once restarted log in to the Exchange Management Console and start configuring!

Exchange 2010 Management Console

Related Posts:

1. How to install Exchange 2016 (CU3 and beyond) on Windows Server 2016

2. How to install Exchange 2013 (SP1) on Windows Server 2012 R2

3. Exchange 2013 Initial Configuration Settings multi-part series

4. Exchange Server and Update Rollups Build Numbers

5. PowerShell: Identify the number of users connected to a Exchange 2010 CAS Server

28 thoughts on “How to install Exchange 2010 (SP3) on Windows Server 2012

    1. sudip

      i have a problem while while installing exchange 2010 prerequisites from power shell.
      after 68% it gives following error:

      PS C:UsersHOD> Import-Module ServerManager
      PS C:UsersHOD> Add-WindowsFeature NET-Framework-Features,NET-HTTP-Activation,RPC-over-HTTP-proxy,RSAT-Clustering,Web-M
      onsole,Web-Metabase,Web-Net-Ext,Web-Request-Monitor,Web-Server,Web-Static-Content,Web-Windows-Auth,Web-WMI -Restart
      Add-WindowsFeature : The request to add or remove features on the specified server failed.
      Installation of one or more roles, role services, or features failed.
      The source files could not be downloaded.
      Use the “source” option to specify the location of the files that are required to restore the feature. For more
      information on specifying a source location, see

      Error: 0x800f0906
      At line:1 char:1
      + Add-WindowsFeature NET-Framework-Features,NET-HTTP-Activation,RPC-over-HTTP-prox …
      + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      + CategoryInfo : InvalidOperation: (@{Vhd=; Credent…Name=localhost}:PSObject) [Install-WindowsFeature],
      + FullyQualifiedErrorId : DISMAPI_Error__Cbs_Download_Failure,Microsoft.Windows.ServerManager.Commands.AddWindowsF

      Success Restart Needed Exit Code Feature Result
      ——- ————– ——— ————–
      False No Failed {}

      1. Fernan

        Hi there! I ‘ve got this error trying to import Module in PS. Any suggestion?

        Exception calling “Translate” with “1” argument(s): “Some or all identity references could not be translated.”
        At C:\Windows\system32\WindowsPowerShell\v1.0\Modules\ServerManager\ServerManager.psm1:32 char:21
        + $groupNames = @(((New-Object System.Security.Principal.SecurityIdentifier ($ …
        + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo : NotSpecified: (:) [], MethodInvocationException
        + FullyQualifiedErrorId : IdentityNotMappedException

        Exception calling “Translate” with “1” argument(s): “Some or all identity references could not be translated.”
        At C:\Windows\system32\WindowsPowerShell\v1.0\Modules\ServerManager\ServerManager.psm1:32 char:21
        + $groupNames = @(((New-Object System.Security.Principal.SecurityIdentifier ($ …
        + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo : NotSpecified: (:) [], MethodInvocationException
        + FullyQualifiedErrorId : IdentityNotMappedException

  1. Lonnie

    I have Exchange 2010 SP3 running on Server 2012 (Mailbox, Client Access, Hub Transport all on the same domain member server). With Outlook Anywhere and RPC-over-HTTP enabled, users who are able to connect internally are unable to connect externally with Outlook Anywhere.

    Using the Test-OutlookConnectivity cmdlet, I’ve determined that the connection fails when the client pings the RpcProxy. The failure is due to a (401) unauthorized error returning from a call to the /rpc/RpcProxy.dll virtual directory.

    The Rpc virtual directory (C:WindowsSystem32RpcProxy) in ISS has the following permissions:
    – ALL APPLICATION PACKAGES : Read & execute
    – CREATOR OWNER : Full control
    – SYSTEM : Full control
    – Trusted Installer : Full control
    – LocalHostAdministrators : Full control
    – LocalHostUsers: Read & execute

    By default, there are no domain groups or users included in the permissions for the RpcProxy directory. In addition, the permissions on the rpc virtual directory cannot be changed (the Add & Edit buttons are disabled). However, I found that when domain/exchange users are added to the LocalHostUsers group, the problem is remedied. This seems like a reasonable solution except that it would then allow these users to log on interactively to the exchange server which is undesirable.

    I’ve noted that in SBS 2011, the RpcProxy directory includes DomainUsers and DomainAdministrators instead of the LocalHost groups.

    The questions I have are:

    1. Is this situation always the case when Exchange 2010 is installed on Server 2012 or is my situation an anomaly?
    2. Is there a solution other than adding the users to the LocalHostUsers group? (i.e. Is it appropriate to seize ownership of the RpcProxy directory in order to add the desired domain group?)

    1. Lonnie

      Thanks Carl!

      I have removed and reinstalled the RPC-over-HTTP feature (disabled and re-enabled Outlook Anywhere). I also tried many other suggestions from all over the internet.

      I actually went ahead and took ownership of the RpcProxy folder and added an “Outlook Anywhere Users” group. I also compared an Exchange 2013 installation to the 2010 installation and I noticed that it has a second “Backend” site in IIS that I’m guessing it uses for the RPC-over-HTTP feature. The permissions on that folder make more sense. It seems the Exchange 2010 dev team overlooked the new RpcProxy config in Server 2012.

  2. Jeremy

    do you have to go through the process of installing exchange with SP1 first and then SP3…it is not clear how it is labelled. what is what and when i download Exchange i am only presented with the options exchange with SP1 or Exchange 2013?
    SP3 is available from Microsoft Download…the Disk size is not even close as well…can you clarify what the starting point is…thx

      1. Jeremy

        thanks for the info…i had to make one registry change to disable IP6 components before installing after that the installation was clean….thx again

          1. Jeremy

            Sure i added this registry entry as i received an error for the hub transport install
            HKLM > System > CurrentControlSet > Services > TCPIPV6 > Parameters
            added a DWORD32 DisabledComponents with a value of [HEX] 4lffffff then it went through
            credit goes to this Video
            identical process…

      2. James

        Just to double check, I don’t need to install 2010 with sp1 first, I can launch the install from the sp3 download (this is a 2003 to 2010 migration on server 2012) -> does it prompt for the original 2010 install files?


          The installation in this article was done using only the SP3 download. Regarding a migration the method of installation on a new server shouldn’t make any difference, i would however, image the original server and run through the process and steps in a test lab before doing it live. This is just good practice!


      Hi Jake,
      There are several reasons, you could be buying a new server and migrating Exchange 2010 to it, migrating from an older version of Exchange, you may not have 2013 experience in house. Also when the guide was created 2013 was still very new, so installing 2010 was less risky. I’ll take a look at your installation guide though, as I need to start looking at 2013.

  3. Peder

    Hi i am running migrati sbs2003 Exchange to Exchange 2010 i am following :
    Problem is that i tried on 2012 server instead of 2008 R2, the command in powershell:
    Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,RPC-Over-HTTP-Proxy –Restart
    Did not go ok i tried anyway and now i need to take away msx2010 from sbs2003 so quest is:
    If i remove Exchange from the 2012 server add/remove programs vill that interupt my working sbs2003 Exchange that runs now ?

  4. Harry

    Hi, Thanks for your guidance. I’m successfully installed exchange 2010 sp3 on a Windows 2012 server r2. But I’m struggling with creating A and MX records that point to my mail server. I’m hosting my DNS with Godaddy. Please help. Many thanks

  5. Joe

    I’m trying to add a server with the Mailbox role, the other servers have Exchange Enterprise edition. I would like to have the same Enterprise edition in the new server. Do I do anything different to accomplish that? the google searches don’t return any useful info on this.

  6. Thomas

    Could you please do a guide how to only install the Exchange 2010 Management Tools silently?
    Best Regards,

  7. Luis

    Thanks for the article!
    I am trying to install it on Windows 2012 but it won’t install the Transport role, prompting this error message: “The MSExchangeTransport service can’t start”
    Then I go to services and indeed, that service is “starting” all the time.
    This machine is also a DC . Could that be the issue ?
    Thanks again for posting the article!!

  8. Peter McL

    Hi I got
    Mailbox Role Failed

    The following error was generated when “$error.Clear();
    $wevtutil= join-path (join-path $env:SystemRoot system32) wevtutil.exe;
    $manifestPath = [System.IO.Path]::Combine($RoleInstallPath, “Scripts\”);
    Start-SetupProcess -Name:”$wevtutil” -Args:”im `”$manifestPath`” ”
    ” was run: “Process execution failed with exit code 15010.”.

    Process execution failed with exit code 15010.
    Click here for help…

    Fix (registery) at

Comments are closed.