5/23/2015

What'sNewInExchangeServer2013|ExchangeServer2013contentfromWindowsITPro

IT/DevConnections

Forums

Store

Twitter
Facebook
Google+
LinkedIn
RSS
REGISTER LOGIN
WindowsITPro
Windows

ExchangeServer

SharePoint

Virtualization

Cloud

SystemsManagement

Training

InfoCenters

HOME > EXCHANGE SERVER > EXCHANGE SERVER 2013 > WHAT'S NEW IN EXCHANGE SERVER 2013

Whereexpertsandprofessionalsshareinsightsand
inspirationstogrowbusinessandbuildcareers

WindowsITProCommunity
SignupforExchange&Outlooknewsletter.

What'sNewInExchangeServer2013

emailaddress

Architecturalchangesandbrandnewfeaturesarehallmarksofthenewestrelease

Country

Jan22,2013

by

PaulRobichaux

Follow

Followers 1157

Articles 82

Comments

Enteryouremailabovetoreceivemessagesabout
offeringsbyPenton,itsbrands,affiliatesand/orthird
partypartners,consistentwithPentonsPrivacyPolicy.

RSS FollowFollowWe're
feed
us on on
on
TwitterLinked

SHARE

Tweet

Recommend

COMMENTS 0

EMAIL

FeaturedProducts
PowerShellforExchange
Administrators
PresentedbySteveGoodman
Wednesday,May27th
Havingagoodunderstandingof...

BreakingBatch:LeaveBatch
BehindandSwitchtoPowerShell
PresentedbyBillStewart
Thursday,June25th
NowthatPowerShellisbuiltinto
Windows...

Windows10TechnicalDeepDive
PresentedbyJohanArwidmark
Tuesday,June30th
JoinJohanArwidmarkforthis3hour...

MicrosoftrecentlyreleasedExchangeServer2013,labelingit"thenewExchange."(This
interestingbrandingdecisionimplicitlylabelsallotherversionsofExchangeas"old,"with
allthenegativeconnotationsthatlabelcarries.)Understandingwhat'snewinExchange
2013requiresustodigintothearchitecturalandfeaturechangesthatMicrosofthas
madesome(butnotall)ofwhichthecompanyistoutingheavily.

VIEWCATALOG VIEWSHOPPINGCART

WindowsForums

ArchitecturalChanges
TheWindowsITProforums

IfyourememberExchangeServer2003,thenthemajorarchitecturalchangein
Exchange2013willseemveryfamiliar.Therearenowonlytworoles:theMailboxserver
roleandtheClientAccessserverrole.
Thissetupisessentiallythesameasthefrontend/backendarchitectureinExchange
2003,althoughtherearemajorimplementationdifferences.Microsoftdecidedtosplitthe
rolesinthiswaytodramaticallysimplifyimplementationatlargescales.Tightcoupling
betweentheserverrolesnolongerexists:TheClientAccessserverroledoesn'tkeepany
stateorsessiondataandcanbeupgraded(orrebooted)independentlyoftheMailbox
serverrole,andviceversa.Thischangehasseveralinterestingimplications:
http://windowsitpro.com/exchangeserver2013/whatsnewexchangeserver2013

aremovingtomyITforum.com!
Getanswerstoquestions,
sharetips,andengagewith
theITprofessional
community.

1/6

5/23/2015

What'sNewInExchangeServer2013|ExchangeServer2013contentfromWindowsITPro
TheExchange2013ClientAccessserverrole(formerlycalledtheClientAccessFrontEnd
inMicrosoftinternaldocuments)becomesessentiallyasupersmartproxythatnolonger
needstomaintainstateoraffinity.MuchofthecomplexityofconfiguringtheExchange
2010ClientAccessserverrolevanishes.
Loadbalancingiscompletelydifferent.Withnorequirementforaffinity,loadbalancers
thatworkatLayer4(thenetworklayer)oftheOSImodelcanbeused.(Therearestill
casesinwhichitmakessensetouseapplicationawareloadbalancersthatapplygreater
intelligencetodecidingwhenandhowtodistributeloadbetweenservers.)
RemoteProcedureCall(RPC)formailboxaccessisdead.YoucanstilluseRPCover
HTTPSecure(HTTPS),buttheRPCClientAccessserviceisnolongerpartofthe
equation.ThischangeenablestheuseofHTTPSbasedloadbalancing,withoutthe
Exchange2010requirementforseparatenamespacesorcertificates.
TheHubTransportserverroleisgone,itsresponsibilitiessplitbetweentheClientAccess
serverandMailboxserverroles.GiventhatfewExchange2010siteshadcombinedthe
MailboxandHubTransportroles,thischangeisn'thuge.
NewservicesrunontheMailboxserver,soyoumightneedtoreexaminethescalingand
sizingdecisionsthatyoumadeforExchange2010deployments.

