Jump to content

Microsoft Exchange Server

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by 203.91.201.57 (talk) at 08:02, 8 April 2016 (→History). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Microsoft Exchange Server
Developer(s)Microsoft Corporation
Initial releaseApril 11, 1993; 31 years ago (1993-04-11)
Stable release2019 CU14 Apr24HU (15.02.1544.011)[1] (April 23, 2024; 7 months ago (2024-04-23)) [±]
Written inC++,[2] C#[3]
Operating systemWindows Server
Platformx64
TypeCollaborative software
LicenseTrialware
WebsiteExchange

Microsoft Exchange Server is a calendaring and mail server developed by Microsoft that runs exclusively on the Microsoft Windows Server product line.

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 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.

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. During its development Microsoft migrated their own internal email from a XENIX-based system to Exchange Server from April 1993,[6] with all 32,000 Microsoft mailboxes on Exchange by late 1996.[6][7]

The directory used by Exchange Server eventually became Microsoft's Active Directory service, an LDAP-compliant directory service. Active Directory was integrated into Windows 2000 as the foundation of Windows Server domains.

Exchange Server 4.0

The first release of Exchange outside of Microsoft was Exchange Server 4.0 in March 1996,[8] with five service packs being released over the next two years.[9]

Exchange Server 5.0

Introduced the new Exchange Administrator console, as well as opening up "integrated" access to SMTP-based networks for the first 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 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.

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 5.5.

It was sold in two editions: Standard and Enterprise. They differ in database store size, mail transport connectors and clustering capabilities.

Standard Edition
Had the same 16 GB database size limitation as earlier versions of Exchange Server. It included the Site Connector, MS Mail Connector, Internet Mail Service (previously "Internet Mail Connector"), and Internet News Service (previously "Internet News Connector"), as well as software to interoperate with cc:Mail, Lotus Notes and Novell GroupWise.
Enterprise Edition
Had an increased limit of 16 TB (although Microsoft's best practices documentation recommends that the message store not exceed 100 GB). Adds an X.400 connector, and interoperability software with SNADS and PROFS. Introduced two node clustering capability.

Exchange Server 2000

Codenamed "Platinum", this version overcame many of the limitations of its predecessors. For example, it raised the maximum sizes of databases and increased the number of servers in a cluster from two to four. However, many customers were deterred from upgrading by the requirement for a full Microsoft Active Directory infrastructure to be in place, as unlike Exchange Server 5.5, Exchange 2000 Server had no built-in Directory Service, and had a dependency upon Active Directory. The migration process from Exchange Server 5.5 necessitated having the two systems online at the same time, with user-to-mailbox mapping and a temporary translation process between the two directories. Exchange 2000 Server also added support for instant messaging, but that capability was later spun off to Microsoft Office Live Communications Server.

Exchange Server 2003

Codenamed "Titanium", this version can be run on Windows 2000 Server (only if Service Pack 4 is first 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 afford the downtime and expense that comes with a complete migration.

It made the migration from pre-2000 versions of Exchange significantly easier (although still involved the same basic steps), and many users of Exchange Server 5.5 waited for the release of Exchange Server 2003 to upgrade. The upgrade process also required upgrading a company's servers to Windows 2000. Some customers opted to stay on a combination of Exchange Server 5.5 and Windows NT 4.0, both of which are no longer supported by Microsoft.

One of the new features in Exchange Server 2003 is enhanced disaster recovery,[10] which allows administrators to bring the server online more quickly. This is done by allowing the server to send and receive mail while the message stores are being recovered from backup. Some features previously available in the Microsoft Mobile Information Server 2001/2002 products have been added to the core Exchange Server product, like Outlook Mobile Access and server-side Exchange ActiveSync, while the Mobile Information Server product itself has been dropped. Also new is the ability to drop inbound e-mail before being fully processed, thus preventing delays in the message routing system. There are also improved message and mailbox management tools, which allow administrators to execute common chores more quickly. Others, such as Instant Messaging and Exchange Conferencing Server have been extracted completely in order to form separate products. Microsoft now appears to be positioning a combination of Microsoft Office, Microsoft Office Live Communications Server, Live Meeting and SharePoint as its collaboration software of choice. Exchange Server is now to be simply e-mail and calendaring.

Exchange Server 2003 added several basic filtering methods to Exchange Server. They are not sophisticated enough to eliminate spam, but they can protect against DoS and mailbox flooding attacks. Exchange Server 2000 supported the ability to block a sender's address, or e-mail domain by adding '*@domain.com', which is still supported in Exchange Server 2003.

New features

Added filtering methods in Exchange Server 2003 are:

  • Connection filtering: Messages are blocked from DNS RBL lists[11] or from manually specified IP addresses/ranges
  • Recipient filtering: Messages blocked when sent to manually specified recipients on the server (for intranet-only addresses) or to any recipients not on the server (stopping spammers from guessing addresses)
  • Sender ID filtering: Sender ID, a form of Sender Policy Framework (SPF)
  • Intelligent Message Filter: Initially a free Microsoft add-on, later, part of service pack 2, that uses heuristic message analysis to block messages or direct them to the "Junk E-Mail" folder in Microsoft Outlook clients.[12]

It is included with both Windows Small Business Server 2003 Standard and Premium editions.

Editions

Standard Edition:

  • Supports up to two storage groups (with one of the storage groups, called the recovery storage group, being reserved for database recovery operations) and a maximum of two databases per storage group.
  • Each database is limited to a maximum size of 16 GB.
  • Beginning with the release of Service Pack 2, a maximum database size of 75 GB, but only supports 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]

Exchange Server 2007

Released to business customers as part of Microsoft's 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 filtering 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.

The first 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 team blog.[17] On April 25, 2006, Microsoft announced that the next version of Exchange Server would be called "Exchange Server 2007".

Exchange Server 2007 is an integrated part of the Innovative Communications Alliance products.[18]

New features

  • Protection: Anti-spam, antivirus, compliance, clustering with data replication, improved security and encryption
  • Improved Information Worker Access: Improved calendaring, unified messaging, improved mobility, improved web access
  • Improved IT Experience: 64-bit performance and scalability, command-line shell and simplified GUI, improved deployment, role separation, simplified routing
  • Exchange Management Shell: a new command-line 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]
  • "Unified 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).
  • Configure 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 offline address book.

