Microsoft Exchange Server

Microsoft Exchange Server is a calendaring and mail packs being released over the next two years.[9]
server developed by Microsoft that runs exclusively on the
Microsoft Windows Server product line.

1.2 Exchange Server 5.0

Exchange Server was initially Microsofts internal mail

server. The rst version of Exchange Server to be published outside Microsoft was Exchange Server 4.0. Exchange initially used the X.400 directory service but
switched to Active Directory later. Versions 4.0 and 5.0
came bundled with an email client called Microsoft Exchange Client. It was discontinued in favor of Microsoft
Outlook.

Introduced the new Exchange Administrator console, as

well as opening up integrated access to SMTP-based
networks for the rst time. Unlike Microsoft Mail (which
required a standalone SMTP relay), Exchange Server
5.0 could, with the help of an add-in called the Internet
Mail Connector, communicate directly with servers using SMTP. Version 5.0 also introduced a new Web-based
e-mail interface called Exchange Web Access, which was
rebranded as Outlook Web Access in a later service pack.
Along with Exchange Server version 5.0, Microsoft released version 8.01 of Microsoft Outlook, version 5.0
of the Microsoft Exchange Client and version 7.5 of
Microsoft Schedule+ to support the new features in the
new version of Exchange Server.

Exchange Server uses a proprietary protocol called

MAPI. Over time, however, it added support for POP3,
IMAP, SMTP and EAS.

Exchange Server is licensed both in the forms of onpremises software and software as a service. In the onpremises form, customer purchase client access licenses
(CALs). In the software as a service form, Microsoft receives a monthly service fee instead.
Exchange Server 5.0 introduced a number of other new
features including a new version of Outlook Web Access
with calendar support, support for IMAP4 and LDAP v3
clients and the Deleted Item Recovery feature.
1 History
Microsoft had sold a number of email products before
Exchange. Microsoft Mail v2.0 (written by Microsoft)
was replaced in 1991 by Microsoft Mail for PC Networks v2.1,[4] based on Network Courier, which Microsoft had acquired.[5] When the original version of Exchange Server was sold to the public, it was positioned as
an upgrade to Microsoft Mail 3.5.

1.3 Exchange Server 5.5

The last version of Exchange Server to have separate directory, SMTP and NNTP services. There was no new
version of Exchange Client and Schedule+ for version
5.5, instead version 8.03 of Microsoft Outlook was released to support the new features of Exchange Server
Exchange Server was an entirely new X.400-based client 5.5.
server mail system with a single database store that also It was sold in two editions: Standard and Enterprise. They
supported X.500 directory services. During its develop- dier in database store size, mail transport connectors and
ment Microsoft migrated their own internal email from clustering capabilities.
a XENIX-based system to Exchange Server from April
1993,[6] with all 32,000 Microsoft mailboxes on ExStandard Edition Had the same 16 GB database size
change by late 1996.[6][7]
limitation as earlier versions of Exchange Server.
The directory used by Exchange Server eventually beIt included the Site Connector, MS Mail Conneccame Microsofts Active Directory service, an LDAPtor, Internet Mail Service (previously Internet Mail
compliant directory service. Active Directory was inteConnector), and Internet News Service (previously
grated into Windows 2000 as the foundation of Windows
Internet News Connector), as well as software to
Server domains.
interoperate with cc:Mail, Lotus Notes and Novell
GroupWise.

1.1

Exchange Server 4.0

Enterprise Edition Had an increased limit of 16 TB

(although Microsofts best practices documentation
The rst release of Exchange outside of Microsoft was
recommends that the message store not exceed 100
Exchange Server 4.0 in March 1996,[8] with ve service
GB). Adds an X.400 connector, and interoperability
1

HISTORY

software with SNADS and PROFS. Introduced two sage and mailbox management tools, which allow adminnode clustering capability.
istrators to execute common chores more quickly. Others, such as Instant Messaging and Exchange Conferencing Server have been extracted completely in order to
1.4 Exchange Server 2000
form separate products. Microsoft now appears to be positioning a combination of Microsoft Oce, Microsoft
Codenamed Platinum, this version overcame many of Oce Live Communications Server, Live Meeting and
the limitations of its predecessors. For example, it raised SharePoint as its collaboration software of choice. Exthe maximum sizes of databases and increased the num- change Server is now to be simply e-mail and calendarber of servers in a cluster from two to four. However, ing.
many customers were deterred from upgrading by the reExchange Server 2003 added several basic ltering methquirement for a full Microsoft Active Directory infrasods to Exchange Server. They are not sophisticated
tructure to be in place, as unlike Exchange Server 5.5,
enough to eliminate spam, but they can protect against
Exchange 2000 Server had no built-in Directory Service,
DoS and mailbox ooding attacks. Exchange Server
and had a dependency upon Active Directory. The mi2000 supported the ability to block a senders address, or
gration process from Exchange Server 5.5 necessitated
e-mail domain by adding '*@domain.com', which is still
having the two systems online at the same time, with usersupported in Exchange Server 2003.
to-mailbox mapping and a temporary translation process
between the two directories. Exchange 2000 Server also
added support for instant messaging, but that capability 1.5.1 New features
was later spun o to Microsoft Oce Live Communications Server.
Added ltering methods in Exchange Server 2003 are:

1.5

Exchange Server 2003

Codenamed Titanium, this version can be run on