BrandNewFeatures

Asistypicalforanewreleaseofamajorproduct,Exchange2013isfullofnewfeatures.
Knowingwhattolabel"new"cansometimesbedifficultbecauseofMicrosoft'shabitof
makingmajorenhancementstoexistingfeatures,butseveralgenuinelyfreshfeaturesare
included.Themostsignificantoneisarguablythenewmanagedavailabilityfunctionality.
MicrosoftdescribesmanagedavailabilitythuslyontheExchangeTeamBlog:
Managedavailabilityisamonitoringandrecoveryinfrastructurethatisintegratedwith
Exchange'shighavailabilitysolution.Managedavailabilitydetectsandrecoversfrom
problemsastheyoccurandastheyarediscovered.
Thisdescriptionneatlycapturesthemajorpointsofmanagedavailability:Itfocuseson
detectingproblemsthattheenduserwillnoticeandthenrepairingthemautomatically
wheneverpossible.TheExchange2013managedavailabilityimplementation
accomplishesthistaskbyperformingseveralkindsofautomatedchecksthatprobe
variouspartsoftheinfrastructure.Basedontheresultsofthesetests,avarietyof
automatedresponderscantakeaction.Theseactionscanrangefromrestartingthe
responderservice,totakingaprotocolonamachineoutofservice(whichallowsclient
traffictobesenttoanothermachinerunningthesameprotocol),toforcingaserver
rebootandrestart.There'salsotheescalateresponder,whosejobitistofireaneventthat
triggersspecialbehaviorinSystemCenterOperationsManagerorothermonitoring
software.Inthisway,Exchangehasacustomizedmethodforindicatingahighpriority
failurethatrequireshumanintervention.Managedavailabilityrepresentsanambitious
effortbyMicrosofttobringhighscale,datacenterstylemanagementtoExchange.This
effortoffersalotofpotential,althoughI'mreservingjudgmentonitsworthuntilIseeit
proveninthefield.
Anothermajorchangeistheavailabilityofasingleintegratedediscoveryexperience.You
cannowperformdiscoverysearchesthatincludeExchangemailboxesandpublicfolders,
archivedMicrosoftLyncconversations,andmaterialthat'sstoredinMicrosoftSharePoint
fromasingleSharePointbasedinterface.Althoughthisfeaturerequiresthatyoudeploy
SharePoint2013,organizationsthatneedtoperformdiscoverysearcheswillfindthis
featurevaluablebecauseitenablesselfservicediscoverysearchesforuserswith
appropriatepermissions.
Exchange2013alsoincludesagroupoffeaturesthatarelumpedundertherubricofdata
lossprevention(DLP).Thegoalofthesefeaturesistoreducetheriskthatyour
organizationwillcommitorsufferbreachesofsensitivedatasuchaspersonally
identifiableinformation(PII)ofcustomers,datathatmustbeprotectedunder
regulationssuchastheUSHealthInsurancePortabilityandAccountabilityAct(HIPAA)
orEuropeanUnionDataProtectionDirective(EUDPD),ordatathatyoujustdon'twant
tobedisclosed.DLPfeaturesincludearobustsetoftransportruleliketoolsforscanning
messagesforsensitivedata,apredefinedsetofpoliciesforcommonregulatory
http://windowsitpro.com/exchangeserver2013/whatsnewexchangeserver2013

2/6

5/23/2015

What'sNewInExchangeServer2013|ExchangeServer2013contentfromWindowsITPro

requirements,andtoolsforcustomizingtheincludeditemsorbuildingyourown.
ItwillbeinterestingtoseewhichofthesefeaturesdriveExchange2013adoption.Some
arelikelytobeofinteresttoasmallnumberoflargecustomers,whereasafewothers
seemclearlytargetedatabroaderaudience.
MailboxServerChanges