Editions

Standard edition
Can have 5 databases in up to 5 storage groups. Supports LCR (Local Continuous Replication) and SCR (Standby Continuous Replication).
Enterprise edition
This is extended to 50 databases in up to 50 storage groups. Supports LCR (Local Continuous Replication), SCR (Standby Continuous Replication), SCC (Single Copy Clustering), and CCR (Clustered Continuous Replication).

Exchange Server 2010

Exchange Server 2010 logo

Exchange Server 2010 was released to manufacturing on May 2009, and reached general availability on November 9, 2009.[21]

New features

  • DAG (Database Availability Groups): SCC, CCR, LCR and site resiliency functionality SCR have been replaced by DAG. It provides database-level high availability (as opposed to server level) and supports a number of copies of each database (number based on Exchange Edition) and flexible configuration (databases copies may be added / removed at will without requiring major server reconfiguration).
  • 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, Microsoft IT was able to reduce hardware costs by 75% during the migration from Exchange Server 2007 to Exchange Server 2010.
  • 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 different database than the primary mailbox, which may reside on a different 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 configured 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 modified items.
  • Administration delegation: Can now be performed at a granular level due to Exchange Server 2010's implementation of Role Based Access Control (RBAC). Users and administrators can be given extremely fine grained abilities for functions provided both within the Exchange Management Console or Exchange Management Shell and in Outlook Web App. For example, a compliance officer 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 Office message for other employees within the company, or a branch administrator in a remote office may be granted the permission to perform specific Exchange Management Shell commands that pertain only to the Exchange server in their branch office.
  • 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 configured to allow users to join at will or only with a group moderator's permission, and individual messages sent to distribution groups can now be approved or denied by a moderator.
  • "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 different Hub Transport or Edge Transport server for processing...

Editions

Several high-availability options have been consolidated into just one option for Exchange Server 2010 (Mailbox Resiliency), which is now offered in both the Standard and Enterprise editions. The capabilities of Local Continuous Replication, Standby Continuous Replication, and Cluster Continuous Replication are now unified into the Exchange 2010 Mailbox Resiliency capability. These capabilities enable a simplified 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 InfoWorld's 2011 Technology of the Year Award for Best Mail Server.

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]

