Microsoft Exchange Server

Microsoft Exchange Server

Exchange Server 2013 and 2016 logo
Developer(s) Microsoft Corporation
Initial release April 11, 1993 (1993-04-11)
Stable release 2016 RTM (v15.01.0225.042) (October 1, 2015 (2015-10-01)) [±][1]
Development status Active
Written in C++,[2] C#[3]
Operating system Windows Server
Platform x64
Type Collaborative software
License Trialware
Website microsoft.com/exchange

Microsoft Exchange Server is a mail server and calendaring server developed by Microsoft. It runs exclusively on Windows Server operating systems.

Exchange Server was initially Microsoft's internal mail server. The first 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.

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 on-premises software and software as a service. In the on-premises form, customer purchase client access licenses (CALs). In the software as a service form, Microsoft receives a monthly service fee instead (see Microsoft Office 365).

History

Microsoft had sold a number of simpler email products before, but Exchange Server was an entirely new X.400-based client–server mail system with a single database store that also supported X.500 directory services. The directory used by Exchange Server eventually became Microsoft's Active Directory service, an LDAP-compliant directory service which was integrated into Windows 2000 as the foundation of Windows Server domains.

There have been a number of versions:

Exchange Server 2016

This is the current version, and was released on October 1, 2015[7] and introduced a number of new features, including:

For more detail on new features, see the following Microsoft TechNet article: What's new in Exchange 2016

Clustering and high availability

Exchange Server Enterprise Edition supports clustering of up to 4 nodes when using Windows 2000 Server, and up to 8 nodes with Windows Server 2003. Exchange Server 2003 also introduced active-active clustering, but for two-node clusters only. In this setup, both servers in the cluster are allowed to be active simultaneously. This is opposed to Exchange's more common active-passive mode in which the failover servers in any cluster node cannot be used at all while their corresponding home servers are active. They must wait, inactive, for the home servers in the node to fail. Subsequent performance issues with active-active mode have led Microsoft to recommend that it should no longer be used.[8] In fact, support for active-active mode clustering has been discontinued with Exchange Server 2007.

Exchange's 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.[9] In this scenario, the data can be regarded as a single point of failure, despite Microsoft's description of this set-up as a "Shared Nothing" model.[10] This void has however been filled by ISVs and storage manufacturers, through "site resilience" solutions, such as geo-clustering and asynchronous data replication.[11] Exchange Server 2007 introduces new cluster terminology and configurations that address the shortcomings of the previous "shared data model".[12]

Exchange Server 2007 provides built-in support for asynchronous replication modeled on SQL Server's "Log shipping"[13] in CCR (Cluster Continuous Replication) clusters, which are built on MSCS MNS (Microsoft Cluster Service—Majority 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 file share witness that prevents "split brain"[14] scenarios, generally hosted as a file 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 simplified 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 man's 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 high-availability feature called SCR (Standby Continuous Replication). Unlike CCR, which requires that both servers belong to a Windows cluster typically residing in the same datacenter, SCR can replicate data to a non-clustered server, located in a separate datacenter.

With Exchange Server 2010, Microsoft introduced the concept of the Database Availability Group (DAG). A DAG contains Mailbox servers that become members of the DAG. Once a Mailbox server is a member of a DAG, the Mailbox Databases on that server can be copied to other members of the DAG. When a Mailbox server is added to a DAG, the Failover Clustering Windows role is installed on the server and all required clustering resources are created.

Licensing

Like Windows Server products, Exchange Server requires client access licenses, which are different 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.[15] 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 be used interchangeably.

For service providers looking to host Microsoft Exchange, there is a Service Provider License Agreement (SPLA) available whereby Microsoft receives a monthly service fee instead of traditional CALs. Two types of Exchange CAL are available: Exchange CAL Standard and Exchange CAL Enterprise. The Enterprise CAL is an add-on license to the Standard CAL.

Clients

Microsoft Exchange Server uses a proprietary remote procedure call (RPC) protocol called MAPI/RPC,[16] which was designed to be used by Microsoft Outlook. Clients capable of using the proprietary features of Exchange Server include Evolution[17] 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 Leopard, Mac computers running OS X include some support for this technology via Apple's Mail application. Built-in support with Mac OS X 10.6 requires the Exchange organization to be running Exchange Server 2007 SP1/SP2 or Exchange Server 2010.

E-mail hosted on an Exchange Server can also be accessed using SMTP, POP3, and IMAP4 protocols, using clients such as Windows Live Mail, Mozilla Thunderbird, and Lotus Notes. These protocols must be enabled on the server. Exchange Server mailboxes can also be accessed through a web browser, using Outlook Web App (OWA). Exchange Server 2003 also featured a version of OWA for mobile devices, called Outlook Mobile Access (OMA).

Microsoft Exchange Server up to version 5.0 came bundled with Microsoft Exchange Client, a multi-purpose native client for email. After version 5.0, it was superseded by Microsoft Outlook, which was part of Microsoft Office 97 and later.[18] When Outlook 97 was released, Exchange Client 5.0 was still in development and to be later released as part of Exchange Server 5.0, primarily because Outlook was only available for Windows. Later, 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.

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.

Exchange ActiveSync

Support for Exchange ActiveSync was added to Microsoft Exchange Server 2003. It allows a compliant device such as a Windows Mobile device or smartphone to securely synchronize mail, contacts and other data directly with an Exchange server and has become a popular mobile access standard for businesses due to support from companies like Nokia and Apple Inc.[19] as well as its device security and compliance features.

Support for push email was added to Exchange Server 2003 with Service Pack 2 is supported by Windows Phone 7,[20] the iPhone and Android phones.[21]