TheMailboxserverroleremainsatthecoreofExchange.Forthisrelease,Microsoft
rewrotetheExchangeInformationStoreservice(store.exe)completelyinmanagedcode,
takingadvantageofthe.NETcommonlanguageruntime(CLR)memorymanagement
support.
TheinternalarchitectureoftheInformationStoreservicehaschangedagooddealas
well.There'snowanewservice,theExchangeReplicationservice,whichcontrolsfailover
andswitchoveroperationsanddatabasemountsanddismounts,plusaserviceprocess
controllerthatmanagesthedatabaseworkerprocesses.Eachdatabasenowhasitsown
workerprocess,sofailureoftheInformationStoreserviceprocessshouldaffectonlyone
databaseatatime.Anadditionalrelatedchangehasbeensomewhatcontroversial:
Exchange2013isnowlimitedtoamaximumof50databasesperserverinsteadof100.It
remainstobeseenhowmanycustomersthischangeaffectsandwhetherMicrosoftwill
considerliftingthelimitinafuturerelease.
ThesechangesarecoupledwithseveralaggressiveoptimizationstotheStoreschema
itself.Microsoft'sgoalforthisreleasewastoreduceoverallI/Ooperationspersecond
(IOPS)fromExchange2010byasmuchas50percentwhilesimultaneouslyenablingthe
widespreaduseofdatabasesupto100GB.Todothis,Microsoftessentiallytradedoff
CPUandRAMusageforIOPS.Byincreasingthedegreeofphysicalandlogicalcontiguity
intheExchange2013schema,fewerlargeI/Oswillberequiredbutanincreased
amountofCPUwillbeneededtohandlethem.Microsoftisexpectedtoupdatethe
ExchangeMailboxRoleCalculator(familiarfrompreviousversionsofExchange)totake
thesechangesintoaccount.
TheExchange2013Storefullysupportsmixingmultipledatabasespervolume.For
example,youcanputoneactivedatabaseandmultiplepassivedatabasesonasingledisk.
With8TBdrivesexpectedtobeavailablesoon,andwiththeexistingrecommendationof
2TBasamaximumsizeforExchangedatabases,leveragingboththestorageandIOPS
potentialoflargedisksbycombiningdatabasesmakessense.ThenewStorealso
implementsanewAutoReseedfeature.Thisfeaturecanimmediatelycreateanewpassive
replicaofadatabaseonafaileddiskbyusingasparediskontheserver,quickly(and
automatically)replacingthefailedcopytomaintainthecorrectnumberofcopiesinthe
databaseavailabilitygroup(DAG).
InoneofthemostsurprisingchangestoExchange2013,Microsofthascompletelyre
implementedpublicfolders.Thenew"modern"publicfoldersystemreplacestheold
multimastermodel,whichwasdependentonthefinickysystemofpublicfolder
replicationintroducedinExchange4.0.Thenewsystemismuchsimpler:Publicfolders
essentiallylookandactlikedatabases.PublicfolderdatabasesarestoredinDAGs,justas
mailboxesare,soyouprotectpublicfoldersagainstoutagesbyaddingmultiplereplicasof
agivenpublicfolderdatabasetoaDAG.Clientsalwaysconnecttotheactivecopyofthe
publicfolder,whichmighthaveimplicationsforscalabilityinsomeenvironments.
ClientAccessChanges

Aspreviouslymentioned,thenewClientAccessserverroleinExchange2013nolonger
rendersdatafortheclient.Theonlythingitdoesisperformproxyconnectionsfromthe
clienttotheappropriateMailboxserver.Thisproxyonlydesigneliminatestheneedfor
theClientAccessservertomaintainaffinityorstatewithclients,whichinturnenablesa
muchbroaderrangeofpotentialloadbalancingsolutions.DNSroundrobinand
WindowsNetworkLoadBalancing(NLB)arebothfullysupported,althoughneithercan
recognizethepresenceofserverfailures.

http://windowsitpro.com/exchangeserver2013/whatsnewexchangeserver2013

3/6

5/23/2015

What'sNewInExchangeServer2013|ExchangeServer2013contentfromWindowsITPro

