Tag: Exchange

Exchange 2016 Installation Step by Step Guide

Microsoft Exchange product has been released Exchange 2016 to the public. Here I am going to show you how to install Exchange 2016 on a testing infrastructure.


Before we jump in to installation of Exchange 2016 lets take a look at some of the System requirements and compatibility requirements.


Coexistence between exchange 2016 and earlier versions.
Exchange version Exchange organization coexistence
Exchange 2007 and earlier versions Not supported
Exchange 2010 Supported with Update Rollup 9 for Exchange 2010 SP3 or later on all Exchange 2010 servers in the organization, including Edge Transport servers.
Exchange 2013 Supported with Exchange 2013 Cumulative Update 8 or later on all Exchange 2013 servers in the organization, including Edge Transport servers.
Mixed Exchange 2010 and Exchange 2013 organization Supported with the following minimum versions of Exchange:

  • Update Rollup 9 for Exchange 2010 SP3 or later on all Exchange 2010 servers in the organization, including Edge Transport servers.
  • Exchange 2013 Cumulative Update 8 or later on all Exchange 2013 servers in the organization, including Edge Transport servers.
Hybrid deployments with Office 365 Supported with Office 365 tenants that have been upgraded to the latest version.
Supported Forest Functional Level for Exchange Server 2016 Active Directory must be at Windows Server 2008 forest functionality mode or higher.
Minimum Operation System Requirements
  • Windows Server 2012 R2 Standard or Datacenter
  • Windows Server 2012 Standard or Datacenter
Memory Requirement
  • Mailbox   8GB minimum
  • Edge Transport   4GB minimum


Please use below URL for latest information about Exchange 2016 system requirements


* You must have Enterprise Admin, Schema Admin and Domain admin rights before you start the installation of Exchange 2016.



Lab Scenario

In this lab we are using Windows server 2012 R2 Domain controllers and no legacy exchange versions. Our AD domain name is UCtalks.local and mail domain is uctalks.com.

Installing Exchange 2016 Pre-requisites

Install Active Directory preparation pre-requisites. This will allow you to prepare AD schema during Exchange 2016 installation wizard.

  1. Open Windows PowerShell.
  2. Install the Remote Tools Administration Pack using the following command.

Install-WindowsFeature RSAT-ADDS


Install Mailbox Server Role Pre-requisites . Make sure to reboot the server once completing the pre-requisites installation.

Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell, 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

Please use below url for the latest Exchange 2016 prerequisites



After you’ve installed the operating system roles and features, install the following software in the order as shown below.

  1. .NET Framework 4.5.2
  2. Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit


Installing .NET Framework 4.5.2


Installing Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit


We need to prepare ADSchema/ PrepareAD and prepareDomain. Please use fallowing Cmdlets for ran each task.

  1. Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms
  2. Setup.exe /PrepareAD /OrganizationName:"<organization name>" /IAcceptExchangeServerLicenseTerms
  3. Setup.exe /PrepareDomain:uctalks.local /IAcceptExchangeServerLicenseTerms


Prepare AD Schema – Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms


Prepare AD – Setup.exe /PrepareAD /OrganizationName:"Contoso" /IAcceptExchangeServerLicenseTerms


After we prepare the AD, there is no way to install Exchange 2010 or Exchange 2013 as mentioned above screenshot.

Prepare Domain – Setup.exe /PrepareDomain:uctalks.local /IAcceptExchangeServerLicenseTerms


Now we have prepare the Active Directory for Exchange 2016. It will take few minutes to few hours to complete AD replication.


Installing Exchange 2016 Using Setup Wizard

Now we are installing Exchange 2016 using GUI. Please bare in mind to use elevated prompt if we use UAC enable mode. Its always better to select to check internet for updates.


Once you check the available update and Setup will start to copy Exchange files to local disk.


Click Next.


Accept the Microsoft License Agreement and click next.


Select Recommended settings and click next.


Select mailbox role and windows features installation check box. management tools will select automatically.


Select the installation location and Click Next.


Keep enable the Malware protection settings and click next.



Click next to start installation process.




We have completed the exchange 2016 installation. Please restart the server to complete the installation.

There are lot of post installation tasks and you can find all the required configuration from below url.


Configuring and managing the Pickup Directory – Part 1

This article series contain two articles, in first article I provide Theoretical Basics information of pickup directory, how works and importance of pickup directory. In the second article I’ll describe how to configure pickup directory using Exchange management shell.

By default pickup directory exists in "\Transport Roles\Pickup" of installation directory on every Exchange 2007 computer that has installed Edge role or Hub role. If you formatted .eml file and placed in the pickup directory, pickup directory will submit to delivery. This method used by most Exchange Administrator for mail flow troubleshooting their emails by creating .eml files.


How Pickup Directory process messages 

Correctly formatted messages that copied to pickup directory is processed for submission for delivery as fallowing order.

  1. Pickup Directory checked for new email messaged every 5 seconds and you can’t change that time interval.By default pickup directory processed 100 messages and messaged are cannot open left in the directory for next pool.
  2. Limits that are messages in pickup directory checked.By default maximum header size is 64K and maximum recipient limit is 100 recipients.
  3. eml file rename to .tmp file.if .tmp file already exists it is renamed as a <file name><Date time>.tmp.If the file renaming fail, pickup process proceed for next eml file with generated event log.
  4. After the .tmp file converted to the email message, a “Delete on Close” command is issued and tmp file still exists but can’t open file by anyone else.
  5. after submitted the message to delivery ,a “Close” command issued,.tmp file is deleted from pickup directory.If deletion is failed, event error generated in event log.If transport services restated all .emp files are renamed to .eml files and start repressing messages.That could lead to duplicate mail messages transmission.