Windows 2000 Server (only if Service Pack 4 is rst installed) and 32-bit Windows Server 2003, although some
new features only work with the latter. Like Windows
Server 2003, Exchange Server 2003 has many compatibility modes to allow users to slowly migrate to the new
system. This is useful in large companies with distributed
Exchange Server environments who cannot aord the
downtime and expense that comes with a complete migration.

Connection ltering: Messages are blocked from

DNS RBL lists[11] or from manually specied IP addresses/ranges
Recipient ltering: Messages blocked when sent
to manually specied recipients on the server (for
intranet-only addresses) or to any recipients not on
the server (stopping spammers from guessing addresses)
Sender ID ltering: Sender ID, a form of Sender
Policy Framework (SPF)

Intelligent Message Filter: Initially a free MiIt made the migration from pre-2000 versions of Excrosoft add-on, later, part of service pack 2, that
change signicantly easier (although still involved the
uses heuristic message analysis to block messages or
same basic steps), and many users of Exchange Server
direct them to the Junk E-Mail folder in Microsoft
5.5 waited for the release of Exchange Server 2003 to
Outlook clients.[12]
upgrade. The upgrade process also required upgrading
a companys servers to Windows 2000. Some customers It is included with both Windows Small Business Server
opted to stay on a combination of Exchange Server 5.5 2003 Standard and Premium editions.
and Windows NT 4.0, both of which are no longer supported by Microsoft.
1.5.2 Editions
One of the new features in Exchange Server 2003 is en[10]
hanced disaster recovery, which allows administrators
Standard Edition:
to bring the server online more quickly. This is done by
allowing the server to send and receive mail while the
Supports up to two storage groups (with one of the
message stores are being recovered from backup. Some
storage groups, called the recovery storage group,
features previously available in the Microsoft Mobile Inbeing reserved for database recovery operations) and
formation Server 2001/2002 products have been added
a maximum of two databases per storage group.
to the core Exchange Server product, like Outlook Mobile Access and server-side Exchange ActiveSync, while
Each database is limited to a maximum size of 16
the Mobile Information Server product itself has been
GB.
dropped. Also new is the ability to drop inbound e-mail
Beginning with the release of Service Pack 2, a maxbefore being fully processed, thus preventing delays in the
imum database size of 75 GB, but only supports
message routing system. There are also improved mes-

1.7

Exchange Server 2010

16 GB by default; larger sized databases have to be
updated-in with a registry change.[13]

Enterprise Edition allows a 16 TB maximum database

size, and supports up to four storage groups with 5
databases per storage group for a total of 20 databases
per server.
Exchange 2003 mainstream support ended on April 14,
2009.[14] Extended support ended on April 8, 2014.[15]

1.6

Exchange Server 2007

Released to business customers as part of Microsofts

roll-out wave of new products. It includes new clustering
options, x64 support for greater scalability, voice mail integration, better search and support for Web services, better ltering options, and a new Outlook Web Access interface. Exchange 2007 also dropped support for Exchange
5.5 migrations, routing groups, admin groups, Outlook
Mobile Access, X.400, and some API interfaces, amongst
other features.[16]
Exchange Server 2007 (v8, code name E12, or with
SP1 v8.1) runs only on x64 versions of Windows Server.
This requirement applies to supported production environments only; a 32-bit trial version is available for download and testing. Hence, companies currently running
Exchange Server on 32-bit hardware will be required
to replace or migrate hardware if they wish to upgrade
to the new version. Companies that are currently running Exchange Server on 64-bit capable hardware are
still required to migrate from their existing Exchange
2000/2003 servers to a new 2007 server since in-place
upgrades are not supported in 2007.

3
improved deployment, role separation, simplied
routing
Exchange Management Shell: a new commandline shell and scripting language for system administration (based on Windows PowerShell). Shell users
can perform every task that can be performed in the
Exchange Server graphical user interface plus additional tasks, and can program often-used or complex tasks into scripts that can be saved, shared, and
re-used. The Exchange Management Shell has over
375 unique commands to manage features of Microsoft Exchange Server 2007.[19]
Unied Messaging: Lets users receive voice
mail, e-mail, and faxes in their mailboxes, and lets
them access their mailboxes from cell phones and
other wireless devices. Voice commands can be
given to control and listen to e-mail over the phone
(and also send some basic messages, like I'll be
late)
Increased database maximum size limit:
Database size is now limited to 16TB per
database[20]
Increased maximum storage groups and mail
databases per server: 5 each for Standard Edition
(from one each in Exchange Server 2003 Standard),
and to 50 each for Enterprise Edition (from 4 groups
and 20 databases in Exchange Server 2003 Enterprise).
Congure Outlook Anywhere: Formerly known
as RPC over HTTP provides external access to Microsoft Exchange Server 2007 for users. This also
provides external URLs for Exchange services such
as the Availability service and oine address book.

The rst beta of Exchange Server 2007 (then named Exchange 12 or E12) was released in December 2005 to a
very limited number of beta testers. A wider beta was
made available via TechNet Plus and MSDN subscriptions in March 2006 according to the Microsoft Exchange 1.6.2 Editions
team blog.[17] On April 25, 2006, Microsoft announced
that the next version of Exchange Server would be called Standard edition Can have 5 databases in up to 5 storExchange Server 2007.
age groups. Supports LCR (Local Continuous
Replication) and SCR (Standby Continuous RepliExchange Server 2007 is an integrated part of the
[18]
cation).
Innovative Communications Alliance products.

Enterprise edition This is extended to 50 databases in

