With Exchange Server 2016 we've taken what we learned running Exchange Online to apply
to on-premises Exchange and over the next couple of minutes I'm going to show
you how we've refined the Exchange architecture rolls, what we're doing
to prevent to recover from data corruption and provide an update on how
Exchange can leverage cloud services.
To simplify Exchange server deployment
we've now taken away the CAS roll (Client Access Roll) and we've added the client services to
the mailbox role. So now you only have one roll to install the Exchange mailbox server. For the past two
releases our guidance has been to collocate roles and with 2016 we're simply
building that guidance into the product. Not only just putting the roles onto just
one server makes sense in terms of performance, as the role of complement
each other really well in terms of how they use system resources, it also means you
can raise the overall availability of the system and reduce the number of servers
you have to deploy. To illustrate let's look at an example let's imagine your
deployment of CAS and mailbox servers to be rowers in a boat. With previous versions
of Exchange you might have deployed four CAS and 10 mailbox servers but by
colocating the roles you will actually end up with more CAS servicing clients
than you would have previously had and you can probably reduce the overall server
count as you are spreading the load more effectively. So you have more mailbox and
CAS but overall you have fewer servers and of course that also means the loss
of any one server has a smaller impact on the overall system.
We're also bringing a lot
of the work we've been doing in Exchange Online to make Exchange faster in
recovering from failure and more reliable to our on-prem release.
The first change to mention is related to ReFS the Resilient File System and you might be
wondering why I mention this because you know we added support for ReFS volumes
with Exchange Server 2013.
Well it's because with Exchange Server 2016 we're making this are recommended
file system. Why? Well, it's more resilient, the clue is in the name of the feature
afterall, and we've learned that using it decreases the number file system
corruption incidents which for Exchange specifically means it
decreases the number of database receipts. Now if you watched the preview
video we did, you'll remember we talked about the work we've been doing to allow
search indexes to be created from passive database copies.
Well we're not gonna have a specific feature ready in time for RTM but when
we do ship it an upcoming CU you will also notice that database failover times
have decreased failovers are faster. It's a side effect of the indexing work we did and
we'll think you'll find those two changes are worth waiting for.
Speaking of CUs we also plan on releasing the first Exchange Service 2016 CU
you early in calendar year 2016. And one last thing here, Exchange 2016 runs better
than ever and commodity hardware. You don't need SANs, you don't need big
servers filled with memory and processors. What you need are cheap two socket boxes
with local storage and a minimal amount of RAM. That's exactly how we running
Office 365 that's exactly how you should run it on-prem. Don't forget, scale out and not up.
The last area to talk about is how we've made changes to the way Exchange can
connect to and consume services from the cloud
plus we have some comments on e-discovery and compliance. We've continued
to develop a hybrid deployment capabilities giving you the choice to
deploy mailboxes on-prem or in the cloud.
We've updated the wizard so it's downloaded from the cloud each time you
run it so you always get the latest and greatest version of the tool and it
backs up our belief that you can benefit from features we offer the cloud even if
you want to keep your mailboxes on-prem. Features like Advanced Threat
Protection a feature you can add to an Exchange Online Protection subscription
that's a great example. Advanced Threat Protection uses some very cool
technology to scan and process mail that you receive from the internet and can
protect users in several different ways. For example, it can identify and protect
your users against unknown viruses and malware.
It's giving your users zero-day protection. Messages and attachments that are
suspected of being suspicious are sent to a special hypervisor environment where they are
pass-through tools that can detect if their intent is malicious. And if it is?
They take care of it right there and then. ATP can also protect against the very common
tricks spammers try to play today where they try to send messages containing
links that appear valid, trying to trick the user into clicking them. Well ATP can spot
those messages and replace the URLs in the messages before they get to the user
pretty cool and simple bolt on to your on-prem Exchange Server deployment. Well last but
certainly not least, we've added 13 new sensitive information types to Exchanges
DLP capabilities and we've re-architected e-discovery cert to increase
the speed of results.
Also new is the ability to place data in public folders on hold to
allow archiving and eDiscovery. That's been a longstanding requests from customers
and we're excited to
deliver it in this release.
These are just a few highlights of the work our team has
done to simplify architecture, improve reliability, recoverability and hybrid
coexistence with Exchange Server 2016. You can start evaluating and deploying
Exchange Server 2016 today. Thank you for watching.
Office Mechanics
Microsoft Office Office.com/Mechanics