Requirements for Message Files in the Pickup Directory


A message file that is copied to pickup directory must be meet following conditions.

  • The message file must be a simple text file that contain with basic SMTP message format.
  • A message file extension must be a .eml.
  • At least one email address must be exists in from: or sender message header fields. If a single email address exists in the both from or sender filed,email address in the from: filed used as the originator of the message in the message envelop.
  • Only one email address can ever exist in the send filed.The sender filed is not required if email address present in From: filed.
  • Multiple e-mail addresses are allowed in the From: field, but a single e-mail address must also exist in the Sender field. The address in the Sender field is then used as the originator of the message in the message envelope.
  • At least one e-mail address must exist in the To:, Cc:, or Bcc: fields.
  • A blank line must exist between the message header and the message body.


Please see below example of text message that uses acceptable message formatting for the pickup directory.

To: chinthaka@msglab.info

From: Devid@msglab.info

Subject: Test message

This is test Message to check mail flow.


MIME contain messages are supported in pickup directory.Please see below example that is compatible with pickup directory

To: chinthaka@msglab.info
From: bob@nwtraders.com
Subject: Message subject
MIME-Version: 1.0
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
<TR><TD>cell 1</TD><TD>cell 2</TD></TR>
<TR><TD>cell 3</TD><TD>cell 4</TD></TR>


In here I am given you basic Theoretical information of pickup directory. I’ll show how to configure pickup directory in next article called "Configuring and Managing pickup directory-Part 2 ".


Managing the Pickup Directory

Installing Exchange Server 2010 Beta1-part2

This is the second part of the Installing exchange 2010 article. If you have missed first part,I suggest you to read Exchange 2010 pre-requests and system requirements post. In this post I suppose to describe how to install exchange 2010 on the windows 2008 server.

Exchange 2010 setup process added some improvements to install exchange in different languages. You will see bunch of language folders in exchange 2010 source file folder. When we run setup.exe the setup will identify the current language of the operating system and display initial screen and introduction page by current language. In the second step we have to select download language file or use English as a default language.

Please bear in mind once the operating system has been install, you must be install all pre-requisites as mentioned in previous post. After that good to run Microsoft update for any additional update that might be needed. Then restart the server before install exchange 2010.

After setting up everything properly we should able to install exchange 2010.i am not going to guide how to prepare active directory in here. For more information regarding that please refer Prepare Active Directory and Domains TechNet article. Ok I think everything is clear. Let’s back to work.

Now we are ready to install Exchange 2010, you can use either GUI or command line to install. In this article I’ll use the GUI.

I lunch the Setup.exe in the extracted folder. Now you can see Exchange 2010 splash screen.


You can see exchange 2010 Splash screen is very similar to Exchange 2007 one and it’s detect required pre-requisites and those are grayed. So we can proceed to next step.

Click Install Microsoft Exchange link on the Splash screen. Then you will see copying setup files.


After completed the file processing step, Setup appears introduction page.


Click next, then you see language selection page


Currently I don’t have any additional language pack, so I’ll continue English as a Default language pack. Then you see language pack confirmation screen. Click next and continue.

Then license agreement page appears


Accept it and click next. After that error reporting page appears. Select as your choose and click next.

Then Exchange installation type page appears


Click custom and next. Then custom role selection page appears


If you see carefully custom exchange server installation, you will see there is no Clustered mail box server component. Because exchanges 2010 have new feature called incremental Deployment. you can configure high availability option after install exchange 2010.also there is a another feature called Database High availability Group(DAG).if you use DAS it’s created failover clustering for you, no need to create windows failover clustering manually. It makes configuring High availability easy.

Select Mailbox server role, Client access server role, Hub transport server roles. Management tools will select automatically.

Then Exchange organization page appears. Give organization name as a Demolab.


Then client settings page appears


If your organizations have client’s outlook 2003 or earlier versions you must select yes. Because Outlook 2003 and earlier version use public folders to access system data such as Free/Busy. Outlook 2007 and later versions use CAS server to access system data.

Then Exchange Customer Experience Improvement Program appears and joins as your wish.

Then readiness check page appears.


All readiness checks must be successfully passed as below.


AT this point setup is ready for exchange 2010 installation. So I click on the Install button. Then installation screen appears.


After installation Uncheck the Finalize installation using the Exchange Management Console checkbox, and click Finish completing setup. Then reboot the server.


Now Exchange 2010 installation has completed.

Exchange 2007 SP1 update rollup 9 has been released

Microsoft Exchange product team has been release update rollup 9(KB 970162) for exchange 2007 SP1.the release of the rollup via Microsoft update will -happen on July 28.According to Microsoft team blog majority of changes in this rollup are bug fixes.I would like to present some of those fixes.


KB 969911 –This bug is affect customers who is using Messaging Record    Management feature and have specified storage limit for managed folder.after move mailbox,the property which marks the folder as a managed is not preserved.

KB 968621 – Information store stop responding during online maintenance or when schedule backup is canceled.

KB 945877 – Performance improvements to esutil when it vitrifies the checksum of transactions logs.

– Supports for Windows 2008 R2 domain controllers.However that doesn’t mean it supports install exchange 2007 on Windows 2008 R2 Os.

KB 968715 – This bug is mostly effects for clients who have deployed CAS-CAS proxying.


KB 970162-have more details about this release


More Information

Update Rollup 9 for Exchange Server 2007 Service Pack 1 has been released

Description of Update Rollup 9 for Microsoft Exchange Server 2007 Service Pack 1