![[Translate to US:] Microsoft Exchange](https://edv-solutions.org/fileadmin/_processed_/f/8/csm_logo_microsoft_exchange_server_44bcc1a658.webp "[Translate to US:] Microsoft Exchange"){kind=logo}
Experience the power of Exchange 2019 with customized solutions from EDV Solutions. Our experts offer comprehensive implementation and management of your Exchange environment to optimize your communication and collaboration. With Exchange 2019, you benefit from improved security, higher availability and a user-friendly interface that increases your productivity.
Discover how Exchange 2019 and EDV Solutions can revolutionize your IT infrastructure. Contact us today to find out more about our customized solutions!
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 only for clusters with two nodes. In this setup, both servers in the cluster can be active at the same time. This is in contrast to the more common Exchange active-passive mode, where 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 this mode should no longer be used. In fact, support for clustering in active mode was discontinued with Exchange Server 2007.
Exchange clustering (active-active or active-passive mode) has been criticized because the servers in the cluster nodes must use the same data. Clustering in Exchange Server provides redundancy for Exchange Server as an application, but not for the Exchange data. In this scenario, the data can be considered a single point of failure, although Microsoft describes this setup as a "shared nothing" model. However, this gap has been filled by ISVs and storage vendors through "site resilience" solutions such as geo-clustering and asynchronous data replication.
The Exchange functionality in the 2016 version is divided into two so-called roles, which are defined during installation:
Mailbox - contains the main functionality, holds the databases and receives client requests Edge transport - additional security for email transmission between the internal network and the Internet (e.g. spam filtering); normally located in a DMZ
Client-server communication
Microsoft Exchange Server uses a proprietary interface called MAPI to communicate with the client, whose calls are transported using the RPC and HTTP protocols and which is used by Microsoft Outlook for Windows, among others. When using current versions of Exchange Server and Outlook, the RPC layer is deactivated in favor of greater flexibility and MAPI is transmitted directly via HTTP.
Outlook for Macintosh, on the other hand, uses the newer EWS server interface. In future, third-party providers should also use this instead of the MAPI interface.
The initially simple e-mail system became a comprehensive groupware solution. In the 2003 version, the Intelligent Message Filter (IMF) was implemented for the first time as a server-side filter that makes it possible to filter out unwanted emails. Since the 2013 version, rudimentary anti-virus software has also been included.
The functionality includes:
E-mails Appointments/calendar Tasks Contacts/addresses Notes Mobile e-mail access via ActiveSync technology E-mail retrieval via POP3/IMAP4, e-mail delivery via SMTP Global address book Certificate-based authentication Support for Secure/Multipurpose Internet Mail Extensions (S/MIME) Intelligent anti-spam filter: SmartScreen filter technology, Intelligent Message Filter (IMF) Global acceptance and rejection list (white list/black list) Anti-virus filtering or anti-virus API, with which third-party anti-virus software can be connected. Anti-virus API, with which third-party anti-virus software can be connected Support for the sender ID email authentication protocol Outlook Web App, web access to the server's functions Mixed operation with an Office 365 Exchange online service Data loss prevention
Basically, data is divided into personal and user-dependent data on the one hand and shared data such as the so-called public folders on the other, which makes group work possible.
Microsoft Outlook is usually used as the front-end application.
Version history Version Year 4.0 1996 5.0 1997 5.5 1998 2000 (6.0) 2000 2003 (6.5) 2003 2007 (8.x) 2006 2010 (14.x) 2009 2013 (15.0) 2012 2016 (15.1) 2019 2015 2018
Microsoft originally offered the MS Mail mail system (up to and including version 3.5), but this was no longer able to meet the requirements of larger environments. It was only possible to create a maximum of 500 mailboxes on one server, and storing the data in a file tree turned out to be more and more of a problem as the volume of mail increased due to the amount of data to be managed. Exchange itself was developed from scratch. The version number 4.0 was used for the first Exchange Server in order to suggest a proximity to Microsoft Mail and to encourage customers to switch to Exchange. Right from the start, secure data processing (relational database with 2-phase commit transactions) and scalability played a special role in the development. The Jet Engine (Jet Blue), which was later also used for products such as Active Directory or the Kerberos Distribution Server, has formed the basis since the beginning.