up to 50 storage groups. Supports LCR (Local
Continuous Replication), SCR (Standby Continuous
Protection: Anti-spam, antivirus, compliance,
Replication), SCC (Single Copy Clustering), and
clustering with data replication, improved security
CCR (Clustered Continuous Replication).
and encryption

1.6.1

New features

Improved Information Worker Access: Improved

calendaring, unied messaging, improved mobility, 1.7 Exchange Server 2010
improved web access
Exchange Server 2010 was released to manufacturing on
Improved IT Experience: 64-bit performance and May 2009, and reached general availability on November
scalability, command-line shell and simplied GUI, 9, 2009.[21]

HISTORY

crosoft IT was able to reduce hardware costs by 75%

during the migration from Exchange Server 2007 to
Exchange Server 2010.

Exchange Server 2010 logo

1.7.1

New features

DAG (Database Availability Groups): SCC,

CCR, LCR and site resiliency functionality SCR
have been replaced by DAG. It provides databaselevel high availability (as opposed to server level)
and supports a number of copies of each database
(number based on Exchange Edition) and exible
conguration (databases copies may be added / removed at will without requiring major server reconguration).
Client Access Server (CAS): High availability for
the Client Access Server role is provided by using
Client Access Server (CAS) arrays. A CAS array
can contain multiple Client Access Servers in an Active Directory site and provide a single name endpoint for client connections. CAS arrays cannot span
multiple Active Directory sites.
Mailbox Server Role may be combined with the
Client Access Server: In Exchange Server 2007,
a clustered mailbox server could not be combined
with any other roles. In Exchange Server 2010,
the Mailbox Server Role may be combined with the
Client Access Server and/or Hub Transport roles, regardless of whether or not the mailbox server participates in a Database Availability Group. However, since Database Availability Groups use Windows Failover Clustering, and Microsoft does not
support the combination of Windows Failover Clustering and Windows Network Load Balancing on the
same server, a multi-role deployment will require
the use of a 3rd party load balancer to provide load
balancing and fault tolerance for the Client Access
Server role.
RPC Client Access: With the introduction of the
RPC Client Access service, all Outlook clients access their mailbox database through the Client Access Server role. This abstraction layer allows for
improved load balancing and redundancy and minimal client impact in the event of a database level
*-over (switchover or failover) event.
Cost savings in required hardware: Exchange
Server 2010 provides cost savings in required hardware. Storage performance requirements (measured
in IOPS: Input/output operations per second) have
been reduced by approximately 70% over Exchange
Server 2007, and by approximately 90% over Exchange Server 2003. According to a case study, Mi-

Personal Archive: Exchange Server 2010 extends

the large mailbox support introduced in Exchange
Server 2007, and also introduces a Personal Archive
feature to allow messages to be retained longer without the need for a third-party archival system. The
Personal Archive is implemented as a secondary
mailbox for archive-enabled users, and in Exchange
Server 2010 Service Pack 1, the Personal Archive
may be located on a dierent database than the primary mailbox, which may reside on a dierent disk
if desired. Backup can be performed via multiple
solutions like Handy Backup or Acronis.
Recoverable Items: The compliance and legal
search features have been enhanced. What was formerly known as the Dumpster in previous versions
of Exchange (a special storage area for messages that
have been deleted from the Deleted Items folder or
permanently deleted from a regular folder, such
as the Inbox) has been evolved into the Recoverable
Items folder in Exchange Server 2010. If congured appropriately, the Recoverable Items folder allows for a tamper proof storage area (users cannot
circumvent the Recoverable Items folder to bypass
legal discovery), which also provides a revision history of any modied items.
Administration delegation: Can now be performed at a granular level due to Exchange Server
2010s implementation of Role Based Access Control (RBAC). Users and administrators can be given
extremely ne grained abilities for functions provided both within the Exchange Management Console or Exchange Management Shell and in Outlook
Web App. For example, a compliance ocer may
be given the ability to perform cross mailbox discovery searches within Outlook Web App; a help desk
technician may be granted the ability to set an Out
Of Oce message for other employees within the
company, or a branch administrator in a remote ofce may be granted the permission to perform specic Exchange Management Shell commands that
pertain only to the Exchange server in their branch
oce.
Outlook Web App includes improvements: Including, for example, the ability for users to track
their sent messages and printable calendar views and
the Premium experience is now available across
multiple browsers (including Safari and Firefox).
Distribution groups can now be moderated:
Meaning that distribution groups can now be congured to allow users to join at will or only with a
group moderators permission, and individual messages sent to distribution groups can now be approved or denied by a moderator.

1.9

Exchange Server 2016

Shadow Redundancy: Exchange Server 2010

introduces a transport concept called Shadow Redundancy that protects e-mail messages while they
are in transit. If a Hub Transport server or an Edge
Transport server fails after it has received a message
for processing, but before it was able to deliver it to
the next hop server, the server sending the message to the transport server is now able to detect the
failure and redeliver the message to a dierent Hub
Transport or Edge Transport server for processing...
1.7.2

Editions

Several high-availability options have been consolidated

into just one option for Exchange Server 2010 (Mailbox Resiliency), which is now oered in both the Standard and Enterprise editions. The capabilities of Local Continuous Replication, Standby Continuous Replication, and Cluster Continuous Replication are now unied into the Exchange 2010 Mailbox Resiliency capability. These capabilities enable a simplied approach to
high availability and disaster recovery. The Standard Edition supports up to 5 databases with each database being
limited to a maximum size of 16 TB. While the Enterprise Edition supports up to 100 databases with no size
limit.
Storage group is no more in Exchange 2010 and onwards.
In January 2011, Microsoft Exchange Server 2010 won
InfoWorlds 2011 Technology of the Year Award for Best
Mail Server.

