Hello, little friends!
ExchangeServer 2016 Public preview can now be downloaded now, interested in small friends can experience! This version is special, because he was born in the cloud, can better integrate office365 deployment use. There are also many people called Exchange Server 2016 versions that are Exchange Server 2013 SP2 patches? What do you think of this?
Let me briefly talk a few words, if you have good suggestions, we will discuss the discussion together.
1. From the architecture, Exchange Server 2016 has scaled back server roles, and Microsoft believes that our hardware resources are now significantly cheaper and no longer a constraint. To remove this factor, Exchange 2016 is primarily designed to be simpler in size, improving hardware utilization and fault isolation. In the Exchange 2016 release, the number of server roles decreased to two: Mailbox and Edge Transport server roles. Cancels the CAS server role.
2, speaking of which, many people will ask a question, Exchange server 2016 releases the CAS server role, how do clients access it? In fact, the check box for Exchange CAS is missing, which does not mean that the CAS role does not exist. What Microsoft is doing is putting all CAS code on the MBX server. That is, mailbox Server. It turns out that this initiative has told us that once Exchange2010 was called a multi-role server, when we went to study him, we might need an effective way to first study the various roles of Exchange Server, and in terms of the coexistence of mailboxes, we need more hardware resources to use them. And now our preferred architecture is a hybrid deployment approach to better build on the Office 365 cloud.
3. According to the official, we can reduce the number of servers and increase the availability of our servers by getting rid of the CAS role. and improve our ability to maintain failure, we have the ability to recover better in the case of a failure, and while we are transitioning back to the exchange simple schema, it may be easier to do this exchange version when we do the migration, as far as the Exchange Management Console is concerned, Exchange 2016 Management control is very similar to Exchange 2013, and how to deal with Exchange system issues in a timely manner, such as Mailbox server availability, client responsiveness, and so on, and provides powerful assistive tools in Exchange 2016 to help us solve the problem. During the database DB copy process, log shipping is used, and the active node establishes an index in advance of transmitting to the passive node.
650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M01/70/15/wKioL1WxISviFZVTAAG8q4c6XjA444.jpg "title=" 1.png " alt= "Wkiol1wxisvifzvtaag8q4c6xja444.jpg"/>
4. In terms of client access, Exchange 2016 does not support Outlook 2003. To connect Microsoft Outlook to Exchange 2016, you need to use the Autodiscover service. In Exchange 2016, Microsoft Outlook clients can connect using Outlook everywhere (RPC/HTTP) or MAPI over HTTP Outlook 2013Service Pack 1 and later.
Exchange Andexchange Online supports the following versions of Outlook:
· Outlook 2013
· Outlook with KB2965295
· Outlook for Mac for Office 365
· Outlook for MAC 2011
This is written first, and will continue to be updated in the future.
This article is from "Jason's Tech Blog" blog, please be sure to keep this source http://jasondocs.blog.51cto.com/7223084/1677783
Exchange Server 2016 preview is released!