Microsoft Exchange Server is the mail server and server calendar developed by Microsoft. It runs exclusively on the Windows Server operating system.
The first version of Exchange Server to be published by Microsoft is Exchange Server 4.0. Exchange originally used the X.400 directory service but switched to Active Directory later. Versions 4.0 and 5.0 are bundled with an email client called Microsoft Exchange Client . It was discontinued in favor of Microsoft Outlook.
Exchange Server uses proprietary protocols called MAPI. Over time, however, it adds support for POP3, IMAP, SMTP, and EAS.
The Exchange Server is licensed both in the form of software and on-site software as a service. In local form, customers purchase client access licenses (CALs). In software as a form of service, Microsoft receives a monthly service fee instead.
Video Microsoft Exchange Server
Histori
Microsoft has sold a number of more simple email products before, but Exchange Server is an entirely new X.400 client-server email system with one database store that also supports X.500 directory services. The directory used by Exchange Server eventually becomes Microsoft Active Directory service, an LDAP-compliant directory service that is integrated into Windows 2000 as the foundation for Windows Server domains.
Ada sejumlah versi:
- Exchange Server 4.0
- Exchange Server 5.0
- Exchange Server 5.5
- Exchange Server 2000
- Exchange Server 2003
- Exchange Server 2007
- Exchange Server 2010
- Exchange Server 2013
- Exchange Server 2016
- Exchange Server 2019 (belum dirilis, diumumkan pada Ignite 2017)
​​Exchange Server 2016
The latest version was released on October 1, 2015 and introduced a number of changes:
- Mailbox Server and Edge Transport are the only roles available.
- Updates to the UI in Outlook on the web (formerly Outlook Web App).
- Office 365 Packages : The Hybrid Configuration Wizard (HCW) that comes with Exchange 2013 is on the move to become a cloud-based app. When configuring a hybrid implementation in Exchange 2016, users will 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 details about the new features, see the following Microsoft TechNet article: What's new in Exchange 2016
Maps Microsoft Exchange Server
Clustering and high availability
Exchange Server Enterprise Edition supports grouping up to 4 nodes when using Windows 2000 Server, and up to 8 nodes with Windows Server 2003. Exchange Server 2003 also introduces active-active clustering, but only for two-node clusters. In this setting, both servers in the cluster are allowed to be active simultaneously. This is contrary to the more common passive on-pass mode in which failover servers in any cluster nodes can not be used at all when their associated home servers are active. They have to wait, inactive, so the home server at the node fails. The next performance issue with active-on mode has made Microsoft recommend that it no longer be used. In fact, support for active-enabled mode grouping has been discontinued with Exchange Server 2007.
Exchange grouping (active-active or active-passive mode) has been criticized because of the requirement for servers in the cluster node to share the same data. Grouping in Exchange Server provides redundancy for Exchange Server as an app , but not for Exchange data . In this scenario, data may be considered a single point of failure, although Microsoft's description of this set-up as a "Shared Not Available" model. This void has been populated by ISV manufacturers and storage, through "site endurance" solutions, such as geo-clustering and asynchronous data replication. Exchange Server 2007 introduces new cluster terminology and configuration that addresses the previous "shared data model" shortcomings.
Exchange Server 2007 provides built-in support for asynchronous replication that is modeled on the SQL Server "Log shipping" in the cluster CCR (Cluster Continuous Replication) cluster, built on the MSCS MNS (Cluster Service - Cluster Majority Node Set) that does not require shared storage. This cluster type can be cheap and placed in one, or "stretched" in the two data centers for protection against site-wide failures such as natural disasters. Limitations of the CCR cluster are the ability to have only two nodes and a third node known as the "selector node" or witness sharing file that prevents the "brain split" scenario, generally hosted as a file share on Hub Transport Server. The second cluster type is the traditional grouping available in earlier versions, and is now referred to as SCC (Single Copy Cluster). In Exchange Server 2007, the deployment of CCR and SCC clusters has been simplified and improved; the whole clustering process takes place during the installation of Exchange Server. LCR or Local Continuous Replication has been referred to as "a group of the poor". It is designed to allow data replication to an alternate drive attached to the same system and is intended to provide protection against local storage failures. It does not protect against cases 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 both servers belonging to a Windows cluster that are usually located in the same data center, SCR can replicate data to a non-clustered server, located in separate data centers.
With Exchange Server 2010, Microsoft introduced the concept of Database Availability Group (DAG). DAG contains Mailbox servers that are members of DAG. After the Mailbox server is a DAG member, the Mailbox Mailbox on the server can be copied to other DAG members. When Mailbox servers are added to DAG, Windows Failover Clustering roles are installed on the server and all the required grouping resources are created.
License
Like any Windows Server product, Exchange Server requires a client access license, which is different from Windows CAL. Corporate license agreements, such as Enterprise Agreement, or EA, including Exchange Server CALs. It also comes as part of Core CAL. Just like Windows Server and other server products from Microsoft, there is an option to use the User CAL or the Device CAL. The CAL device is assigned to devices (workstations, laptops or PDAs), which can be used by one or more users. User CALs are assigned to users, enabling them to access Exchange from any device. Users and CAL Devices have the same price, however, they can not be used interchangeably.
For service providers who want to host Microsoft Exchange, there is a Service Provider License Agreement (SPLA) available where Microsoft receives a monthly service fee, not a traditional CAL. Two types of CAL Exchange available: Standard CAL Exchange and CAL Enterprise Exchange. Enterprise CAL is an additional license for CAL Standards.
Client
Microsoft Exchange Server uses a proprietary remote procedure call (RPC) protocol called MAPI/RPC, which is designed for use by Microsoft Outlook. Clients who are able to use Exchange Server ownership features include Evolution, Hiri and Microsoft Outlook. Exchange Web Services (EWS), an alternative to the MAPI protocol, is a documented SOAP protocol introduced with Exchange Server 2007, which significantly reduces synchronization time between server versus WebDAV, 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 through the Apple Mail app. Built-in support with Mac OS X 10.6 requires that Exchange organizations run 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. The Exchange Server mailbox can also be accessed via a web browser, using Outlook Web App (OWA). Exchange Server 2003 also displays an OWA version for mobile devices, called Outlook Mobile Access (OMA).
Microsoft Exchange Server up to version 5.0 comes bundled with Microsoft Exchange Client, a multi-purpose original client for email. After version 5.0, it was replaced by Microsoft Outlook, which is part of Microsoft Office 97 and later. When Outlook 97 was released, Exchange Client 5.0 was still under development and later released as part of Exchange Server 5.0, mainly because Outlook is only available for Windows. Then, in Exchange Server 5.5, the Exchange Client has been deleted and Outlook is the only Exchange client. As part of Exchange Server 5.5, Outlook is released for other platforms.
The original Windows 95 "Inbox" client also uses MAPI and is called "Microsoft Exchange". A stripped down version of Exchange Client that does not have support for Exchange Server is released as Windows Messaging to avoid confusion; it is included with Windows 95 OSR2, Windows 98, and Windows NT 4. It was stopped because it moved to standard emails like SMTP, IMAP, and POP3, all of which support Outlook Express better than Windows Messaging.
Exchange ActiveSync
Support for Exchange ActiveSync is added to Microsoft Exchange Server 2003. It enables compatible devices such as Windows Mobile devices or smartphones to sync emails, contacts and other data securely with Exchange servers and has become a popular mobile access standard for businesses due to support from companies like Nokia and Apple Inc. as well as its device security and compliance features.
Support for push email is added to Exchange Server 2003 with Service Pack 2 and is supported by Windows Phone 7, iPhone and Android phones.
Exchange ActiveSync Policies allows administrators to control which devices can connect to the organization, disable the feature remotely, and wipe the lost or stolen devices remotely.
Exchange Server is hosted as a service
The complexity of the Exchange Server management makes it attractive for organizations to purchase it as a hosted service.
Third party providers
It has been possible from a number of providers for over 10 years, but by June 2018 many service providers have marketed this service as "cloud computing" or "Software as a Service". Exchange hosting allows Microsoft Exchange Server to run on the Internet, also referred to as Cloud, and managed by "Hosted Exchange Server provider" instead of building and deploying in-house systems.
Microsoft
Microsoft Exchange Online is an email solution, calendar and contacts sent as a cloud service, hosted by Microsoft. This is essentially the same service offered by Exchange providers that are hosted and built on the same technology as Microsoft Exchange Server. Exchange Online provides end users with a familiar email experience across PCs, Web and mobile devices, while providing IT administrators or small businesses and professional web-based tools to manage their online deployments.
Microsoft Exchange is available both as in-place software and as a service hosted with Exchange Online. Customers can also choose to combine local and online options in hybrid deployment.
Hybrid deployment can serve as an advanced step between internal Exchange solutions and fully hosted. This configuration provides many features such as enabling organizations to migrate user mailboxes by better providing the ability to not only move local mailboxes to Exchange Online, but from Exchange Online back to the local server, cloud-based messaging for mailboxes and mailbox management a centralized letter for both infrastructures, to name a few.
With local server requirements; ie Exchange Server and Active Directory Azure sync server, there is an overhead of resources for implementing hybrid solutions. Hybrid implementation remains a popular choice for organizations who are unsure of the need or urgency to make a full cut-over to Exchange Online; also allows the migration of staggered emails.
Hybrid monitoring and reporting tools include Microsoft Exchange, Lync, SharePoint, Windows, and the main Active Directory server in place, in addition to using replica data to report the cloud user experience. Server monitoring is essential for optimal maintenance of server infrastructure, as well as, cloud reporting to monitor the user experience.
History
Exchange Online was first provided as a service that was hosted in a dedicated customer environment in 2005 to select a pilot customer. Microsoft released the Exchange Online multi-tenant version as part of the Business Productivity Online Standard Suite in November 2008. As of June 2011, as part of the commercial release of Microsoft Office 365, Exchange Online has been updated with Exchange Server 2010 capabilities.
Exchange Server 2010 is developed concurrently as a server product and for Exchange Online services.
See also
- Microsoft Exchange Server History
- Email server comparison
- Expandable Storage Engine
- List of apps with iCalendar support
- List of collaborative software
- Innovative Communication Alliance (Microsoft - Nortel)
References
External links
- Official website
Source of the article : Wikipedia
0 Comments