1.8

Exchange Server 2013

Microsoft reached the RTM milestone for Exchange

Server 2013 on October 11, 2012.[22] A trial version of
this product is available from Microsoft website.[23]
1.8.1

New features

New features include:[24][25][26][27]

Oine support in OWA: Emails and actions are
automatically synced the next time connectivity is
restored.
Client connectivity: CAS role is the point of connectivity for all clients in Exchange 2013.
Public folders: In 2013, public folders are now
part of mailbox databases and high availability is
achieved using DAG.
Site Mailboxes: Brings Exchange emails and
SharePoint documents together.

5
Ability to customize: Outlook and OWA by integrating apps from the Oce marketplace. (Yes,
this is a reference to the Agaves add-ins that Microsoft and partners will be making available via the
new Oce Store.) The new Napa tools and/or
HTML5 are Microsofts preferred ways for developers to build these.
Exchange Administrative Center (EAC): Replacement of the Exchange Management Console
by a Web-based Exchange Administrative Center
(EAC).
Support for up to 8TB disks: And multiple
databases per disk via Data Availability Group
(DAG) management.
Built in basic anti-malware protection: Ability
for administrators to congure and manage settings
from inside EAC. (Note: this feature can be turned
o, replaced or paired with premium services such
as Exchange Online Protection for layered protection.).
New Data Loss Prevention (DLP): Capabilities
for identifying and protecting sensitive data. DLP
policies are based on regulatory standards, including
PII and PCI. Also: new policy tips in Outlook 2013
can be set to inform users about potential policy violations.
In-Place eDiscovery: Can be run across Exchange,
SharePoint, and Lync from a single interface.
Combine Roles: A reduction in the number of
available roles to two: a Client Access Server and
a Mailbox Server role.
FAST Search: Now integrated into Exchange 2013
managed store to provide a more consistent (across
Microsoft servers) indexing and searching experience.
Inclusion of a Managed Store: The name of
the rewritten information store processes, which are
now written in C#.
Replication: Public folders are now stored in mailbox databases and can take advantage of Database
Availability Groups for replication and high availability.
Data loss prevention: Capabilities that can be integrated into Transport Rules.

1.9 Exchange Server 2016

Outlook Web App: Oers three dierent UI layouts optimized for desktop, tablet, and mobile phone On October 1, 2015, Microsoft announced the general
browsers.
availability (GA) of Exchange Server 2016.[28]

3 LICENSING

1.9.1

New features

Combine Roles: A reduction in the number of

available roles to two: a Mailbox Server and an Edge
Transport (intended only in certain Oce 365 hybrid scenarios).
Outlook on the web (formerly Outlook Web
App): UI changes
Oce 365 hybrid: The Hybrid Conguration Wizard (HCW) that was included with Exchange 2013 is
moving to become a cloud-based application. When
one chooses to congure a hybrid deployment in Exchange 2016, you'll be prompted to download and
install the wizard as a small app.
Messaging policy and compliance: New DLP and
Archiving/Retention/eDiscovery features.
For more detail on new features, see the following Microsoft TechNet article: Whats new in Exchange 2016

ServiceMajority Node Set) clusters, which do not require shared storage. This type of cluster can be inexpensive and deployed in one, or stretched across two
data centers for protection against site-wide failures such
as natural disasters. The limitation of CCR clusters is the
ability to have only two nodes and the third node known
as voter node or le share witness that prevents split
brain[35] scenarios, generally hosted as a le share on a
Hub Transport Server. The second type of cluster is the
traditional clustering that was available in previous versions, and is now being referred to as SCC (Single Copy
Cluster). In Exchange Server 2007 deployment of both
CCR and SCC clusters has been simplied and improved;
the entire cluster install process takes place during Exchange Server installation. LCR or Local Continuous
Replication has been referred to as the poor mans cluster. It is designed to allow for data replication to an alternative drive attached to the same system and is intended
to provide protection against local storage failures. It does
not protect against the case where the server itself fails.

In November 2007, Microsoft released SP1 for Exchange

Server 2007. This service pack includes an additional
2 Clustering and high availability high-availability feature called SCR (Standby Continuous Replication). Unlike CCR, which requires that both
Exchange Server Enterprise Edition supports clustering servers belong to a Windows cluster typically residing in
of up to 4 nodes when using Windows 2000 Server, and the same datacenter, SCR can replicate data to a nonup to 8 nodes with Windows Server 2003. Exchange clustered server, located in a separate datacenter.
Server 2003 also introduced active-active clustering, but With Exchange Server 2010, Microsoft introduced the
for two-node clusters only. In this setup, both servers in concept of the Database Availability Group (DAG). A
the cluster are allowed to be active simultaneously. This DAG contains Mailbox servers that become members of
is opposed to Exchanges more common active-passive the DAG. Once a Mailbox server is a member of a DAG,
mode in which the failover servers in any cluster node the Mailbox Databases on that server can be copied to
cannot be used at all while their corresponding home other members of the DAG. When a Mailbox server is
servers are active. They must wait, inactive, for the home added to a DAG, the Failover Clustering Windows role
servers in the node to fail. Subsequent performance is- is installed on the server and all required clustering resues with active-active mode have led Microsoft to rec- sources are created.
ommend that it should no longer be used.[29] In fact, support for active-active mode clustering has been discontinued with Exchange Server 2007.
Exchanges clustering (active-active or active-passive
mode) has been criticized because of its requirement for
servers in the cluster nodes to share the same data. The
clustering in Exchange Server provides redundancy for
Exchange Server as an application, but not for Exchange
data.[30] In this scenario, the data can be regarded as a
single point of failure, despite Microsofts description of
this set-up as a Shared Nothing model.[31] This void has
however been lled by ISVs and storage manufacturers,
through site resilience solutions, such as geo-clustering
and asynchronous data replication.[32] Exchange Server
2007 introduces new cluster terminology and congurations that address the shortcomings of the previous
shared data model.[33]