New features

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

  • Offline 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.
  • Outlook Web App: Offers three different UI layouts optimized for desktop, tablet, and mobile phone browsers.
  • Ability to customize: Outlook and OWA by integrating apps from the Office marketplace. (Yes, this is a reference to the Agaves add-ins that Microsoft and partners will be making available via the new Office Store.) The new "Napa" tools and/or HTML5 are Microsoft's 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 configure and manage settings from inside EAC. (Note: this feature can be turned off, 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.

Exchange Server 2016

On October 1, 2015, Microsoft announced the general availability (GA) of Exchange Server 2016.[28]

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 Office 365 hybrid scenarios).
  • Outlook on the web (formerly Outlook Web App): UI changes
  • Office 365 hybrid: The Hybrid Configuration Wizard (HCW) that was included with Exchange 2013 is moving to become a cloud-based application. When one chooses to configure 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: 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.[29] 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.[30] 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.[31] This void has however been filled 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 configurations that address the shortcomings of the previous "shared data model".[33]

Exchange Server 2007 provides built-in support for asynchronous replication modeled on SQL Server's "Log shipping"[34] 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"[35] 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.[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 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.

Exchange hosting

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[when?] 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.

Exchange Online

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.[38]

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[39] 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 a staggered 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.[citation needed]

History

Exchange Online was first provided as a hosted service in dedicated customer environments in 2005 to select pilot customers.[40] Microsoft launched a multi-tenant version of Exchange Online as part of the Business Productivity Online Standard Suite in November 2008.[41] 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.

Clients

Microsoft Exchange Server uses a proprietary remote procedure call (RPC) protocol called MAPI/RPC,[42] which was designed to be used by Microsoft Outlook. Clients capable of using the proprietary features of Exchange Server include Evolution[43] 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.[44] 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. 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.[45] as well as its advanced device security and compliance features.

Support for push email was added to Exchange Server 2003 with Service Pack 2. Windows Mobile 5.0 requires the "Messaging and Security Feature Pack (MSFP)", later versions of the mobile operating system, such as Windows Phone 7, have the capability built in.[46] Many other devices now support Exchange ActiveSync push email, such as the iPhone and Android Phones.[47] Exchange Server 2007 and Exchange Server 2010 support the use of Exchange ActiveSync Policies. By using Exchange ActiveSync Policies, administrators can secure the devices that connect to the organization or remotely deactivate features on the devices. Administrators or users can also remotely wipe a lost mobile device.

Exchange Server 2013 supports the use of Mobile Exchange ActiveSync Policies.[48]

See also