ClientconnectionscanuseIMAP,POP,orExchangeWebServices(EWS),buttheyno
longeruseMessagingAPI(MAPI)RPCs.Instead,allMicrosoftOutlookclientsmustnow
connectbyusingtheOutlookAnywherefeature(anothernameforRPCoverHTTPS),
whichwrapsMAPIRPCsinsideHTTPSpackets.Thischangeenablesclientstorequest
mailboxconnectionsusingamailboxgloballyuniqueidentifier(GUID)plustheuser
principalname(UPN)suffix,withoutanyincludedreferencetoaMailboxserver'sFully
QualifiedDomainName(FQDN).MailboxesaremuchmoreportablebecausetheClient
AccessserveranditsclientsnolongerneedtoknoworcareaboutMailboxservernames.
ThecomplexExchange2010systemofinterrelatednamespaces(andcertificatestosecure
them)isgone,replacedwithadramaticallysimplerimplementation.Tofacilitatetheuse
ofOutlookAnywhereinternally,theClientAccessserverrolenowsupportsanewinternal
hostname(andmatchingauthenticationmethod),whichwillbeused(ifdefined)for
clientsontheLAN.
AnotherpleasantsideeffectofthechangetotheClientAccessserverdesignisthatcross
siteaccessismuchsimpler.ClientsconnecttowhicheverClientAccessserveris
convenient,andtheClientAccessservercanperformHTTPredirectsasnecessarytofind
thecorrectMailboxserveracrossActiveDirectory(AD)sites.
TheservicesthattheClientAccessserverofferstoclientshavechangedquiteabitaswell.
OutlookWebApp(OWA)2013iscompletelyrewrittenandincludessomecompellingnew
features,suchasgreatlyimprovedsupportformobiledevicessuchasAppleiPads.OWA
2013canrunofflineonsupportedbrowserscurrently,GoogleChrome,Microsoft
InternetExplorer(IE)10,andAppleSafari5.x/6.xonMacOSX.
TransportChanges

Thetransportprocesshaschangedsignificantlybecauseofthetworolearchitecture.
WhereasExchange2007andExchange2010hadaseparateHubTransportrole,
Exchange2013doesnot.TheClientAccessserverrolehoststhenewFrontEndTransport
service,whichhandlesallinboundandoutboundSMTPtraffic.Theservicedoesn't
performanycontentfiltering,althoughitdoesprovidefilteringbasedonconnection,
senderorrecipientidentity,andprotocolbehavior.TheFrontEndTransportservice'srole
israthertoactasacentralized,loadbalancedingressandexitpointforallSMTPtraffic.
BearinmindthattheClientAccessserverisn'tintendedtoreplacetheEdgeTransport
role,sodeployingitinaperimeternetworkisunsupported.
ThenewFrontEndTransportservicehasacompletelynewapproachtomailacceptance
anddelivery:Ithasnopermanentqueues.WhenanewSMTPconversationisopened,the
serviceacceptstheconnection,performsfilteringbasedontheSMTPenvelopedata,and
thendeterminestheroutetothe"best"Mailboxserverbeforestartingthedeliveryprocess.
TheMailboxserverisresponsibleforacceptingandqueuingthemessage.IftheFront
EndTransportservicecannotconnecttoaMailboxserver,oriftheserverdoesn'taccept
themessage,thentheFrontEndTransportservicereturnsSMTPerror421tothesender,
indicatingatransientfailurethatmustberetriedlater.Thisapproachdrastically
simplifiestheFrontEndTransportserviceatthecostofmovingthequeuing,
redundancy,anddeliverylogicovertotheMailboxrole.
TheMailboxserverrunsthreenewtransportrelatedservices:
TheMailboxTransportservicedoesmuchofwhattheformerHubTransportroledid.
Theprocessofmailboxtransportisnowstateful,sotheMailboxTransportservice
maintainsstateinformationabouteachmessageasitpassesthroughtheengine.Mailbox
transportperformspolicyenforcement(includingenforcingsizelimits)andprovides
queuingformessages.ThisistheonlymailboxservicethatcommunicateswithFrontEnd
Transportservice.
TheMailboxTransportDeliveryserviceacceptsmailfromtheMailboxTransportservice
anddeliversittothemailboxdatabase.
TheMailboxTransportSubmissionserviceretrievesmailfromthemailboxdatabaseand
submitsittotheMailboxTransportserviceforprocessing.

ThedivisionoflaborbetweentheClientAccessserverandMailboxTransportservice
http://windowsitpro.com/exchangeserver2013/whatsnewexchangeserver2013

4/6

5/23/2015

What'sNewInExchangeServer2013|ExchangeServer2013contentfromWindowsITPro