3 Licensing

Like Windows Server products, Exchange Server requires client access licenses, which are dierent from
Windows CALs. Corporate license agreements, such
as the Enterprise Agreement, or EA, include Exchange
Server CALs. It also comes as part of the Core CAL.
Just like Windows Server and other server products from
Microsoft, there is the choice to use User CALs or Device CALs. Device CALs are assigned to devices (workstation, laptop or PDA), which may be used by one or
more users.[36] User CALs, are assigned to users, allowing them to access Exchange from any device. User and
Device CALs have the same price, however, they cannot
Exchange Server 2007 provides built-in support for asyn- be used interchangeably.
chronous replication modeled on SQL Servers "Log ship- For service providers looking to host Microsoft Exping"[34] in CCR (Cluster Continuous Replication) clus- change, there is a Service Provider License Agreement
ters, which are built on MSCS MNS (Microsoft Cluster (SPLA) available whereby Microsoft receives a monthly

7
service fee instead of traditional CALs. Two types of Exchange Server 2010 was developed concurrently as a
Exchange CAL are available: Exchange CAL Standard server product and for the Exchange Online service.
and Exchange CAL Enterprise. The Enterprise CAL is
an add-on license to the Standard CAL.

Exchange hosting

6 Clients

Microsoft Exchange Server can also be purchased as a

hosted service from a number of providers.[37] Though
Exchange hosting has been around for more than 10
years, it is only recently that many providers have
been marketing the service as Cloud Computing or
Software-as-a-Service. Exchange hosting allows for Microsoft Exchange Server to be running in the Internet,
also referred to as the Cloud, and managed by a Hosted
Exchange Server provider instead of building and deploying the system in-house.

Microsoft Exchange Server uses a proprietary remote

procedure call (RPC) protocol called MAPI/RPC,[41]
which was designed to be used by Microsoft Outlook.
Clients capable of using the proprietary features of Exchange Server include Evolution[42] and Microsoft Outlook. Exchange Web Services (EWS), an alternative to
the MAPI protocol, is a documented SOAP-based protocol introduced with Exchange Server 2007, which significantly reduces synchronization time between the server
versus WebDAV, which is used by Exchange Server
2003. Exchange Web Services is used by the latest version of Microsoft Entourage for Mac and Microsoft Outlook for Mac. Also, since the release of Mac OS X Snow
5 Exchange Online
Leopard, Mac computers running OS X include some
support for this technology via Apples Mail application.
Microsoft Exchange Online is an email, calendar and Built-in support with Mac OS X 10.6 requires the Excontacts solution delivered as a cloud service, hosted change organization to be running Exchange Server 2007
by Microsoft. It is essentially the same service of- SP1/SP2 or Exchange Server 2010.
fered by hosted Exchange providers and it is built on the
E-mail hosted on an Exchange Server can also be acsame technologies as Microsoft Exchange Server. Excessed using SMTP, POP3 and IMAP4 protocols, using
change Online provides end users with a familiar email
clients such as Windows Live Mail, Mozilla Thunderbird,
experience across PCs, the Web and mobile devices,
and Lotus Notes. These protocols must be enabled on
while giving IT administrators or small businesses and
the server. Exchange Server mailboxes can also be acprofessionals web-based tools for managing their online
cessed through a web browser, using Outlook Web App
deployment.[38]
(OWA). Exchange Server 2003 also featured a version of
Microsoft Exchange is available both as on-premises soft- OWA for mobile devices, called Outlook Mobile Access
ware and as a hosted service with Exchange Online. Cus- (OMA).
tomers can also choose to combine both on-premises and
Microsoft Exchange Server up to version 5.0 came bunonline options in a hybrid deployment.
dled with Microsoft Exchange Client, a multi-purpose
Hybrid monitoring and reporting tools cover the main on- native client for email. After version 5.0, it was superpremises stack of Microsoft Exchange, Lync, SharePoint, seded by Microsoft Outlook, which was part of Microsoft
Windows, and Active Directory servers, in addition to Oce 97 and later.[43] When Outlook 97 was released,
using replica data to report cloud user experience. The Exchange Client 5.0 was still in development and to be
monitoring of servers is important to the optimal main- later released as part of Exchange Server 5.0, primarily
tenance of the server infrastructure, as well as, cloud re- because Outlook was only available for Windows. Later,
porting to monitor user experience.
in Exchange Server 5.5, Exchange Client was removed
and Outlook was made the only Exchange client. As part
of Exchange Server 5.5, Outlook was released for other
platforms.
5.1 History
Exchange Online was rst provided as a hosted service in
dedicated customer environments in 2005 to select pilot
customers.[39] Microsoft launched a multi-tenant version
of Exchange Online as part of the Business Productivity Online Standard Suite in November 2008.[40] In June
2011, as part of the commercial release of Microsoft Ofce 365, Exchange Online was updated with the capabilities of Exchange Server 2010.

The original Windows 95 Inbox client also used MAPI

and was called Microsoft Exchange. A stripped down
version of the Exchange Client that does not have support
for Exchange Server was released as Windows Messaging to avoid confusion; it was included with Windows 95,
Windows 98 and Windows NT 4. It was discontinued
because of the move to email standards such as SMTP,
IMAP, and POP3, all of which Outlook Express supports
better than Windows Messaging.

6.1

Exchange ActiveSync

Support for Exchange ActiveSync was added to Microsoft Exchange Server 2003. Exchange ActiveSync,
in the context of Exchange Server, allows a compliant
device such as a Windows Mobile device to securely
synchronize mail, contacts and other data directly with
an Exchange server. Since its inception, Exchange ActiveSync has become a popular mobile access standard
for businesses due to cross-platform support from companies like Nokia and Apple Inc.[44] as well as its advanced
device security and compliance features.

REFERENCES

[5] Paul Korzeniowski (1992). E-mail becoming foundation

for networked applications. Software Magazine. Retrieved 28 October 2012.
[6] Microsofts Migration to Microsoft Exchange Server.
TechNet. Retrieved 28 October 2012.
[7] Dr. Nikolai Bezroukov. XENIX Microsoft Short-lived
Love Aair with Unix. Softpanorama. Retrieved 28 October 2012.
[8] Redmond, Tony (31 March 1997). Microsoft Exchange
Server 5.0 Smoothes the Rough Edges. Windows IT Pro.
Penton.

Support for push email was added to Exchange Server

2003 with Service Pack 2. Windows Mobile 5.0 requires [9] Microsoft Support Lifecycle/Exchange Server, Microsoft.com
the Messaging and Security Feature Pack (MSFP)", later
versions of the mobile operating system, such as Win- [10] Vidhya (1992). Exchange Server backup and Disaster
dows Phone 7, have the capability built in.[45] Many other
Recovery. Software Magazine. Retrieved 28 October
devices now support Exchange ActiveSync push email,
2012.
such as the iPhone and Android Phones.[46] Exchange
Server 2007 and Exchange Server 2010 support the use of [11] Markus Klien (2003). Implementing and Conguring
Blacklist Support in Exchange Server 2003. MSExExchange ActiveSync Policies. By using Exchange Acchange. Retrieved 28 October 2012.
tiveSync Policies, administrators can secure the devices
that connect to the organization or remotely deactivate [12] Exchange Intelligent Message Filter. Microsoft. 2003.
features on the devices. Administrators or users can also
Retrieved 28 October 2012.
remotely wipe a lost mobile device.
Exchange Server 2013 supports the use of Mobile Exchange ActiveSync Policies.[47]

See also
Comparison of mail servers
Extensible Storage Engine
List of collaborative software
List of Microsoft - Nortel (ICA) Products
List of applications with iCalendar support

References

[1] Exchange Server build numbers and release dates. Microsoft. Retrieved 10 December 2015.
[2] Lextrait, Vincent (January 2010). The Programming
Languages Beacon, v10.0. Retrieved 14 March 2010.
[3] Richard Schwendiman (July 29, 2013). Exchange 2013:
Store, FAST, and ESE Cache DemystiedHopefully!
- Richard Schwendimans Blog - Site Home - TechNet
Blogs. blogs.technet.com. Retrieved January 27, 2016.
[4] The box says Microsoft Mail for PC Networks v2.1, but
under the hood users will nd Consumer Software Incs,
Network Courier..., August 26, 1991, Computerworld

[13] Registry tweak to set a 75gb store limit on Exchange

2003 Standard SP2. TechNet. 2005. Retrieved 28 October 2012.
[14] Microsoft Support Lifecycle. TechNet. 2007. Retrieved 28 October 2012.
[15] Microsoft Warns of Looming Exchange Server 2003
Support Deadline. Redmond Channel Partner. 2014.
Retrieved 8 April 2014.
[16] Discontinued Features and De-Emphasized Functionality in Exchange 2007. TechNet. 2005. Retrieved 28
October 2012.
[17] Terry Myerson (1 March 2006). Exchange 12 Beta 1
Community Technology Preview. The Microsoft Exchange Team Blog. Retrieved 28 October 2012.
[18] Elizabeth Montalbano (17 January 2007). Microsoft,
Nortel unveil ICAs rst products. InfoWorld. Retrieved
28 October 2012.
[19] Cmdlet List. Microsoft. Retrieved January 27, 2016.
[20] Rodney Buike. Understanding the Exchange Information
Store. Retrieved 2008-12-19.
[21] Elizabeth Montalbano (9 November 2009). Microsoft
releases Exchange 2010, acquires Teamprise. Beyond
Binary - CNET News. Retrieved 28 October 2012.
[22] The New Exchange Reaches RTM!". The Exchange
Team Blog. 11 October 2012. Retrieved 28 October
2012.
[23] Microsoft Exchange Server 2013 Trial. TechNet. Retrieved 17 November 2012.

[24] Rajith Enchiparambil (2013). Exchange 2013 - Points to

note. theucguy.net. Retrieved 11 February 2013.

[44] Microsoft Exchange ActiveSync Licensees. Microsoft.

Retrieved 28 October 2012.

[25] Mary Jo Foley (23 July 2012). Microsofts Exchange

Server 2013: Whats new. ZDNet.com. Retrieved 28
October 2012.

[45] Exchange ActiveSync: Frequently Asked Questions.

TechNet. Retrieved 28 October 2012.

[26] Paul Cunningham (2012). New Features in Exchange

Server 2013. exchangeserverpro.com. Retrieved 28 October 2012.

[46] Exchange ActiveSync. Apple. Retrieved 28 October

2012.
[47] Apple - iPhone in Business. TechNet. Retrieved 28
October 2012.

[27] Changes in Exchange 2013 Preview. eighttwone.com.

2012. Retrieved 28 October 2012.
[28] Exchange Server 2016: Forged in the cloud. Now available on-premises.. Retrieved January 27, 2016.
[29] Considerations when deploying Exchange on an Active/Active cluster. Microsoft. Retrieved 28 October
2012.
[30] The benets of Windows 2003 clustering with Exchange
2003. The Exchange Team Blog. 9 June 2004. Retrieved
28 October 2012.
[31] Exchange Clustering Concepts. TechNet. 9 February
2006. Retrieved 28 October 2012.
[32] Storage Glossary: Basic Storage Terms. TechNet. 8
March 2005. Retrieved 28 October 2012.
[33] High availability. TechNet. 8 March 2005. Retrieved 2
July 2007.
[34] Frequently asked questionsSQL Server 2000Log
shipping. Microsoft. 8 March 2005. Retrieved 28 October 2012.
[35] An update is available that adds a le share witness feature and a congurable cluster heartbeats feature to Windows Server 2003 Service Pack 1-based server clusters.
Microsoft. Retrieved 28 October 2012.
[36] Top 75 Microsoft Licensing Terms A Glossary From
A(ntigen) To Z(une)". OMTCO, omt-co Operations
Management Technology Consulting GmbH. Retrieved
24 April 2013.
[37] Hosted Exchange Partner Directory. Microsoft. Retrieved 28 October 2012.
[38] Microsoft Exchange Online for Enterprises Service Description. Microsoft. Retrieved 28 October 2012.
[39] Ina Fried (10 March 2005). Microsoft hops into managed PC business. CNET News. Retrieved 28 October
2012.
[40] Microsoft hops into managed PC business. Microsoft.
7 November 2008. Retrieved 28 October 2012.
[41] Exchange Server Protocols. Microsoft. 7 November
2008. Retrieved 28 October 2012.
[42] Evolution/FAQ - GNOME Live!". Microsoft. Retrieved
28 October 2012.
[43] What is the Microsoft Exchange client?".

9 External links
Ocial website

10

10

10
10.1

TEXT AND IMAGE SOURCES, CONTRIBUTORS, AND LICENSES

Text and image sources, contributors, and licenses

Text

Microsoft Exchange Server Source: https://en.wikipedia.org/wiki/Microsoft_Exchange_Server?oldid=703888928 Contributors: Nate

Silva, Edemaine, LionKimbro, Edward, Modster, Nixdorf, Lousyd, Ixfd64, Haakon, Disdero, Zbnet, Andrewman327, LMB, Joy, Indefatigable, Northgrove, Chealer, Fredrik, DocWatson42, Zigger, Marcika, Varlaam, EJDyksen, Pascal666, AlistairMcMillan, Khalid
hassani, Alex Libman, Alexf, Beland, Jesster79, Ohura, EagleOne, Ta bu shi da yu, Diagonalsh, Pmsyyz, Orbital, Abelson, TimBray, Bender235, Vt100, Syp, PPGMD, Newtronic, Bobo192, Nigelj, Stesmo, Apyule, Richi, Gary, Cee, Rebroad, Stephan Leeds, Chilly Penguin,
Btornado, Mindmatrix, SusanLarson, Pol098, Wayward, Marudubshinki, Royan, Rjwilmsi, Digemedi, Carbonite, R.O.C, Gilesmorant,
Aapo Laitinen, FlaBot, Fragglet, Czar, Riki, NevilleDNZ, Chobot, Bgwhite, NSR, Peterl, Jim.Liu, RobotE, RussBot, Stevenbdjr, Richard
Slater, Gardar Rurak, Yuhong, Rsrikanth05, Cleared as led, Mikeblas, Vlad, Jeremy Visser, Xpclient, Cloudbound, Chrissawer, JLaTondre, Katieh5584, Mardus, Draicone, Veinor, SmackBot, Vryl, Reedy, Od Mishehu, Scott Paeth, Gilliam, DStoykov, Snori, Deli nk,
U, BoKu, Abrahami, Thewyzewun, Warren, Lord Eru, Fdiv bug, Kennedye, Dogears, Keramos, Wikiolap, Nort~enwiki, SuperTycoon,
Kuru, Euchiasmus, Soumyasch, Sir Nicholas de Mimsy-Porpington, Waggers, Tmcw, EEPROM Eagle, BranStark, Wikidear, Tawkerbot2,
CmdrObot, Th.held~enwiki, Cydebot, Pyeman73, Valodzka, A876, Gogo Dodo, Mtlk, Odie5533, Lofote, Iliank, Kozuch, Njan, Smiteri,
Thijs!bot, Majid ahmadi, Eastmain, Vertium, X201, TechSoEasy, Zachary, Big Bird, Natalie Erin, Hmrox, Zack Howes, Gioto, Widefox,
Raitchison, Darklilac, Leuqarte, JAnDbot, MER-C, .anacondabot, Meeples, Mondebleu, Tedickey, IzKen, OceanO, Lakorai, Danieleran,
Keandobus, Panarchy, CommonsDelinker, Tumbleweed05, J.delanoy, Trusilver, SaxicolousOne, Svenster~enwiki, Kudpung, Jmcw37, Jhwinder, Simontbates, Bonadea, VolkovBot, Alanfeld, Picassob, Canaima, Lwc, Sambellajoe, Xp fun, Logan, Edomenig, Gbawden, Gohan71, Bsoo, Yintan, Joel8r, Jdaloner, OKBot, Dekaptein, BfMGH, L337h1um, Wdavidpence, ClueBot, Mdlueck, Hutcher, RobertL,
Pelekan, Mild Bill Hiccup, Jonathonblocker, Brionwong, SuperHamster, Bsuneja, Alexbot, Panyd, EhJJ, Unused000706, MelonBot, Vanished user uih38riiw4hjlsd, Aardila, XLinkBot, WikHead, Addbot, Ghettoblaster, Jonbryce, Guoguo12, Zellfaze, WinCEB, AndersBot,
Jasper Deng, West.andrew.g, Bwrs, Lightbot, Dcs78, Zorrobot, Yobot, Bunnyhop11, Senator Palpatine, Twojenkins, Omarmalali, Dmarquard, AnomieBOT, Dperegudov, Materialscientist, Citation bot, LilHelpa, Cameron Scott, Xqbot, Shouran, Teguhth, TheCuriousGnome,
Sourceholder, Jmundo, Shadowjams, Erik9, FrescoBot, Sunnybanthiya, Amplitude101, Redrose64, Andy1979s, Shshme, Chunt006, I
dream of horses, Maginks, 95j, Tdada, Backdoor2world, Infostellar, Full-date unlinking bot, Retired user 0001, LogAntiLog, Mishra78, Tbhotch, Melnakeeb, Vin1317, Perhelion, RjwilmsiBot, JohnExchange, EmausBot, Timtempleton, Heracles31, XantiSS, Dewritech, Pah861,
MaxMVP, Kkm010, Superiaklubbene, OnePt618, DB111,
, , Donner60, MainFrame, Frozen Wind, Diamondland, Kypr8, ClueBot NG, Jack Greenmaven, WikIan, Meirpolaris, Kmchanw, Delfassy, Widr, Helpful Pixie Bot, BG19bot, Annvu, Frze, Wolscmip,
Lenin1234, Compfreak7, H7, Craigcarry1, Riley Huntley, Mrt3366, Khazar2, EagerToddler39, Codename Lisa, Mendel129, Mogism,
Pritchardavid, Bwmcq, Frosty, Wikicrowley, Reatlas, JypeeM, Tentinator, Sanjayntms, Babitaarora, CV9933, JeremiahY, Ericsimson5,
GRAND RADION and Anonymous: 525

10.2

Images

File:Ambox_important.svg Source: https://upload.wikimedia.org/wikipedia/commons/b/b4/Ambox_important.svg License: Public domain Contributors: Own work, based o of Image:Ambox scales.svg Original artist: Dsmurat (talk contribs)
File:Commons-logo.svg Source: https://upload.wikimedia.org/wikipedia/en/4/4a/Commons-logo.svg License: CC-BY-SA-3.0 Contributors: ? Original artist: ?
File:Edit-clear.svg Source: https://upload.wikimedia.org/wikipedia/en/f/f2/Edit-clear.svg License: Public domain Contributors: The
Tango! Desktop Project. Original artist:
The people from the Tango! project. And according to the meta-data in the le, specically: Andreas Nilsson, and Jakub Steiner (although
minimally).
File:Exchange-2010logo.svg Source: https://upload.wikimedia.org/wikipedia/commons/8/8b/Exchange-2010logo.svg License: Public
domain Contributors: http://www.microsoft.com/exchange/en-us/downloads-and-trials.aspx (Direct link)
Original artist:
Microsoft Corporation
File:Folder_Hexagonal_Icon.svg Source: https://upload.wikimedia.org/wikipedia/en/4/48/Folder_Hexagonal_Icon.svg License: Cc-bysa-3.0 Contributors: ? Original artist: ?
File:Internet-mail.svg Source: https://upload.wikimedia.org/wikipedia/commons/5/54/Internet-mail.svg License: Public domain Contributors: The Tango! Desktop Project Original artist: Jakub Steiner; contributor Andreas Nilsson; The people from the Tango! project
File:M_box.svg Source: https://upload.wikimedia.org/wikipedia/commons/9/94/M_box.svg License: Public domain Contributors: Own
work based on: File:Microsoft.svg Original artist: Ariesk47 (<a href='//commons.wikimedia.org/wiki/User_talk:Ariesk47' title='User
talk:Ariesk47'>talk</a>)
File:Microsoft_Exchange_logo.png Source: https://upload.wikimedia.org/wikipedia/commons/2/22/Microsoft_Exchange_logo.png License: Public domain Contributors: http://www.microsoft.com/exchange/en-us/mobile-email-with-exchange-activesync.aspx Original
artist: Microsoft
File:Microsoft_logo.svg Source: https://upload.wikimedia.org/wikipedia/commons/4/44/Microsoft_logo.svg License: Public domain
Contributors: www.microsoft.com Original artist: Microsoft
File:People_icon.svg Source: https://upload.wikimedia.org/wikipedia/commons/3/37/People_icon.svg License: CC0 Contributors: OpenClipart Original artist: OpenClipart
File:Question_book-new.svg Source: https://upload.wikimedia.org/wikipedia/en/9/99/Question_book-new.svg License: Cc-by-sa-3.0
Contributors:
Created from scratch in Adobe Illustrator. Based on Image:Question book.png created by User:Equazcion Original artist:
Tkgd2007

10.3

10.3

Content license

Content license

Creative Commons Attribution-Share Alike 3.0

11