Exchange ActiveSync Policies allow administrators to control which devices can connect to the organization, remotely deactivate features, and remotely wipe a lost or stolen device. [22]

Exchange Server hosted as a service

The complexities of managing Exchange Server make it attractive for organisations to purchase it as a hosted service.

Third-party providers

This has been possible from a number of providers[23] for more than 10 years, but 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

Microsoft Exchange Online is an email, calendar, and contacts solution delivered as a cloud service, hosted by Microsoft. It is essentially the same service offered by hosted Exchange providers and it is built on the same technologies as Microsoft Exchange Server. Exchange Online provides end users with a familiar email experience across PCs, the Web and mobile devices, while giving IT administrators or small businesses and professionals web-based tools for managing their online deployment.[24]

Microsoft Exchange is available both as on-premises software and as a hosted service with Exchange Online. Customers can also choose to combine both on-premises and online options in a hybrid deployment.

A hybrid deployment[25] can serve as an intermediate step between an on-premises and a fully hosted Exchange solution. This configuration provides a wealth of features such as allowing organizations to better migrate user mailboxes providing the ability to not only move on-premises mailboxes to Exchange Online, but from Exchange Online back to the on-premises server, cloud-based message archiving for on-premises mailboxes and centralized mailbox management for both infrastructures, to name a few.

With the necessity of on-premises servers; namely an Exchange Server and an Azure Active Directory synchronization server, there is a resource overhead to implement a hybrid solution. Hybrid implementations remain a popular choice for organizations that are unsure of the need or urgency to do a full cut-over to Exchange Online; also allowing for staggered email migration.

Hybrid monitoring and reporting tools cover the main on-premises stack of Microsoft Exchange, Lync, SharePoint, Windows, and Active Directory servers, in addition to using replica data to report cloud user experience. The monitoring of servers is important to the optimal maintenance of the server infrastructure, as well as, cloud reporting to monitor user experience.

History

Exchange Online was first provided as a hosted service in dedicated customer environments in 2005 to select pilot customers.[26] Microsoft launched a multi-tenant version of Exchange Online as part of the Business Productivity Online Standard Suite in November 2008.[27] In June 2011, as part of the commercial release of Microsoft Office 365, Exchange Online was updated with the capabilities of Exchange Server 2010.

Exchange Server 2010 was developed concurrently as a server product and for the Exchange Online service.

See also

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 Demystified…Hopefully! - Richard Schwendiman's Blog - Site Home - TechNet Blogs". blogs.technet.com. Retrieved January 27, 2016.
  4. ↑ Redmond, Tony (31 March 1997). "Microsoft Exchange Server 5.0 Smoothes the Rough Edges". Windows IT Pro. Penton.
  5. ↑ "Microsoft Support Lifecycle/Exchange Server", Microsoft.com
  6. ↑ Elizabeth Montalbano (9 November 2009). "Microsoft releases Exchange 2010, acquires Teamprise". Beyond Binary - CNET News. Retrieved 28 October 2012.
  7. ↑ "Exchange Server 2016: Forged in the cloud. Now available on-premises.". Retrieved January 27, 2016.
  8. ↑ "Considerations when deploying Exchange on an Active/Active cluster". Microsoft. Retrieved 28 October 2012.
  9. ↑ "The benefits of Windows 2003 clustering with Exchange 2003". The Exchange Team Blog. 9 June 2004. Retrieved 28 October 2012.
  10. ↑ "Exchange Clustering Concepts". TechNet. 9 February 2006. Retrieved 28 October 2012.
  11. ↑ "Storage Glossary: Basic Storage Terms". TechNet. Microsoft. 8 March 2005. Archived from the original on July 15, 2007. Retrieved 28 October 2012.
  12. ↑ "High availability". TechNet. 8 March 2005. Retrieved 2 July 2007.
  13. ↑ "Frequently asked questions—SQL Server 2000—Log shipping". Microsoft. 8 March 2005. Retrieved 28 October 2012.
  14. ↑ "An update is available that adds a file share witness feature and a configurable cluster heartbeats feature to Windows Server 2003 Service Pack 1-based server clusters". Microsoft. Retrieved 28 October 2012.
  15. ↑ "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.
  16. ↑ "Exchange Server Protocols". Microsoft. 7 November 2008. Retrieved 28 October 2012.
  17. ↑ "Evolution/FAQ - GNOME Live!". Microsoft. Retrieved 28 October 2012.
  18. ↑ "What is the Microsoft Exchange client?".
  19. ↑ "Microsoft Exchange ActiveSync Licensees". Microsoft. Retrieved 28 October 2012.
  20. ↑ "Exchange ActiveSync: Frequently Asked Questions". TechNet. Retrieved 28 October 2012.
  21. ↑ "Exchange ActiveSync". Apple. Retrieved 28 October 2012.
  22. ↑ "Apple - iPhone in Business". TechNet. Retrieved 28 October 2012.
  23. ↑ "Hosted Exchange Partner Directory". Microsoft. Retrieved 28 October 2012.
  24. ↑ "Microsoft Exchange Online for Enterprises Service Description". Microsoft. Retrieved 28 October 2012.
  25. ↑ Puca, Anthony (2013). Microsoft Office 365 Administration Inside Out. Microsoft Press. pp. 459–462. ISBN 978-0735678231.
  26. ↑ Ina Fried (10 March 2005). "Microsoft hops into managed PC business". CNET News. Retrieved 28 October 2012.
  27. ↑ "Microsoft hops into managed PC business". Microsoft. 7 November 2008. Retrieved 28 October 2012.
This article is issued from Wikipedia - version of the 12/3/2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.