Deployment of an Exchange Server 2013 server goes through three main stages.
Overview
In Windows Server 2012, dcpromo has been deprecated.
If you are installing Exchange Server in the AD forest for the first time run the following Exchange 2013 setup command to prepare Active Directory:
Note: if your organization name contains spaces then it must be enclosed in quotes as shown above.
If an Exchange organization already exists you can omit the /OrganizationName parameter.
INSTALLING THE EXCHANGE SERVER 2013 PRE-REQUISITES
Exchange Server 2013 can be installed on Windows Server 2012 and Windows Server 2012 R2, either Standard or Datacenter edition.
Windows Server 2012 will support any of the Exchange 2013 server roles. Unlike Windows Server 2008 R2, if you want to run Exchange Server 2013 Mailbox servers as members of a Database Availability Group you can still do so with the Standard edition of Windows Server 2012. Enterprise edition is not required for DAG members.
Note: Exchange Server 2013 Service Pack 1 added support for installing on Windows Server 2012 R2. For the purposes of this article any mention of Windows Server 2012 includes R2, and assumes that you will be installing Exchange Server 2013 SP1 or later.
As there are only two mandatory Exchange Server 2013 server roles there are only two combinations of pre-requisites required:
For the third server role, Edge Transport, the pre-requisites are quite minimal. Find out more about installing Exchange 2013 Edge Transport here.
INSTALLING PRE-REQUISITES FOR AN EXCHANGE SERVER 2013 MAILBOX, OR MAILBOX AND CLIENT ACCESS SERVER
For a Windows Server 2012 server that will host either the Exchange 2013 Mailbox server role, or both the Mailbox and Client Access server roles, the following PowerShell commands is used to install the required server roles and features.
Note: the Add-WindowsFeature command is quite lengthy and you will need to scroll across to be able to copy/paste all of it.
A restart is required after the roles and features have finished installing.
Next, install the following software in this order.
For a Windows Server 2012 server that will host only the Exchange 2013 Client Access server role, the following PowerShell command is used to install the required roles and features.
Note: the Add-WindowsFeature command is quite lengthy and you will need to scroll across to be able to copy/paste all of it.
A restart is required after the roles and features have finished installing.
Next, install the following software. This is the same requirement as the Mailbox server role just without the Office Filter Pack.
The server is now ready for the installation of Exchange Server 2013.
Accept the license agreement and click Next to continue.
Choose whether or not to enable Error Reporting and click Next to continue.
After a check that all the pre-requisites are installed the setup wizard will move on to the next step automatically (if the check was successful).
Now we can choose the server roles to install. If this is the first server you’re installing Microsoft recommends you install the Mailbox server role first (this can be either a Mailbox-only server or a combined Mailbox/Client Access server).
Verify that you have enough disk space for the installation, or choose a path that does have enough disk space, and click Nextto continue.
If there is no existing Exchange organization in Active Directory, and you haven’t already prepared Active Directory for Exchange, you will be prompted to enter an Exchange organization name.
When installing the Mailbox server role you are given the option to disable malware protection. If you disable it now you can enable it again later.
Some readiness checks are performed. If this is the not the first server you’re installing and there is no Send Connector defined for outbound email then you may see a warning, but you can still proceed with the server installation.
Setup can’t detect a Send connector with an address space of ‘*’. Mail flow to the Internet may not work properly.
When you are ready to proceed you can click Install to begin.
The install is a fairly lengthy process, so you may want to go and do something else while you wait. When setup has finished click Finish.
- Setup your first Domain Controller
- Preparing Active Directory (if you are installing Exchange Server 2013 for the first time)
- Installing the Exchange Server 2013 pre-requisites on the server
- Running Exchange Server 2013 setup
Overview
In Windows Server 2012, dcpromo has been deprecated.
Using Server Manager (UI):
In order to make the windows server 2012 domain controller we will install ADDS (Active Directory Domain Services) role from the server manager on Windows Server 2012.
First we will change the server name let say DC01 and the IP address 10.10.21.1 (try to avoid using default 192.168.0.1)
INSTALLING AD DS ROLE
“Before You Begin” screen provides you basic information such as configuring strong passwords, IP addresses and Windows updates.
On Installation Type page, select the first option “Role-based or Feature-based Installation“.
Scenario-based Installation option applied only to Remote Desktop services.
On the “Server Selection” Page, select a server from the server pool and click next.
To install AD DS, select Active Directory Domain Services in turn it will pop-up to add other AD DS related tools. Click on Add Features.
After clicking “Add Features” above, you will be able to click “Next >” as shown in the screen below.
On the “Select Features” Page, Group Policy Management feature automatically installed during the promotion. Click next.
On the “Active Directory Domain Services” page, it gives basic information about AD DS. Click Next.
On the “Confirmation” Page, You need to confirm this to continue with this configuration. It will provide you an option to export the configuration settings and also if you want the server to be restarted automatically as required.
After clicking “Install” the selected role binaries will be installed on the server.
After “Active Directory Domain Services” role binaries have been installed and now it is time to promote the server to a Domain Controller.
To create a new AD forest called “ArabITPro.local”, select add a new forest.
Type the name ArabITPro.local
Specify the FFL, DFL, whether or not it should be a DNS Server and also the DSRM administrator password. As you can see, it has selected the GC option by default and you cannot deselect it. The reason for this is that is the very first DC of the AD forest and at least one needs to be a GC.
DNS delegation warning.
Checks the NetBIOS name already assigned.
Specify the location of the AD related folders and then click next.
Summary Of All Installation Options/Selections.
Click View script for single command line PowerShell script for dcpromo.
Before the actual install of AD, all prerequisites are checked. If All prerequisite checks are passed successfully then clickInstall.
When you click Install, DNS and the GPMC are installed automatically.
After the promotion of the server to a DC finished server restart automatically.
Once the server is booted and you logon to it, click on Server Manager | Tools , will notice that following have been installed :
In order to make the windows server 2012 domain controller we will install ADDS (Active Directory Domain Services) role from the server manager on Windows Server 2012.
First we will change the server name let say DC01 and the IP address 10.10.21.1 (try to avoid using default 192.168.0.1)
“Before You Begin” screen provides you basic information such as configuring strong passwords, IP addresses and Windows updates.
On Installation Type page, select the first option “Role-based or Feature-based Installation“.
Scenario-based Installation option applied only to Remote Desktop services.
On the “Server Selection” Page, select a server from the server pool and click next.
To install AD DS, select Active Directory Domain Services in turn it will pop-up to add other AD DS related tools. Click on Add Features.
After clicking “Add Features” above, you will be able to click “Next >” as shown in the screen below.
On the “Select Features” Page, Group Policy Management feature automatically installed during the promotion. Click next.
On the “Active Directory Domain Services” page, it gives basic information about AD DS. Click Next.
On the “Confirmation” Page, You need to confirm this to continue with this configuration. It will provide you an option to export the configuration settings and also if you want the server to be restarted automatically as required.
After clicking “Install” the selected role binaries will be installed on the server.
After “Active Directory Domain Services” role binaries have been installed and now it is time to promote the server to a Domain Controller.
To create a new AD forest called “ArabITPro.local”, select add a new forest.
Type the name ArabITPro.local
Specify the FFL, DFL, whether or not it should be a DNS Server and also the DSRM administrator password. As you can see, it has selected the GC option by default and you cannot deselect it. The reason for this is that is the very first DC of the AD forest and at least one needs to be a GC.
DNS delegation warning.
Checks the NetBIOS name already assigned.
Specify the location of the AD related folders and then click next.
Summary Of All Installation Options/Selections.
Click View script for single command line PowerShell script for dcpromo.
Before the actual install of AD, all prerequisites are checked. If All prerequisite checks are passed successfully then clickInstall.
When you click Install, DNS and the GPMC are installed automatically.
After the promotion of the server to a DC finished server restart automatically.
Once the server is booted and you logon to it, click on Server Manager | Tools , will notice that following have been installed :
- Active Directory Administrative Center
- Active Directory Domains and Trusts
- Active Directory Module for Windows PowerShell
- Active Directory Sites and Services
- Active Directory Users and Computers
- ADSI Edit
- DNS
- Group Policy Management
PREPARING ACTIVE DIRECTORY FOR EXCHANGE SERVER 2013
When you are installing Exchange Server 2013 for the first time the Active Directory needs to be prepared.
There are a series of requirements for Active Directory preparation to be successful:
Because the Active Directory preparation requires the RSAT-ADDS tools I am running it on the domain controller in my test lab.
Alternatively, you can install the tools on a member server to run Exchange 2013 Active Directory preparation.
For Windows Server 2012, in PowerShell run:
When you are installing Exchange Server 2013 for the first time the Active Directory needs to be prepared.
There are a series of requirements for Active Directory preparation to be successful:
- Schema master running Windows Server 2003 with SP2, or a later version of Windows Server
- At least one Global catalog server per site that Exchange will be installed in that is running Windows Server 2003 SP2 or later
- At least one Domain controller per site that Exchange will be installed in that is running Windows Server 2003 SP2 or later
- Forest functional mode of Windows Server 2003 or higher
- An account with Schema Admins, Domain Admins, and Enterprise Admins permissions to run Exchange setup
Because the Active Directory preparation requires the RSAT-ADDS tools I am running it on the domain controller in my test lab.
Alternatively, you can install the tools on a member server to run Exchange 2013 Active Directory preparation.
For Windows Server 2012, in PowerShell run:
Install-WindowsFeature RSAT-ADDS
If you are installing Exchange Server in the AD forest for the first time run the following Exchange 2013 setup command to prepare Active Directory:
cd Exchange_2013_SP1_64bit
.\setup /PrepareAD /OrganizationName: "your organization name" /IAcceptExchangeServerLicenseTerms
Note: if your organization name contains spaces then it must be enclosed in quotes as shown above.
If an Exchange organization already exists you can omit the /OrganizationName parameter.
cd Exchange_2013_SP1_64bit
.\setup /PrepareAD /IAcceptExchangeServerLicenseTerms
INSTALLING THE EXCHANGE SERVER 2013 PRE-REQUISITES
Exchange Server 2013 can be installed on Windows Server 2012 and Windows Server 2012 R2, either Standard or Datacenter edition.
Windows Server 2012 will support any of the Exchange 2013 server roles. Unlike Windows Server 2008 R2, if you want to run Exchange Server 2013 Mailbox servers as members of a Database Availability Group you can still do so with the Standard edition of Windows Server 2012. Enterprise edition is not required for DAG members.
Note: Exchange Server 2013 Service Pack 1 added support for installing on Windows Server 2012 R2. For the purposes of this article any mention of Windows Server 2012 includes R2, and assumes that you will be installing Exchange Server 2013 SP1 or later.
As there are only two mandatory Exchange Server 2013 server roles there are only two combinations of pre-requisites required:
- Mailbox servers, or combination Mailbox and Client Access servers
- Client Access servers
For the third server role, Edge Transport, the pre-requisites are quite minimal. Find out more about installing Exchange 2013 Edge Transport here.
INSTALLING PRE-REQUISITES FOR AN EXCHANGE SERVER 2013 MAILBOX, OR MAILBOX AND CLIENT ACCESS SERVER
For a Windows Server 2012 server that will host either the Exchange 2013 Mailbox server role, or both the Mailbox and Client Access server roles, the following PowerShell commands is used to install the required server roles and features.
Note: the Add-WindowsFeature command is quite lengthy and you will need to scroll across to be able to copy/paste all of it.
PS C:\> 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
Success Restart Needed Exit Code Feature Result
------- -------------- --------- --------------
True Yes SuccessRest... {Application Server, HTTP Activation, .NET...
WARNING: You must restart this server to finish the installation process.
A restart is required after the roles and features have finished installing.
Next, install the following software in this order.
- Unified Communications Managed API 4.0 Runtime
- Microsoft Office 2010 Filter Pack 64 bit
- Microsoft Office 2010 Filter Pack SP1 64 bit
For a Windows Server 2012 server that will host only the Exchange 2013 Client Access server role, the following PowerShell command is used to install the required roles and features.
Note: the Add-WindowsFeature command is quite lengthy and you will need to scroll across to be able to copy/paste all of it.
PS C:\> Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, 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
Success Restart Needed Exit Code Feature Result
------- -------------- --------- --------------
True Yes SuccessRest... {Application Server, HTTP Activation, .NET...
WARNING: You must restart this server to finish the installation process.
A restart is required after the roles and features have finished installing.
Next, install the following software. This is the same requirement as the Mailbox server role just without the Office Filter Pack.
The server is now ready for the installation of Exchange Server 2013.
INSTALLING EXCHANGE SERVER 2013 USING THE SETUP WIZARD
After installing the pre-requisites a restart of the server may be required. If you proceed without restarting then setup may be unable to proceed when it detects the pending restart.
From the location where you have stored your Exchange 2013 files run Setup.exe.
After the setup files have updated click Next to continue.
Click Next to continue past the Introduction message.
After installing the pre-requisites a restart of the server may be required. If you proceed without restarting then setup may be unable to proceed when it detects the pending restart.
From the location where you have stored your Exchange 2013 files run Setup.exe.
The first dialog gives you the opportunity to check for updates to the setup files before you proceed.
Check for updates to Exchange 2013 setup files
After the setup files have updated click Next to continue.
Click Next to continue past the Introduction message.
Exchange 2013 setup introduction
Accept the license agreement and click Next to continue.
Exchange 2013 license agreement
Configure Exchange 2013 error reporting
Now we can choose the server roles to install. If this is the first server you’re installing Microsoft recommends you install the Mailbox server role first (this can be either a Mailbox-only server or a combined Mailbox/Client Access server).
Choose the Exchange 2013 server roles to install
Choose the location to install Exchange 2013
When installing the Mailbox server role you are given the option to disable malware protection. If you disable it now you can enable it again later.
Configure anti-malware protection for the Mailbox server
Setup can’t detect a Send connector with an address space of ‘*’. Mail flow to the Internet may not work properly.
Exchange 2013 setup pre-requisite warning
Begin the installation of Exchange 2013
Exchange 2013 setup is finished
No comments:
Post a Comment