References

  1. ^ "Exchange Server build numbers and release dates". Microsoft. Retrieved February 19, 2018.
  2. ^ Lextrait, Vincent (January 2010). "The Programming Languages Beacon, v10.0". Retrieved March 14, 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. ^ "The box says Microsoft Mail for PC Networks v2.1, but under the hood users will find Consumer Software Inc's, Network Courier...", August 26, 1991, Computerworld
  5. ^ Paul Korzeniowski (1992). "E-mail becoming foundation for networked applications". Software Magazine. Retrieved October 28, 2012.
  6. ^ a b "Microsoft's Migration to Microsoft Exchange Server". TechNet. Microsoft. Archived from the original on May 7, 2005.
  7. ^ Dr. Nikolai Bezroukov. "XENIX – Microsoft Short-lived Love Affair with Unix". Softpanorama. Retrieved October 28, 2012.
  8. ^ Redmond, Tony (March 31, 1997). "Microsoft Exchange Server 5.0 Smoothes the Rough Edges". Windows IT Pro. Penton.
  9. ^ "Microsoft Support Lifecycle/Exchange Server", Microsoft.com
  10. ^ Vidhya (1992). "Exchange Server backup and Disaster Recovery". Software Magazine. Retrieved October 28, 2012.
  11. ^ Markus Klien (2003). "Implementing and Configuring Blacklist Support in Exchange Server 2003". MSExchange. Retrieved October 28, 2012.
  12. ^ "Exchange Intelligent Message Filter". TechNet. Microsoft. 2003. Archived from the original on July 6, 2007. {{cite web}}: Unknown parameter |deadurl= ignored (|url-status= suggested) (help)
  13. ^ "Registry tweak to set a 75gb store limit on Exchange 2003 Standard SP2". TechNet. 2005. Retrieved October 28, 2012.
  14. ^ "Microsoft Support Lifecycle". TechNet. 2007. Retrieved October 28, 2012.
  15. ^ "Microsoft Warns of Looming Exchange Server 2003 Support Deadline". Redmond Channel Partner. 2014. Retrieved April 8, 2014.
  16. ^ "Discontinued Features and De-Emphasized Functionality in Exchange 2007". TechNet. 2005. Retrieved October 28, 2012.
  17. ^ Terry Myerson (March 1, 2006). "Exchange 12 Beta 1 Community Technology Preview". The Microsoft Exchange Team Blog. Retrieved October 28, 2012.
  18. ^ Elizabeth Montalbano (January 17, 2007). "Microsoft, Nortel unveil ICA's first products". InfoWorld. Retrieved October 28, 2012.
  19. ^ "Cmdlet List". Microsoft. Retrieved January 27, 2016.
  20. ^ Rodney Buike. "Understanding the Exchange Information Store". Retrieved December 19, 2008.
  21. ^ Elizabeth Montalbano (November 9, 2009). "Microsoft releases Exchange 2010, acquires Teamprise". Beyond Binary - CNET News. Retrieved October 28, 2012.
  22. ^ "The New Exchange Reaches RTM!". The Exchange Team Blog. October 11, 2012. Retrieved October 28, 2012.
  23. ^ "Microsoft Exchange Server 2013 Trial". TechNet. Retrieved November 17, 2012.
  24. ^ Rajith Enchiparambil (2013). "Exchange 2013 - Points to note". theucguy.net. Retrieved February 11, 2013.
  25. ^ Mary Jo Foley (July 23, 2012). "Microsoft's Exchange Server 2013: What's new". ZDNet.com. Retrieved October 28, 2012.
  26. ^ Paul Cunningham (2012). "New Features in Exchange Server 2013". exchangeserverpro.com. Retrieved October 28, 2012.
  27. ^ "Changes in Exchange 2013 Preview". eighttwone.com. 2012. Retrieved October 28, 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 October 28, 2012.
  30. ^ "The benefits of Windows 2003 clustering with Exchange 2003". The Exchange Team Blog. June 9, 2004. Retrieved October 28, 2012.
  31. ^ "Exchange Clustering Concepts". TechNet. February 9, 2006. Retrieved October 28, 2012.
  32. ^ "Storage Glossary: Basic Storage Terms". TechNet. Microsoft. March 8, 2005. Archived from the original on July 15, 2007. Retrieved October 28, 2012.
  33. ^ "High availability". TechNet. March 8, 2005. Retrieved July 2, 2007.
  34. ^ "Frequently asked questions—SQL Server 2000—Log shipping". Microsoft. March 8, 2005. Retrieved October 28, 2012.
  35. ^ "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 October 28, 2012.
  36. ^ "Top 75 Microsoft Licensing Terms – A Glossary From A(ntigen) To Z(une)". OMTCO, omt-co Operations Management Technology Consulting GmbH. Retrieved April 24, 2013.
  37. ^ "Hosted Exchange Partner Directory". Microsoft. Retrieved October 28, 2012.
  38. ^ "Microsoft Exchange Online for Enterprises Service Description". Microsoft. Retrieved October 28, 2012.
  39. ^ Puca, Anthony (2013). Microsoft Office 365 Administration Inside Out. Microsoft Press. pp. 459–462. ISBN 978-0735678231.
  40. ^ Ina Fried (March 10, 2005). "Microsoft hops into managed PC business". CNET News. Retrieved October 28, 2012.
  41. ^ "Microsoft hops into managed PC business". Microsoft. November 7, 2008. Retrieved October 28, 2012.
  42. ^ "Exchange Server Protocols". Microsoft. November 7, 2008. Retrieved October 28, 2012.
  43. ^ "Evolution/FAQ - GNOME Live!". Microsoft. Retrieved October 28, 2012.
  44. ^ "What is the Microsoft Exchange client?".
  45. ^ "Microsoft Exchange ActiveSync Licensees". Microsoft. Retrieved October 28, 2012.
  46. ^ "Exchange ActiveSync: Frequently Asked Questions". TechNet. Retrieved October 28, 2012.
  47. ^ "Exchange ActiveSync". Apple. Retrieved October 28, 2012.
  48. ^ "Apple - iPhone in Business". TechNet. Retrieved October 28, 2012.
Retrieved from "https://en.wikipedia.org/w/index.php?title=Microsoft_Exchange_Server&oldid=714200950"