Deploying Exchange 2013 on windows 2012 Server

Exchange  2013 comes up with some good features and also have reduced some of the roles like Hub-transport, Edge Server , better integration with  SharePoint & Lync, E-discovery and many more let check out the deployment process.

To deploy exchange 2013 you must have a supported operating system (such as Windows Server 2008 R2 with Service Pack 1 (SP1) or Windows Server 2012), have enough disk space, be a member of an Active Directory domain.

In this blog im going to install exchange 2013 using setup wizard , we can also install by using unattended installation  mode

Prerequisites for windows 2012 server

If we have mailbox server role on a separate server

  • Open Windows PowerShell.
  • Run the following command to install the required Windows components.

Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation

We need to install the following Pre-requisites in windows 2012

  • Microsoft Unified Communication Managed API 4.0 Core Runtime 64bit
  • Microsoft Office filter pack
  • Microsoft Office filter pack Service Pack 1

Setup Wizard starts for Exchange 2013.







Malware Protection settings

Exchange Server 2013 anti-malware protection feature which helps combat malware in our email messaging environment

Click Yes to enable malware scanning.


I need to install unified communication managed api and filter pack with sp1



Lets start the Setup as we have completed with all the Pre-requisites



Now we are done we the setup we need to verify our deployment

Post deployment tasks

  • During the deployment we need to check the Application logs, system logs from event viewer need to make sure we are not getting any warnings or errors.
  • Exchange server create setup logs during the setup process you can find on C:\ExchangeSetupLogs\ExchangeSetup.log
  • Setup log file capture each and every task which is performed during the deployment process




Also verify the services are up and running

Its recommend to restart the Server

Now you can see new console to manage Exchange 2013 Exchange Admin Center

Type the following url to access the Admin center https://servername/Ecp




We will check more about Exchange 2013 features in my next blog thanks for viewing it !!!!!! 🙂







Hello Everyone

Here is my First blog about Exchange 2010 Unattended Installation Mode.

Let’s discuss about the deployment Scenario for Exchange 2010 in Unattended Mode,

Types of Setup

We have Following Types of Setup which we can perform for Exchange server

1) Exchange Setup GUI:  We can run the Exchange 2010 Setup wizard GUI Mode

2) Exchange Unattended Setup: is an unattended which we need to perform using Command prompt or through a script

Before we start our setup we need to install the prerequisites


  • We need to make sure that our Forest Functional Level is windows 2003 Active Directory
  • Minimum OS should be Windows Server 2008 with SP2 64bit or Windows Server 2008 R2 must be installed for Exchange 2010 server
  • Configure Raid as per your requirement.
  • Make Sure to  install Windows Updates
  • Permissions for deploying Exchange 2010
    • Schema Admins
    • Domain Admins
    • Enterprise Admins
    • Local administration rights on the server
  • Imp Note: If we you are planning for DAG (Database Availability Group) We Must install Windows Enterprise 2008 Sp2 or R2 because The Standard Edition doesn’t support the features needed for DAG.
  • Make Sure the IP Settings are proper
  • Microsoft Office Filter Packs
  • Adding  Import-Module ServerManager from Power Shell
  • Add-WindowsFeature cmdlet to install the component

We are deploying the following roles in Exchange 2010 

Client Access, Hub Transport, and Mailbox server for this we need the following features: 

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,Web-Asp-Net,Web-Client-Auth,Web-Dir-Browsing,Web-Http-Errors,Web-Http-Logging,Web-Http-Redirect,Web-Http-Tracing,Web-ISAPI-Filter,Web-Request-Monitor,Web-Static-Content,Web-WMI,RPC-Over-HTTP-Proxy –Restart


After the restart launch another elevated Windows PowerShell console and run the following command

Set-Service NetTcpPortSharing -StartupType Automatic


Just a quick Note:

Before Exchange 2010 SP1 released we need to install this components manually

Now Exchange SP1 has new deployment Functionality were it will install all the components automatically


More information

We can now select the /InstallWindowsComponents parameter during an unattended install of Exchange 2010 SP1

Also we need to install some of the Hotfixes if we are deploying

Exchange 2010 SP1 and SP2 Hotfixes for Windows Server 2008 R2

List of Hotfixes





For more information you can use this link

Before we install Exchange Server in our Organization we need to prepare schema and AD /Prepareschema or /PS

To run this command you should have schema admin rights and Enterprise Admin.

Setup /PrepareAD /OrganizationName:organization name

Once we are done with Prepare schema same as we need to run prepare AD.

Lets begin the Setup /mode:install /role:CA,MB,HT,MT /organizationName:MyExchangeserver

This command we need to run to install the following roles Client Access Server,Mailbox & Hub-Transport

Now we need to restart the server

Verifying Our Exchange server setup.

Here is very important thing which we need to check to verify our setup.

Microsoft Recommends to verify the setup by using Get-ExchangeServer Cmdlet or by reviewing the Setup logs file.

We can use this CMD to check Full information about our Exchange Server

Get-ExchangeServer |FL


You can find the setup log at <system drive>\ExchangeSetupLogs\ExchangeSetup.log. The <system drive> variable represents the root directory of the drive where the operating system is installed.

For more info you can refer

Thanks for Viewing.

Exchange 2010 Setup in Unattended Mode