Jump to content

History of Microsoft Exchange Server: Difference between revisions

Add links
From Wikipedia, the free encyclopedia
Browse history interactively
← Previous edit
Content deleted Content added
VisualWikitext
AnomieBOT (talk | contribs)
Bots
6,524,652 edits
m Dating maintenance tags: {{Cn}}
Microsoft have added support for Windows Server 2022 after CU12 of Exchange 2019 (Look it up it's on Microsoft website if you don't believe me).
 
(15 intermediate revisions by 13 users not shown)
Line 1: Line 1:
{{Lead too short|date=August 2023}}
The '''history of Microsoft Exchange Server''' begins with the first [[Microsoft Exchange Server]] product - Exchange Server 4.0 in April 1996 - and extends to the current day.
{{Cleanup rewrite|date=January 2024}}

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",<ref>[https://books.google.com/books?id=qPEu5Wzi018C&dq=%22network+Courier%22+microsoft+%2C%22Consumer+Software+Inc%22&pg=PA38 "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''</ref> based on ''Network Courier'', which Microsoft had acquired.<ref name=courier/> When the original version of Exchange Server was sold to the public, it was positioned as an upgrade to [[Microsoft Mail]] 3.5.
The first release of [[Microsoft Exchange Server]] was version 4.0 in April 1996, when it was sold as an upgrade to [[Microsoft Mail]] 3.5. Before that, [[Microsoft Mail]] v2.0 (written by [[Microsoft]]) was replaced in 1991 by "Microsoft Mail for PC Networks v2.1",<ref>{{cite web|url=https://books.google.com/books?id=qPEu5Wzi018C&dq=%22network+Courier%22+microsoft+%2C%22Consumer+Software+Inc%22&pg=PA38|title=Microsoft Mail: Solid, less graphical|quote=The box says Microsoft Mail for PC Networks v2.1, but under the hood users will find Consumer Software Inc's, Network Courier…|date=August 26, 1991|work=[[Computerworld]]}}</ref> based on ''Network Courier'' from its acquisition of [[Consumers Software]].<ref name="courier"/> Exchange Server was an entirely new {{nowrap|[[X.400]]-}}based [[client–server]] mail system with a single database store that also supported {{nowrap|[[X.500]]}} directory services. During its development, Microsoft migrated their own internal email from a [[Xenix]]-based system to Exchange Server from April 1993,<ref name="xenix1"/> with all 32,000 Microsoft mailboxes on Exchange by late 1996.<ref name="xenix1"/><ref name="xenix2"/> The directory used by Exchange Server eventually became Microsoft's [[Active Directory]] service, an [[Lightweight Directory Access Protocol|LDAP]]-compliant directory service. Active Directory was integrated into [[Windows 2000]] as the foundation of [[Windows domain]]s.

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,<ref name=xenix1/> with all 32,000 Microsoft mailboxes on Exchange by late 1996.<ref name=xenix1/><ref name=xenix2/>

The directory used by Exchange Server eventually became Microsoft's [[Active Directory]] service, an [[Lightweight Directory Access Protocol|LDAP]]-compliant directory service. Active Directory was integrated into [[Windows 2000]] as the foundation of [[Windows Server domain]]s.


==Versions==
==Versions==
Line 22: Line 18:
|Rowspan=5 {{N/A}}
|Rowspan=5 {{N/A}}
|2 April 1996
|2 April 1996
|{{N/A}} <ref>{{Cite web|url=https://support.microsoft.com/en-us/lifecycle/search/730|title = Search Product and Services Lifecycle Information - Microsoft Lifecycle}}</ref>
|{{N/A}} <ref>{{Cite web|url=https://support.microsoft.com/en-us/lifecycle/search/730|title =Search Product and Services Lifecycle Information - Microsoft Lifecycle}}</ref>
|{{N/A}}
|{{N/A}}
|-
|-
Line 85: Line 81:


===Exchange Server 4.0===
===Exchange Server 4.0===
The first release of Exchange outside of Microsoft was Exchange Server 4.0 in April 1996,<ref name="initial-release">{{cite web|date=2 April 1996|title=Microsoft Exchange Server Available|url=https://news.microsoft.com/1996/04/02/microsoft-exchange-server-available|access-date=5 February 2023|website=[[Microsoft]]}}</ref> with five [[service packs]] being released over the next two years.<ref>[https://support.microsoft.com/en-us/lifecycle/search?sort=PN&alpha=Exchange%20Server&Filter=FilterNO "Microsoft Support Lifecycle/Exchange Server"], Microsoft.com</ref>
The first release of Exchange outside of Microsoft was Exchange Server 4.0 in April 1996,<ref name="initial-release">{{cite web|date=2 April 1996|title=Microsoft Exchange Server Available|url=https://news.microsoft.com/1996/04/02/microsoft-exchange-server-available|access-date=5 February 2023|website=[[Microsoft]]}}</ref> with five [[service pack]]s being released over the next two years.<ref>{{cite web|url=https://support.microsoft.com/en-us/lifecycle/search?sort=PN&alpha=Exchange%20Server&Filter=FilterNO|title=Microsoft Support Lifecycle/Exchange Server|website=Microsoft.com}}</ref>


===Exchange Server 5.0===
===Exchange Server 5.0===
Initial release: May 23, 1997.
Initial release: May 23, 1997.


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 App|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.
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 [[webmail]] interface called Exchange Web Access, which was rebranded as [[Outlook on the web|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 [[Lightweight Directory Access Protocol|LDAP]] v3 clients and the Deleted Item Recovery feature.
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 [[Lightweight Directory Access Protocol|LDAP]] v3 clients and the Deleted Item Recovery feature.
Line 100: Line 96:


It was sold in two editions: Standard and Enterprise. They differ in database store size, mail transport connectors, and clustering capabilities.
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&nbsp;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]].
;Standard Edition: Had the same 16&nbsp;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]], [[HCL Notes|Lotus Notes]] and [[Novell]] [[GroupWise]].
;Enterprise Edition: Had an increased limit of 16&nbsp;TB (although Microsoft's best practices documentation recommends that the message store not exceed 100&nbsp;GB). Adds an [[X.400]] connector, and interoperability software with [[SNADS]] and [[PROFS]]. Introduced two node [[Microsoft Cluster Server|clustering]] capability.
;Enterprise Edition: Had an increased limit of 16&nbsp;TB (although Microsoft's best practices documentation recommends that the message store not exceed 100&nbsp;GB). Adds an {{nowrap|[[X.400]]}} connector, and interoperability software with [[SNADS]] and [[PROFS]]. Introduced two node [[Microsoft Cluster Server|clustering]] capability.


===Exchange 2000 Server===
===Exchange 2000 Server===
Line 111: Line 107:
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.
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,<ref name=recovery/> 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]], [[Microsoft Live Meeting|Live Meeting]], and [[SharePoint]] as its collaboration software of choice. Exchange Server is now to be simply e-mail and calendaring.
One of the new features in Exchange Server 2003 is enhanced disaster recovery,<ref name=recovery/> 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]], [[Microsoft Office Live Meeting|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.
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.
Line 135: Line 131:


===Exchange Server 2007===
===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.<ref name=2k7discontinued/>
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, [[voicemail]] 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, {{nowrap|X.400}}, and some API interfaces, amongst other features.<ref name=2k7discontinued/>


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.
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.<ref name=2k7beta1/> On April 25, 2006, Microsoft announced that the next version of Exchange Server would be called "Exchange Server 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.<ref name=2k7beta1/> On April 25, 2006, Microsoft announced that the next version of Exchange Server would be called "Exchange Server 2007".
Line 147: Line 143:
*'''Improved Information Worker Access''': Improved calendaring, unified messaging, improved mobility, improved web access
*'''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
*'''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 interface|command-line]] [[shell (computing)|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.<ref>{{cite web|url=https://technet.microsoft.com/en-us/library/bb123703.aspx|title=Cmdlet List|publisher=Microsoft|accessdate=January 27, 2016}}</ref>
*'''Exchange Management Shell''': a new [[command-line interface|command-line]] [[shell (computing)|shell]] and [[scripting language]] for system administration (based on [[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.<ref>{{cite web|url=https://technet.microsoft.com/en-us/library/bb123703.aspx|title=Cmdlet List|publisher=Microsoft|accessdate=January 27, 2016}}</ref>
*'''"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")
*'''"Unified Messaging"''': Lets users receive [[voicemail]], 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<ref>{{cite web|url=http://www.msexchange.org/articles/Understanding-Exchange-Information-Store.html|title=Understanding the Exchange Information Store|accessdate=2008-12-19|author=Rodney Buike}}</ref>
*'''Increased database maximum size limit''': Database size is now limited to 16TB per database<ref>{{cite web|url=http://www.msexchange.org/articles/Understanding-Exchange-Information-Store.html|title=Understanding the Exchange Information Store|accessdate=2008-12-19|author=Rodney Buike}}</ref>
*'''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).
*'''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.
*'''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.
* '''Room and equipment mailboxes: Finally resources can be properly created and managed, and users in Outlook can easily book them.
* '''Room and equipment mailboxes''': Finally resources can be properly created and managed, and users in Outlook can easily book them.


====Editions====
====Editions====
Line 163: Line 159:


====New features====
====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).
*'''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 or removed 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.
*'''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.
*'''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 (computing)|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.
*'''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.
*'''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.
Line 171: Line 167:
*'''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.
*'''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.
*'''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).
*'''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 (web browser)|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.
*'''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.
*'''"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.
Line 180: Line 176:
Storage group is discontinued in Exchange 2010 and onward.
Storage group is discontinued in Exchange 2010 and onward.


In January 2011, Microsoft Exchange Server 2010 won InfoWorld's 2011 Technology of the Year Award for Best Mail Server.{{cn|date=August 2023}}
In January 2011, Microsoft Exchange Server 2010 won InfoWorld's 2011 Technology of the Year Award for Best Mail Server.{{citation needed|date=August 2023}}


===Exchange Server 2013===
===Exchange Server 2013===
Line 186: Line 182:
Microsoft reached the RTM milestone for Exchange Server 2013 (v15.0) on October 11, 2012.<ref name=2k13rtm/> A [[trial version]] of this product is available from Microsoft website.<ref name=2k3rtmtrial/>
Microsoft reached the RTM milestone for Exchange Server 2013 (v15.0) on October 11, 2012.<ref name=2k13rtm/> A [[trial version]] of this product is available from Microsoft website.<ref name=2k3rtmtrial/>


Exchange 2013 represented a major change to the servicing model: instead of large Service Packs and small Update Rollup packages, a new Cumulative Update methodology is used with CU packages being released on a quarterly schedule and any security updates for that CU released on [[Patch Tuesday]] (or out of band as necessary). Microsoft support only the current and "n-1" Cumulative Update release of Exchange Server 2013 and later during mainstream support, and only the current CU once the transition to extended support completes. Despite this, Cumulative Update 4 was rebranded as Service Pack 1 due to significant additional functionality.<ref>{{cite web|title=Released: Exchange Server 2013 Service Pack 1|url=https://techcommunity.microsoft.com/t5/exchange-team-blog/released-exchange-server-2013-service-pack-1/ba-p/587548|website=techcommunity.microsoft.com|date=25 February 2014|publisher=Microsoft|access-date=5 October 2022}}</ref> The 23rd and final Cumulative Update for Exchange 2013 was released on June 18, 2019.<ref>{{cite web|title=Exchange Server build numbers and release dates|url=https://learn.microsoft.com/en-us/exchange/new-features/build-numbers-and-release-dates?view=exchserver-2019#exchange-server-2013|website=learn.microsoft.com|publisher=Microsoft|access-date=5 October 2022}}</ref>
Exchange 2013 represented a major change to the servicing model: instead of large Service Packs and small Update Rollup packages, a new Cumulative Update methodology is used with CU packages being released on a quarterly schedule and any security updates for that CU released on [[Patch Tuesday]] (or out-of-band as necessary). Microsoft supported only the "n-1" Cumulative Update release of Exchange Server 2013 and later during mainstream support, and only the final CU once the transition to extended support completed. Despite this, Cumulative Update 4 was rebranded as Service Pack 1 due to significant additional functionality.<ref>{{cite web|title=Released: Exchange Server 2013 Service Pack 1|url=https://techcommunity.microsoft.com/t5/exchange-team-blog/released-exchange-server-2013-service-pack-1/ba-p/587548|website=techcommunity.microsoft.com|date=25 February 2014|publisher=Microsoft|access-date=5 October 2022}}</ref> The 23rd and final Cumulative Update for Exchange 2013 was released on June 18, 2019.<ref>{{cite web|title=Exchange Server build numbers and release dates|url=https://learn.microsoft.com/en-us/exchange/new-features/build-numbers-and-release-dates?view=exchserver-2019#exchange-server-2013|website=learn.microsoft.com|publisher=Microsoft|access-date=5 October 2022}}</ref>


====New features====
====New features====
Line 195: Line 191:
*'''Site Mailboxes''': Brings Exchange emails and SharePoint documents together.
*'''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.
*'''[[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.
*'''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 would 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).
*'''Exchange Administrative Center (EAC)''': Replacement of the Exchange Management Console by a Web-based Exchange Administrative Center (EAC).
*'''Support for up to 8 TB disks''': And multiple databases per disk via Data Availability Group (DAG) management.
*'''Support for up to 8 TB disks''': And multiple databases per disk via Data Availability Group (DAG) management.
Line 203: Line 199:
*'''Combine Roles''': A reduction in the number of available roles to two: a Client Access Server and a Mailbox Server role.
*'''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.
*'''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#.
*'''Inclusion of a "Managed Store"''': The name of the rewritten information store processes, which are now written in [[C# (programming language)|C#]].
*'''Replication''': Public folders are now stored in mailbox databases and can take advantage of Database Availability Groups for replication and high availability.
*'''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.
*'''Data loss prevention''': Capabilities that can be integrated into Transport Rules.
*'''MAPI over HTTPS''': New protocol designed from the ground up to replace Outlook Anywhere. This functionality requires that all Exchange 2013 Servers are running at least Service Pack 1; it is disabled by default in organizations where Exchange Server 2013 has been installed and must be manually enabled once the prerequisites are met.
*'''[[MAPI]] over HTTPS''': New protocol designed from the ground up to replace Outlook Anywhere. This functionality requires that all Exchange 2013 Servers are running at least Service Pack 1; it is disabled by default in organizations where Exchange Server 2013 has been installed and must be manually enabled once the prerequisites are met.


====Removed features====
====Removed features====
*'''MAPI over RPC''': All client connectivity to Exchange 2013 and later uses HTTPS, requiring special consideration for coexistence with Exchange 2010/2007.
*'''MAPI over RPC''': All client connectivity to Exchange 2013 and later uses [[HTTPS]], requiring special consideration for coexistence with Exchange 2010/2007.


===Exchange Server 2016===
===Exchange Server 2016===
Line 217: Line 213:
*'''Combine Roles''': A reduction in the number of available roles to two: Mailbox Server and Edge Transport
*'''Combine Roles''': A reduction in the number of available roles to two: Mailbox Server and Edge Transport
*'''[[Outlook on the web]] (formerly Outlook Web App)''': UI changes
*'''[[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.
*'''Office 365 hybrid''': The Hybrid Configuration Wizard (HCW) that was included with Exchange 2013 is moving to become a cloud-based application. When users choose to configure a hybrid deployment in Exchange 2016, they'll be prompted to download and install the wizard as a small app.
*'''Messaging policy and compliance''': New DLP and Archiving/Retention/eDiscovery features.
*'''Messaging policy and compliance''': New DLP and Archiving/Retention/eDiscovery features.


Line 223: Line 219:


===Exchange Server 2019===
===Exchange Server 2019===
Exchange Server 2019 (v15.2) was released in October 2018.<ref>{{cite web|url=https://www.frankysweb.de/microsoft-kuendigt-exchange-2019-an/|title=Microsoft kündigt Exchange 2019 an|date=26 September 2017 }}</ref> Unlike other Office Server 2019 products such as SharePoint and Skype for Business, Exchange Server 2019 can only be deployed on Windows Server 2019. One of the key features of the new release is that Exchange Server can be deployed onto Windows Server Core for the first time, additionally Microsoft has retired the Unified Messaging feature of Exchange, meaning that Skype for Business on-premises customers will have to use alternative solutions for voicemail, such as Azure cloud voicemail. Unified Messaging continues to exist in Exchange Online requiring an Exchange Plan 2 license.
Exchange Server 2019 (v15.2) was released in October 2018.<ref>{{cite web|url=https://www.frankysweb.de/microsoft-kuendigt-exchange-2019-an/|title=Microsoft kündigt Exchange 2019 an|date=26 September 2017}}</ref> Unlike other Office Server 2019 products such as SharePoint and Skype for Business, Exchange Server 2019 can only be deployed on [[Windows Server 2019]]. One of the key features of the new release is that Exchange Server can be deployed onto [[Windows Server Core]] for the first time, additionally Microsoft has retired the [[unified messaging]] feature of Exchange, meaning that Skype for Business on-premises customers will have to use alternative solutions for [[voicemail]], such as [[Microsoft Azure|Azure]] cloud voicemail. Unified Messaging continues to exist in Exchange Online requiring an Exchange Plan 2 license.


A pre-release was released on 25th July.<ref>{{cite web|url=https://tweakers.net/downloads/45131/microsoft-exchange-server-2019-public-preview.html|title=Microsoft Exchange Server 2019 Public Preview }}</ref>
A pre-release was released on 25 July.<ref>{{cite web|url=https://tweakers.net/downloads/45131/microsoft-exchange-server-2019-public-preview.html|title=Microsoft Exchange Server 2019 Public Preview}}</ref>


====New Features====
====New Features====
*'''Security:''' support for installing Exchange Server 2019 onto Windows Server Core
*'''Security:''' support for installing Exchange Server 2019 onto Windows Server Core
*'''Performance:''' supports running Exchange Server with up to 48 processor cores and 256 GB of RAM
*'''Performance:''' supports running Exchange Server with up to 48 processor cores and 256 GB of RAM
*'''Security:''' support for installing Exchange Server 2019 onto Windows Server 2022 after Exchange CU12


====Removed features====
====Removed features====
Line 239: Line 236:
{{Reflist|30em|refs=
{{Reflist|30em|refs=
<ref name=xenix1>{{cite web|title=Microsoft's Migration to Microsoft Exchange Server|url=https://www.microsoft.com/technet/archive/itsolutions/intranet/build/exchgdep.mspx|work=[[Microsoft TechNet|TechNet]]|publisher=[[Microsoft]]|archiveurl=https://web.archive.org/web/20050507010335/http://www.microsoft.com/technet/archive/itsolutions/intranet/build/exchgdep.mspx|archivedate=May 7, 2005}}</ref>
<ref name=xenix1>{{cite web|title=Microsoft's Migration to Microsoft Exchange Server|url=https://www.microsoft.com/technet/archive/itsolutions/intranet/build/exchgdep.mspx|work=[[Microsoft TechNet|TechNet]]|publisher=[[Microsoft]]|archiveurl=https://web.archive.org/web/20050507010335/http://www.microsoft.com/technet/archive/itsolutions/intranet/build/exchgdep.mspx|archivedate=May 7, 2005}}</ref>
<ref name=xenix2>{{cite web|title=XENIX – Microsoft Short-lived Love Affair with Unix|url=http://www.softpanorama.org/People/Torvalds/Finland_period/xenix_microsoft_shortlived_love_affair_with_unix.shtml|publisher=Softpanorama|author=Dr. Nikolai Bezroukov|accessdate=28 October 2012}}</ref>
<ref name=xenix2>{{cite web|title=XENIX – Microsoft Short-lived Love Affair with Unix|url=http://www.softpanorama.org/People/Torvalds/Finland_period/xenix_microsoft_shortlived_love_affair_with_unix.shtml|publisher=Softpanorama|author=Nikolai Bezroukov|accessdate=28 October 2012}}</ref>
<!--
<!--
<ref name=fax>{{cite web|title=How to Set Up a Fax Server or Fax Client with Microsoft Fax|url=http://support.microsoft.com/kb/141292/en-us|publisher=Microsoft|accessdate=28 October 2012}}</ref>
<ref name=fax>{{cite web|title=How to Set Up a Fax Server or Fax Client with Microsoft Fax|url=http://support.microsoft.com/kb/141292/en-us|publisher=Microsoft|accessdate=28 October 2012}}</ref>
Line 245: Line 242:
<ref name=courier>{{cite web|title=E-mail becoming foundation for networked applications|url=http://www.highbeam.com/doc/1G1-11725946.html|archive-url=https://web.archive.org/web/20130516142557/http://www.highbeam.com/doc/1G1-11725946.html|url-status=dead|archive-date=16 May 2013|publisher=Software Magazine|author=Paul Korzeniowski|accessdate=28 October 2012|year=1992}}</ref>
<ref name=courier>{{cite web|title=E-mail becoming foundation for networked applications|url=http://www.highbeam.com/doc/1G1-11725946.html|archive-url=https://web.archive.org/web/20130516142557/http://www.highbeam.com/doc/1G1-11725946.html|url-status=dead|archive-date=16 May 2013|publisher=Software Magazine|author=Paul Korzeniowski|accessdate=28 October 2012|year=1992}}</ref>
<ref name=recovery>{{cite web|title=Exchange Server backup and Disaster Recovery|url=http://blog.vembu.com/ms-exchange-2003-2007-2010-backup-restore-using-storegrid-2/|publisher=Software Magazine|author=Vidhya|accessdate=28 October 2012|year=1992|archive-date=27 October 2012|archive-url=https://web.archive.org/web/20121027112613/http://blog.vembu.com/ms-exchange-2003-2007-2010-backup-restore-using-storegrid-2/|url-status=dead}}</ref>
<ref name=recovery>{{cite web|title=Exchange Server backup and Disaster Recovery|url=http://blog.vembu.com/ms-exchange-2003-2007-2010-backup-restore-using-storegrid-2/|publisher=Software Magazine|author=Vidhya|accessdate=28 October 2012|year=1992|archive-date=27 October 2012|archive-url=https://web.archive.org/web/20121027112613/http://blog.vembu.com/ms-exchange-2003-2007-2010-backup-restore-using-storegrid-2/|url-status=dead}}</ref>
<ref name=dnsrbllists>{{cite web|title=Implementing and Configuring Blacklist Support in Exchange Server 2003|url=http://www.msexchange.org/tutorials/Blacklist_Support_Exchange_2003.html|publisher=MSExchange|author=Markus Klien|accessdate=28 October 2012|year=2003}}</ref>
<ref name=dnsrbllists>{{cite web|title=Implementing and Configuring Blacklist Support in Exchange Server 2003|url=http://www.msexchange.org/tutorials/Blacklist_Support_Exchange_2003.html|publisher=MSExchange|author=Markus Klien|accessdate=28 October 2012|year=2003|archive-date=27 December 2012|archive-url=https://web.archive.org/web/20121227004210/http://www.msexchange.org/tutorials/blacklist_support_exchange_2003.html|url-status=dead}}</ref>
<ref name=messagefilter>{{cite web|title=Exchange Intelligent Message Filter|url=https://technet.microsoft.com/en-us/library/aa996624.aspx|work=[[Microsoft TechNet|TechNet]]|publisher=Microsoft|year=2003|url-status=live|archiveurl=https://web.archive.org/web/20070706200643/http://technet.microsoft.com/en-us/exchange/bb288484.aspx|archivedate=July 6, 2007}}</ref>
<ref name=messagefilter>{{cite web|title=Exchange Intelligent Message Filter|url=https://technet.microsoft.com/en-us/library/aa996624.aspx|work=[[Microsoft TechNet|TechNet]]|publisher=Microsoft|year=2003|url-status=live|archiveurl=https://web.archive.org/web/20070706200643/http://technet.microsoft.com/en-us/exchange/bb288484.aspx|archivedate=July 6, 2007}}</ref>
<ref name=2k3support>{{cite web|title=Microsoft Support Lifecycle|url=http://support.microsoft.com/lifecycle/default.aspx?LN=en-us&p1=1773&x=10&y=14|publisher=TechNet|accessdate=28 October 2012|year=2007}}</ref>
<ref name=2k3support>{{cite web|title=Microsoft Support Lifecycle|url=http://support.microsoft.com/lifecycle/default.aspx?LN=en-us&p1=1773&x=10&y=14|publisher=TechNet|accessdate=28 October 2012|year=2007}}</ref>
Line 256: Line 253:
<ref name=2k13rtm>{{cite web|title=The New Exchange Reaches RTM!|url=http://blogs.technet.com/b/exchange/archive/2012/10/11/the-new-exchange-reaches-rtm.aspx|publisher=The Exchange Team Blog|accessdate=28 October 2012|date=11 October 2012}}</ref>
<ref name=2k13rtm>{{cite web|title=The New Exchange Reaches RTM!|url=http://blogs.technet.com/b/exchange/archive/2012/10/11/the-new-exchange-reaches-rtm.aspx|publisher=The Exchange Team Blog|accessdate=28 October 2012|date=11 October 2012}}</ref>
<ref name=2k13new0>{{cite web|title=Exchange 2013 - Points to note|url=https://theucguy.net/exchange-2013-points-to-note/|publisher=theucguy.net|author=Rajith Enchiparambil|accessdate=11 February 2013|year=2013|archive-date=14 October 2014|archive-url=https://web.archive.org/web/20141014235742/http://theucguy.net/exchange-2013-points-to-note/|url-status=dead}}</ref>
<ref name=2k13new0>{{cite web|title=Exchange 2013 - Points to note|url=https://theucguy.net/exchange-2013-points-to-note/|publisher=theucguy.net|author=Rajith Enchiparambil|accessdate=11 February 2013|year=2013|archive-date=14 October 2014|archive-url=https://web.archive.org/web/20141014235742/http://theucguy.net/exchange-2013-points-to-note/|url-status=dead}}</ref>
<ref name=2k13new1>{{cite web|title=Microsoft's Exchange Server 2013: What's new|url=https://www.zdnet.com/microsofts-exchange-server-2013-whats-new-7000001407/|publisher=ZDNet.com|author=Mary Jo Foley|accessdate=28 October 2012|date=23 July 2012}}</ref>
<ref name=2k13new1>{{cite web|title=Microsoft's Exchange Server 2013: What's new|url=https://www.zdnet.com/article/microsofts-exchange-server-2013-whats-new/|publisher=ZDNet.com|author=Mary Jo Foley|access-date=28 October 2012|date=23 July 2012}}</ref>
<ref name=2k13new2>{{cite web|title=New Features in Exchange Server 2013|url=http://exchangeserverpro.com/exchange-server-2013|publisher=exchangeserverpro.com|author=Paul Cunningham|accessdate=28 October 2012|year=2012|archive-date=17 October 2012|archive-url=https://web.archive.org/web/20121017091405/http://exchangeserverpro.com/exchange-server-2013|url-status=dead}}</ref>
<ref name=2k13new2>{{cite web|title=New Features in Exchange Server 2013|url=http://exchangeserverpro.com/exchange-server-2013|publisher=exchangeserverpro.com|author=Paul Cunningham|accessdate=28 October 2012|year=2012|archive-date=17 October 2012|archive-url=https://web.archive.org/web/20121017091405/http://exchangeserverpro.com/exchange-server-2013|url-status=dead}}</ref>
<ref name=2k13new3>{{cite web|title=Changes in Exchange 2013 Preview|url=http://eightwone.com/2012/07/18/changes-exchange-2013-preview-whats-new/|publisher=eighttwone.com|accessdate=28 October 2012|year=2012}}</ref>
<ref name=2k13new3>{{cite web|title=Changes in Exchange 2013 Preview|url=http://eightwone.com/2012/07/18/changes-exchange-2013-preview-whats-new/|publisher=eighttwone.com|accessdate=28 October 2012|year=2012}}</ref>
<!-- Unused citations
<!--Unused citations
<ref name=evolution>{{cite web|title=Windows - Evolution|url=http://www.go-evolution.org/Windows#Evolution_Installers_for_Windows|publisher=Microsoft|accessdate=28 October 2012}}</ref>
<ref name=evolution>{{cite web|title=Windows - Evolution|url=http://www.go-evolution.org/Windows#Evolution_Installers_for_Windows|publisher=Microsoft|accessdate=28 October 2012}}</ref>
-->
-->

Latest revision as of 01:32, 12 September 2024

The first release of Microsoft Exchange Server was version 4.0 in April 1996, when it was sold as an upgrade to Microsoft Mail 3.5. Before that, Microsoft Mail v2.0 (written by Microsoft) was replaced in 1991 by "Microsoft Mail for PC Networks v2.1",[1] based on Network Courier from its acquisition of Consumers Software.[2] 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,[3] with all 32,000 Microsoft mailboxes on Exchange by late 1996.[3][4] 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 domains.

Versions

[edit]

Version history

[edit]
Release name Build version Internal version Release Date Mainstream End Date Extended End Date
Old version, no longer maintained: 4.0 4.0.x — 2 April 1996 — [5] —
Old version, no longer maintained: 5.0 5.0.x 23 May 1997 31 December 2003 10 January 2006
Old version, no longer maintained: 5.5 5.5.x 20 March 1998
Old version, no longer maintained: 2000 6.0.x 29 November 2000 31 December 2005 11 January 2011
Old version, no longer maintained: 2003 6.5.x 28 September 2003 14 April 2009 8 April 2014
Old version, no longer maintained: 2007 8.[0123].x 8.0[0123].x 8 March 2007 10 April 2012 11 April 2017
Old version, no longer maintained: 2010 14.[0123].x 14.0[0123].x 9 November 2009 13 January 2015 13 October 2020
Old version, no longer maintained: 2013 15.0.x 15.00.x 9 January 2013 10 April 2018 11 April 2023
Old version, yet still maintained: 2016 15.1.x 15.01.x 1 October 2015 13 October 2020 14 October 2025
Current stable version: 2019 15.2.x 15.02.x 22 October 2018 9 January 2024
Legend:   Old version   Older version, still maintained   Latest version

Exchange Server 4.0

[edit]

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

Exchange Server 5.0

[edit]

Initial release: May 23, 1997.

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

[edit]

Initial release: Nov. 5, 1997, released to manufacturing.

The last version of Exchange Server to have a 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 2000 Server

[edit]

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

[edit]

Codenamed "Titanium", this version can be run on Windows 2000 Server (with Service Pack 4) 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,[8] 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

[edit]

Added filtering methods in Exchange Server 2003 are:

  • Connection filtering: Messages are blocked from DNS RBL lists[9] 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.[10]

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

Editions

[edit]

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

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.[12] Extended support ended on April 8, 2014.[13]

Exchange Server 2007

[edit]

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, voicemail 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.[14]

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.[15] 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.[16]

New features

[edit]
  • 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 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.[17]
  • "Unified Messaging": Lets users receive voicemail, 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[18]
  • 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.
  • Room and equipment mailboxes: Finally resources can be properly created and managed, and users in Outlook can easily book them.

Editions

[edit]
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

[edit]
Exchange Server 2010 logo

Exchange Server 2010 was released to manufacturing in May 2009, and reached general availability on November 9, 2009.[19] The version jumped from v8.x in Exchange 2007 to v14.x in Exchange 2010 to emphasise the synergy of Exchange Server with the Office suite.

New features

[edit]
  • 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 or removed 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

[edit]

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 discontinued in Exchange 2010 and onward.

In January 2011, Microsoft Exchange Server 2010 won InfoWorld's 2011 Technology of the Year Award for Best Mail Server.[citation needed]

Exchange Server 2013

[edit]

Microsoft reached the RTM milestone for Exchange Server 2013 (v15.0) on October 11, 2012.[20] A trial version of this product is available from Microsoft website.[21]

Exchange 2013 represented a major change to the servicing model: instead of large Service Packs and small Update Rollup packages, a new Cumulative Update methodology is used with CU packages being released on a quarterly schedule and any security updates for that CU released on Patch Tuesday (or out-of-band as necessary). Microsoft supported only the "n-1" Cumulative Update release of Exchange Server 2013 and later during mainstream support, and only the final CU once the transition to extended support completed. Despite this, Cumulative Update 4 was rebranded as Service Pack 1 due to significant additional functionality.[22] The 23rd and final Cumulative Update for Exchange 2013 was released on June 18, 2019.[23]

New features

[edit]

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 would 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 8 TB 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 (now Skype for Business) 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.
  • MAPI over HTTPS: New protocol designed from the ground up to replace Outlook Anywhere. This functionality requires that all Exchange 2013 Servers are running at least Service Pack 1; it is disabled by default in organizations where Exchange Server 2013 has been installed and must be manually enabled once the prerequisites are met.

Removed features

[edit]
  • MAPI over RPC: All client connectivity to Exchange 2013 and later uses HTTPS, requiring special consideration for coexistence with Exchange 2010/2007.

Exchange Server 2016

[edit]

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

New features

[edit]
  • Combine Roles: A reduction in the number of available roles to two: Mailbox Server and Edge Transport
  • 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 users choose to configure a hybrid deployment in Exchange 2016, they'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

Exchange Server 2019

[edit]

Exchange Server 2019 (v15.2) was released in October 2018.[29] Unlike other Office Server 2019 products such as SharePoint and Skype for Business, Exchange Server 2019 can only be deployed on Windows Server 2019. One of the key features of the new release is that Exchange Server can be deployed onto Windows Server Core for the first time, additionally Microsoft has retired the unified messaging feature of Exchange, meaning that Skype for Business on-premises customers will have to use alternative solutions for voicemail, such as Azure cloud voicemail. Unified Messaging continues to exist in Exchange Online requiring an Exchange Plan 2 license.

A pre-release was released on 25 July.[30]

New Features

[edit]
  • Security: support for installing Exchange Server 2019 onto Windows Server Core
  • Performance: supports running Exchange Server with up to 48 processor cores and 256 GB of RAM
  • Security: support for installing Exchange Server 2019 onto Windows Server 2022 after Exchange CU12

Removed features

[edit]
  • Unified Messaging

For more detail on new features, see the following Microsoft blog article: Exchange Server 2019 Public Preview

References

[edit]
  1. ^ "Microsoft Mail: Solid, less graphical". Computerworld. August 26, 1991. The box says Microsoft Mail for PC Networks v2.1, but under the hood users will find Consumer Software Inc's, Network Courier…
  2. ^ Paul Korzeniowski (1992). "E-mail becoming foundation for networked applications". Software Magazine. Archived from the original on 16 May 2013. Retrieved 28 October 2012.
  3. ^ a b "Microsoft's Migration to Microsoft Exchange Server". TechNet. Microsoft. Archived from the original on May 7, 2005.
  4. ^ Nikolai Bezroukov. "XENIX – Microsoft Short-lived Love Affair with Unix". Softpanorama. Retrieved 28 October 2012.
  5. ^ "Search Product and Services Lifecycle Information - Microsoft Lifecycle".
  6. ^ "Microsoft Exchange Server Available". Microsoft. 2 April 1996. Retrieved 5 February 2023.
  7. ^ "Microsoft Support Lifecycle/Exchange Server". Microsoft.com.
  8. ^ Vidhya (1992). "Exchange Server backup and Disaster Recovery". Software Magazine. Archived from the original on 27 October 2012. Retrieved 28 October 2012.
  9. ^ Markus Klien (2003). "Implementing and Configuring Blacklist Support in Exchange Server 2003". MSExchange. Archived from the original on 27 December 2012. Retrieved 28 October 2012.
  10. ^ "Exchange Intelligent Message Filter". TechNet. Microsoft. 2003. Archived from the original on July 6, 2007.
  11. ^ "Registry tweak to set a 75gb store limit on Exchange 2003 Standard SP2". TechNet. 2005. Retrieved 28 October 2012.
  12. ^ "Microsoft Support Lifecycle". TechNet. 2007. Retrieved 28 October 2012.
  13. ^ "Microsoft Warns of Looming Exchange Server 2003 Support Deadline". Redmond Channel Partner. 2014. Retrieved 8 April 2014.
  14. ^ "Discontinued Features and De-Emphasized Functionality in Exchange 2007". TechNet. 2005. Retrieved 28 October 2012.
  15. ^ Terry Myerson (1 March 2006). "Exchange 12 Beta 1 Community Technology Preview". The Microsoft Exchange Team Blog. Archived from the original on 27 November 2010. Retrieved 28 October 2012.
  16. ^ Elizabeth Montalbano (17 January 2007). "Microsoft, Nortel unveil ICA's first products". InfoWorld. Retrieved 28 October 2012.
  17. ^ "Cmdlet List". Microsoft. Retrieved January 27, 2016.
  18. ^ Rodney Buike. "Understanding the Exchange Information Store". Retrieved 2008-12-19.
  19. ^ Elizabeth Montalbano (9 November 2009). "Microsoft releases Exchange 2010, acquires Teamprise". Beyond Binary - CNET News. Retrieved 28 October 2012.
  20. ^ "The New Exchange Reaches RTM!". The Exchange Team Blog. 11 October 2012. Retrieved 28 October 2012.
  21. ^ "Microsoft Exchange Server 2013 Trial". TechNet. Retrieved 17 November 2012.
  22. ^ "Released: Exchange Server 2013 Service Pack 1". techcommunity.microsoft.com. Microsoft. 25 February 2014. Retrieved 5 October 2022.
  23. ^ "Exchange Server build numbers and release dates". learn.microsoft.com. Microsoft. Retrieved 5 October 2022.
  24. ^ Rajith Enchiparambil (2013). "Exchange 2013 - Points to note". theucguy.net. Archived from the original on 14 October 2014. Retrieved 11 February 2013.
  25. ^ Mary Jo Foley (23 July 2012). "Microsoft's Exchange Server 2013: What's new". ZDNet.com. Retrieved 28 October 2012.
  26. ^ Paul Cunningham (2012). "New Features in Exchange Server 2013". exchangeserverpro.com. Archived from the original on 17 October 2012. 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. ^ "Microsoft kündigt Exchange 2019 an". 26 September 2017.
  30. ^ "Microsoft Exchange Server 2019 Public Preview".
Retrieved from "https://en.wikipedia.org/enwiki/w/index.php?title=History_of_Microsoft_Exchange_Server&oldid=1245275035"