deliversessentiallythesamehighavailabilityfortransportaswehadinExchange2010,
butit'simplementedverydifferently.TheMailboxTransportservicepersistsevery
submittedmessagebeforethemessageisacknowledgedtothesender.IftheMailbox
Transportservicedoesnotorcannotacceptthemessage,thentheFrontEndTransport
servicesendsa421errortothesenderandmessagedeliveryisreattemptedlater.
Messagesthataresuccessfullysubmittedtothetransportsystemaremaintaineduntil
theirfinaldelivery,andresubmissionofmessagesthatcouldn'tbedeliveredbecauseof
thelossofatransportdatabaseormailboxdatabasefailoverandswitchoverisautomatic.
ThisnewbehaviorisknownasSafetyNet,andit'scomplexenoughthatitwillprobablybe
thesubjectoffutureWindowsITProarticlesandExchangeTeamBlogposts.
Interestingly,Microsoftisn'tcurrentlyshippinganEdgeTransportroleinExchange2013
andhasn'tpubliclyannouncedwhetherorwhenitwilldoso.Relativelyfewcustomers
usetheEdgeTransportrole,soMicrosoftmighthavechosentowaitorevenbakethe
EdgefunctionalityintoafutureversionofanEdgenetworkproductsuchasitsUnified
AccessGateway(UAG)Serverline.
UnifiedMessagingChanges

UnifiedMessaging(UM)isperhapstheareainwhichfunctionalityhaschangedtheleast
inExchange2013.TheUnifiedMessagingroleisnowhostedontheMailboxserver.The
ClientAccessserverrunstheUnifiedMessagingCallRouterservice,whichaccepts
incomingcallsandredirectsthemtotheappropriateMailboxserver.TheMailboxserver
itselfisresponsibleforhandlingallinteractionwiththecaller,includingplayinga
voicemailgreetingorAutoAttendantmessageandrecordingthecaller'svoicemail.
TheremainingUMchangesareallenhancements.Forexample,theVoiceMailPreview
featureismoreaccurate.(AlthoughMicrosoftstilldoesn'tclaimthatitis100percent
accurate,norisitintendedtobe.)UMcannowresolvecontactsagainstallpersonal
Contactsfoldersinauser'smailbox.Therefore,callerIDresolutionnowworkswith
externalcontactsfromFacebook,LinkedIn,andotheraggregatedsources.Liketheother
Exchange2013roles,theUnifiedMessagingrolenowfullysupportsIPv6.Apartfrom
that,usersandadministratorswillprobablynotnoticeanymajordifferencesinhowUM
behaves.AdministratorswillnotetheadditionofafewnewExchangeManagementShell
cmdletsformanagingtheUMservicesandcallroutersettings.
AWarning

OnemajorissuedoesfacesitesthatwanttodeployExchange2013:Itcannotyetcoexist
withExchange2010onpremises.Exchange2010coexistencerequiresExchange2010
SP3,whichMicrosofthasannouncedbutnotreleasedasofthiswriting.Giventhe
troubleswithExchange2010rollupsduring2012,anyprospectivedeploymentof
Exchange2010SP3shouldbeapproachedcarefullyandwithathoroughtestingplan.
ThenecessarychangestosupportcoexistencearealreadydeployedonExchangeOnline,
soifyou'rewillingtomoveyourmailboxestoMicrosoftOffice365,youcandeploy
Exchange2013withoutfurtherdelay.Thisdelayisn'tallbad,though,becauseitgivesyou
theopportunitytotestExchange2013inalabenvironmentandgetabettersenseofits
newfeaturesandbehaviors.Itwillcertainlybeinterestingtoseehowcustomersadopt
Exchange2013andhowMicrosoftupdatesitsproductguidanceanddocumentationto
reflectthelessonslearnedfromthatadoption.

SHARE

Tweet

Recommend

PleaseLogInorRegistertopostcomments.

Related Articles
What'sNewInExchangeServer2013
WhatsNewinExchange2013ArchivingandeDiscovery
WhatsNewinExchange2013ArchivingandeDiscovery

http://windowsitpro.com/exchangeserver2013/whatsnewexchangeserver2013

5/6

5/23/2015

What'sNewInExchangeServer2013|ExchangeServer2013contentfromWindowsITPro

MicrosoftOfficeFilterPack2013nowavailable,butit'snotneededbyExchange2013
Office365forBusiness:WhattoExpectfor2013

WindowsITPro.com
Windows ExchangeServer SharePoint Virtualization Cloud SystemsManagement

Site Features

Penton

ContactUs

PrivacyPolicy

Awards

TermsofService

CommunitySponsors

Advertise

MediaCenter

Follow Us

RSS

Search WindowsITPro.com

Sitemap
SiteArchive
ViewMobileSite

Related Sites
DevPro SharePointPro SQLServerPro SuperSiteforWindows IT/DevConnections myITforum

Copyright2015Penton

http://windowsitpro.com/exchangeserver2013/whatsnewexchangeserver2013

6/6