What's New in Exchange Server 2013 _ Exchange Server 2013 Content From Windows IT Pro
-
Upload
karan-mishra -
Category
Documents
-
view
217 -
download
1
description
Transcript of What's New in Exchange Server 2013 _ Exchange Server 2013 Content From Windows IT Pro
-
5/23/2015 What'sNewInExchangeServer2013|ExchangeServer2013contentfromWindowsITPro
http://windowsitpro.com/exchangeserver2013/whatsnewexchangeserver2013 1/6
Jan22,2013
EMAILTweet COMMENTS 0
Whereexpertsandprofessionalsshareinsightsandinspirationstogrowbusinessandbuildcareers
What'sNewInExchangeServer2013Architecturalchangesandbrandnewfeaturesarehallmarksofthenewestrelease
byPaulRobichaux
MicrosoftrecentlyreleasedExchangeServer2013,labelingit"thenewExchange."(ThisinterestingbrandingdecisionimplicitlylabelsallotherversionsofExchangeas"old,"withallthenegativeconnotationsthatlabelcarries.)Understandingwhat'snewinExchange2013requiresustodigintothearchitecturalandfeaturechangesthatMicrosofthasmadesome(butnotall)ofwhichthecompanyistoutingheavily.
ArchitecturalChanges
IfyourememberExchangeServer2003,thenthemajorarchitecturalchangeinExchange2013willseemveryfamiliar.Therearenowonlytworoles:theMailboxserverroleandtheClientAccessserverrole.
Thissetupisessentiallythesameasthefrontend/backendarchitectureinExchange2003,althoughtherearemajorimplementationdifferences.Microsoftdecidedtosplittherolesinthiswaytodramaticallysimplifyimplementationatlargescales.Tightcouplingbetweentheserverrolesnolongerexists:TheClientAccessserverroledoesn'tkeepanystateorsessiondataandcanbeupgraded(orrebooted)independentlyoftheMailboxserverrole,andviceversa.Thischangehasseveralinterestingimplications:
emailaddress
Country
EnteryouremailabovetoreceivemessagesaboutofferingsbyPenton,itsbrands,affiliatesand/orthirdpartypartners,consistentwithPentonsPrivacyPolicy.
RSSfeed
Followuson
FollowonTwitter
We'reonLinked
SignupforExchange&Outlooknewsletter.
WindowsITProCommunity
FeaturedProducts
PowerShellforExchangeAdministratorsPresentedbySteveGoodmanWednesday,May27th
Havingagoodunderstandingof...
BreakingBatch:LeaveBatchBehindandSwitchtoPowerShellPresentedbyBillStewartThursday,June25thNowthatPowerShellisbuiltintoWindows...
Windows10TechnicalDeepDivePresentedbyJohanArwidmarkTuesday,June30thJoinJohanArwidmarkforthis3hour...
VIEWCATALOG VIEWSHOPPINGCART
WindowsForums
TheWindowsITProforumsaremovingtomyITforum.com!Getanswerstoquestions,sharetips,andengagewiththeITprofessional
community.
HOME > EXCHANGE SERVER > EXCHANGE SERVER 2013 > WHAT'S NEW IN EXCHANGE SERVER 2013
Follow 5 Followers 1157 Articles 82 Comments
SHARE 0Recommend
IT/DevConnections Forums Store
TwitterFacebookGoogle+LinkedInRSS
Windows ExchangeServer SharePoint Virtualization Cloud SystemsManagement Training InfoCentersWindowsITPro
REGISTER LOGIN
-
5/23/2015 What'sNewInExchangeServer2013|ExchangeServer2013contentfromWindowsITPro
http://windowsitpro.com/exchangeserver2013/whatsnewexchangeserver2013 2/6
BrandNewFeatures
Asistypicalforanewreleaseofamajorproduct,Exchange2013isfullofnewfeatures.Knowingwhattolabel"new"cansometimesbedifficultbecauseofMicrosoft'shabitofmakingmajorenhancementstoexistingfeatures,butseveralgenuinelyfreshfeaturesareincluded.Themostsignificantoneisarguablythenewmanagedavailabilityfunctionality.MicrosoftdescribesmanagedavailabilitythuslyontheExchangeTeamBlog:
ManagedavailabilityisamonitoringandrecoveryinfrastructurethatisintegratedwithExchange'shighavailabilitysolution.Managedavailabilitydetectsandrecoversfromproblemsastheyoccurandastheyarediscovered.
Thisdescriptionneatlycapturesthemajorpointsofmanagedavailability:Itfocusesondetectingproblemsthattheenduserwillnoticeandthenrepairingthemautomaticallywheneverpossible.TheExchange2013managedavailabilityimplementationaccomplishesthistaskbyperformingseveralkindsofautomatedchecksthatprobevariouspartsoftheinfrastructure.Basedontheresultsofthesetests,avarietyofautomatedresponderscantakeaction.Theseactionscanrangefromrestartingtheresponderservice,totakingaprotocolonamachineoutofservice(whichallowsclienttraffictobesenttoanothermachinerunningthesameprotocol),toforcingaserverrebootandrestart.There'salsotheescalateresponder,whosejobitistofireaneventthattriggersspecialbehaviorinSystemCenterOperationsManagerorothermonitoringsoftware.Inthisway,Exchangehasacustomizedmethodforindicatingahighpriorityfailurethatrequireshumanintervention.ManagedavailabilityrepresentsanambitiouseffortbyMicrosofttobringhighscale,datacenterstylemanagementtoExchange.Thiseffortoffersalotofpotential,althoughI'mreservingjudgmentonitsworthuntilIseeitproveninthefield.
Anothermajorchangeistheavailabilityofasingleintegratedediscoveryexperience.YoucannowperformdiscoverysearchesthatincludeExchangemailboxesandpublicfolders,archivedMicrosoftLyncconversations,andmaterialthat'sstoredinMicrosoftSharePointfromasingleSharePointbasedinterface.AlthoughthisfeaturerequiresthatyoudeploySharePoint2013,organizationsthatneedtoperformdiscoverysearcheswillfindthisfeaturevaluablebecauseitenablesselfservicediscoverysearchesforuserswithappropriatepermissions.
Exchange2013alsoincludesagroupoffeaturesthatarelumpedundertherubricofdatalossprevention(DLP).Thegoalofthesefeaturesistoreducetheriskthatyourorganizationwillcommitorsufferbreachesofsensitivedatasuchaspersonallyidentifiableinformation(PII)ofcustomers,datathatmustbeprotectedunderregulationssuchastheUSHealthInsurancePortabilityandAccountabilityAct(HIPAA)orEuropeanUnionDataProtectionDirective(EUDPD),ordatathatyoujustdon'twanttobedisclosed.DLPfeaturesincludearobustsetoftransportruleliketoolsforscanningmessagesforsensitivedata,apredefinedsetofpoliciesforcommonregulatory
TheExchange2013ClientAccessserverrole(formerlycalledtheClientAccessFrontEndinMicrosoftinternaldocuments)becomesessentiallyasupersmartproxythatnolongerneedstomaintainstateoraffinity.MuchofthecomplexityofconfiguringtheExchange2010ClientAccessserverrolevanishes.
Loadbalancingiscompletelydifferent.Withnorequirementforaffinity,loadbalancersthatworkatLayer4(thenetworklayer)oftheOSImodelcanbeused.(Therearestillcasesinwhichitmakessensetouseapplicationawareloadbalancersthatapplygreaterintelligencetodecidingwhenandhowtodistributeloadbetweenservers.)
RemoteProcedureCall(RPC)formailboxaccessisdead.YoucanstilluseRPCoverHTTPSecure(HTTPS),buttheRPCClientAccessserviceisnolongerpartoftheequation.ThischangeenablestheuseofHTTPSbasedloadbalancing,withouttheExchange2010requirementforseparatenamespacesorcertificates.
TheHubTransportserverroleisgone,itsresponsibilitiessplitbetweentheClientAccessserverandMailboxserverroles.GiventhatfewExchange2010siteshadcombinedtheMailboxandHubTransportroles,thischangeisn'thuge.
NewservicesrunontheMailboxserver,soyoumightneedtoreexaminethescalingandsizingdecisionsthatyoumadeforExchange2010deployments.
-
5/23/2015 What'sNewInExchangeServer2013|ExchangeServer2013contentfromWindowsITPro
http://windowsitpro.com/exchangeserver2013/whatsnewexchangeserver2013 3/6
requirements,andtoolsforcustomizingtheincludeditemsorbuildingyourown.
ItwillbeinterestingtoseewhichofthesefeaturesdriveExchange2013adoption.Somearelikelytobeofinteresttoasmallnumberoflargecustomers,whereasafewothersseemclearlytargetedatabroaderaudience.
MailboxServerChanges
TheMailboxserverroleremainsatthecoreofExchange.Forthisrelease,MicrosoftrewrotetheExchangeInformationStoreservice(store.exe)completelyinmanagedcode,takingadvantageofthe.NETcommonlanguageruntime(CLR)memorymanagementsupport.
TheinternalarchitectureoftheInformationStoreservicehaschangedagooddealaswell.There'snowanewservice,theExchangeReplicationservice,whichcontrolsfailoverandswitchoveroperationsanddatabasemountsanddismounts,plusaserviceprocesscontrollerthatmanagesthedatabaseworkerprocesses.Eachdatabasenowhasitsownworkerprocess,sofailureoftheInformationStoreserviceprocessshouldaffectonlyonedatabaseatatime.Anadditionalrelatedchangehasbeensomewhatcontroversial:Exchange2013isnowlimitedtoamaximumof50databasesperserverinsteadof100.ItremainstobeseenhowmanycustomersthischangeaffectsandwhetherMicrosoftwillconsiderliftingthelimitinafuturerelease.
ThesechangesarecoupledwithseveralaggressiveoptimizationstotheStoreschemaitself.Microsoft'sgoalforthisreleasewastoreduceoverallI/Ooperationspersecond(IOPS)fromExchange2010byasmuchas50percentwhilesimultaneouslyenablingthewidespreaduseofdatabasesupto100GB.Todothis,MicrosoftessentiallytradedoffCPUandRAMusageforIOPS.ByincreasingthedegreeofphysicalandlogicalcontiguityintheExchange2013schema,fewerlargeI/OswillberequiredbutanincreasedamountofCPUwillbeneededtohandlethem.MicrosoftisexpectedtoupdatetheExchangeMailboxRoleCalculator(familiarfrompreviousversionsofExchange)totakethesechangesintoaccount.
TheExchange2013Storefullysupportsmixingmultipledatabasespervolume.Forexample,youcanputoneactivedatabaseandmultiplepassivedatabasesonasingledisk.With8TBdrivesexpectedtobeavailablesoon,andwiththeexistingrecommendationof2TBasamaximumsizeforExchangedatabases,leveragingboththestorageandIOPSpotentialoflargedisksbycombiningdatabasesmakessense.ThenewStorealsoimplementsanewAutoReseedfeature.Thisfeaturecanimmediatelycreateanewpassivereplicaofadatabaseonafaileddiskbyusingasparediskontheserver,quickly(andautomatically)replacingthefailedcopytomaintainthecorrectnumberofcopiesinthedatabaseavailabilitygroup(DAG).
InoneofthemostsurprisingchangestoExchange2013,Microsofthascompletelyreimplementedpublicfolders.Thenew"modern"publicfoldersystemreplacestheoldmultimastermodel,whichwasdependentonthefinickysystemofpublicfolderreplicationintroducedinExchange4.0.Thenewsystemismuchsimpler:Publicfoldersessentiallylookandactlikedatabases.PublicfolderdatabasesarestoredinDAGs,justasmailboxesare,soyouprotectpublicfoldersagainstoutagesbyaddingmultiplereplicasofagivenpublicfolderdatabasetoaDAG.Clientsalwaysconnecttotheactivecopyofthepublicfolder,whichmighthaveimplicationsforscalabilityinsomeenvironments.
ClientAccessChanges
Aspreviouslymentioned,thenewClientAccessserverroleinExchange2013nolongerrendersdatafortheclient.TheonlythingitdoesisperformproxyconnectionsfromtheclienttotheappropriateMailboxserver.ThisproxyonlydesigneliminatestheneedfortheClientAccessservertomaintainaffinityorstatewithclients,whichinturnenablesamuchbroaderrangeofpotentialloadbalancingsolutions.DNSroundrobinandWindowsNetworkLoadBalancing(NLB)arebothfullysupported,althoughneithercanrecognizethepresenceofserverfailures.
-
5/23/2015 What'sNewInExchangeServer2013|ExchangeServer2013contentfromWindowsITPro
http://windowsitpro.com/exchangeserver2013/whatsnewexchangeserver2013 4/6
ClientconnectionscanuseIMAP,POP,orExchangeWebServices(EWS),buttheynolongeruseMessagingAPI(MAPI)RPCs.Instead,allMicrosoftOutlookclientsmustnowconnectbyusingtheOutlookAnywherefeature(anothernameforRPCoverHTTPS),whichwrapsMAPIRPCsinsideHTTPSpackets.Thischangeenablesclientstorequestmailboxconnectionsusingamailboxgloballyuniqueidentifier(GUID)plustheuserprincipalname(UPN)suffix,withoutanyincludedreferencetoaMailboxserver'sFullyQualifiedDomainName(FQDN).MailboxesaremuchmoreportablebecausetheClientAccessserveranditsclientsnolongerneedtoknoworcareaboutMailboxservernames.ThecomplexExchange2010systemofinterrelatednamespaces(andcertificatestosecurethem)isgone,replacedwithadramaticallysimplerimplementation.TofacilitatetheuseofOutlookAnywhereinternally,theClientAccessserverrolenowsupportsanewinternalhostname(andmatchingauthenticationmethod),whichwillbeused(ifdefined)forclientsontheLAN.
AnotherpleasantsideeffectofthechangetotheClientAccessserverdesignisthatcrosssiteaccessismuchsimpler.ClientsconnecttowhicheverClientAccessserverisconvenient,andtheClientAccessservercanperformHTTPredirectsasnecessarytofindthecorrectMailboxserveracrossActiveDirectory(AD)sites.
TheservicesthattheClientAccessserverofferstoclientshavechangedquiteabitaswell.OutlookWebApp(OWA)2013iscompletelyrewrittenandincludessomecompellingnewfeatures,suchasgreatlyimprovedsupportformobiledevicessuchasAppleiPads.OWA2013canrunofflineonsupportedbrowserscurrently,GoogleChrome,MicrosoftInternetExplorer(IE)10,andAppleSafari5.x/6.xonMacOSX.
TransportChanges
Thetransportprocesshaschangedsignificantlybecauseofthetworolearchitecture.WhereasExchange2007andExchange2010hadaseparateHubTransportrole,Exchange2013doesnot.TheClientAccessserverrolehoststhenewFrontEndTransportservice,whichhandlesallinboundandoutboundSMTPtraffic.Theservicedoesn'tperformanycontentfiltering,althoughitdoesprovidefilteringbasedonconnection,senderorrecipientidentity,andprotocolbehavior.TheFrontEndTransportservice'sroleisrathertoactasacentralized,loadbalancedingressandexitpointforallSMTPtraffic.BearinmindthattheClientAccessserverisn'tintendedtoreplacetheEdgeTransportrole,sodeployingitinaperimeternetworkisunsupported.
ThenewFrontEndTransportservicehasacompletelynewapproachtomailacceptanceanddelivery:Ithasnopermanentqueues.WhenanewSMTPconversationisopened,theserviceacceptstheconnection,performsfilteringbasedontheSMTPenvelopedata,andthendeterminestheroutetothe"best"Mailboxserverbeforestartingthedeliveryprocess.TheMailboxserverisresponsibleforacceptingandqueuingthemessage.IftheFrontEndTransportservicecannotconnecttoaMailboxserver,oriftheserverdoesn'tacceptthemessage,thentheFrontEndTransportservicereturnsSMTPerror421tothesender,indicatingatransientfailurethatmustberetriedlater.ThisapproachdrasticallysimplifiestheFrontEndTransportserviceatthecostofmovingthequeuing,redundancy,anddeliverylogicovertotheMailboxrole.
TheMailboxserverrunsthreenewtransportrelatedservices:
ThedivisionoflaborbetweentheClientAccessserverandMailboxTransportservice
TheMailboxTransportservicedoesmuchofwhattheformerHubTransportroledid.Theprocessofmailboxtransportisnowstateful,sotheMailboxTransportservicemaintainsstateinformationabouteachmessageasitpassesthroughtheengine.Mailboxtransportperformspolicyenforcement(includingenforcingsizelimits)andprovidesqueuingformessages.ThisistheonlymailboxservicethatcommunicateswithFrontEndTransportservice.
TheMailboxTransportDeliveryserviceacceptsmailfromtheMailboxTransportserviceanddeliversittothemailboxdatabase.
TheMailboxTransportSubmissionserviceretrievesmailfromthemailboxdatabaseandsubmitsittotheMailboxTransportserviceforprocessing.
-
5/23/2015 What'sNewInExchangeServer2013|ExchangeServer2013contentfromWindowsITPro
http://windowsitpro.com/exchangeserver2013/whatsnewexchangeserver2013 5/6
Tweet
deliversessentiallythesamehighavailabilityfortransportaswehadinExchange2010,butit'simplementedverydifferently.TheMailboxTransportservicepersistseverysubmittedmessagebeforethemessageisacknowledgedtothesender.IftheMailboxTransportservicedoesnotorcannotacceptthemessage,thentheFrontEndTransportservicesendsa421errortothesenderandmessagedeliveryisreattemptedlater.Messagesthataresuccessfullysubmittedtothetransportsystemaremaintaineduntiltheirfinaldelivery,andresubmissionofmessagesthatcouldn'tbedeliveredbecauseofthelossofatransportdatabaseormailboxdatabasefailoverandswitchoverisautomatic.ThisnewbehaviorisknownasSafetyNet,andit'scomplexenoughthatitwillprobablybethesubjectoffutureWindowsITProarticlesandExchangeTeamBlogposts.
Interestingly,Microsoftisn'tcurrentlyshippinganEdgeTransportroleinExchange2013andhasn'tpubliclyannouncedwhetherorwhenitwilldoso.RelativelyfewcustomersusetheEdgeTransportrole,soMicrosoftmighthavechosentowaitorevenbaketheEdgefunctionalityintoafutureversionofanEdgenetworkproductsuchasitsUnifiedAccessGateway(UAG)Serverline.
UnifiedMessagingChanges
UnifiedMessaging(UM)isperhapstheareainwhichfunctionalityhaschangedtheleastinExchange2013.TheUnifiedMessagingroleisnowhostedontheMailboxserver.TheClientAccessserverrunstheUnifiedMessagingCallRouterservice,whichacceptsincomingcallsandredirectsthemtotheappropriateMailboxserver.TheMailboxserveritselfisresponsibleforhandlingallinteractionwiththecaller,includingplayingavoicemailgreetingorAutoAttendantmessageandrecordingthecaller'svoicemail.
TheremainingUMchangesareallenhancements.Forexample,theVoiceMailPreviewfeatureismoreaccurate.(AlthoughMicrosoftstilldoesn'tclaimthatitis100percentaccurate,norisitintendedtobe.)UMcannowresolvecontactsagainstallpersonalContactsfoldersinauser'smailbox.Therefore,callerIDresolutionnowworkswithexternalcontactsfromFacebook,LinkedIn,andotheraggregatedsources.LiketheotherExchange2013roles,theUnifiedMessagingrolenowfullysupportsIPv6.Apartfromthat,usersandadministratorswillprobablynotnoticeanymajordifferencesinhowUMbehaves.AdministratorswillnotetheadditionofafewnewExchangeManagementShellcmdletsformanagingtheUMservicesandcallroutersettings.
AWarning
OnemajorissuedoesfacesitesthatwanttodeployExchange2013:ItcannotyetcoexistwithExchange2010onpremises.Exchange2010coexistencerequiresExchange2010SP3,whichMicrosofthasannouncedbutnotreleasedasofthiswriting.GiventhetroubleswithExchange2010rollupsduring2012,anyprospectivedeploymentofExchange2010SP3shouldbeapproachedcarefullyandwithathoroughtestingplan.ThenecessarychangestosupportcoexistencearealreadydeployedonExchangeOnline,soifyou'rewillingtomoveyourmailboxestoMicrosoftOffice365,youcandeployExchange2013withoutfurtherdelay.Thisdelayisn'tallbad,though,becauseitgivesyoutheopportunitytotestExchange2013inalabenvironmentandgetabettersenseofitsnewfeaturesandbehaviors.ItwillcertainlybeinterestingtoseehowcustomersadoptExchange2013andhowMicrosoftupdatesitsproductguidanceanddocumentationtoreflectthelessonslearnedfromthatadoption.
PleaseLogInorRegistertopostcomments.
Related Articles
What'sNewInExchangeServer2013
WhatsNewinExchange2013ArchivingandeDiscovery
WhatsNewinExchange2013ArchivingandeDiscovery
SHARE 0Recommend
-
5/23/2015 What'sNewInExchangeServer2013|ExchangeServer2013contentfromWindowsITPro
http://windowsitpro.com/exchangeserver2013/whatsnewexchangeserver2013 6/6
Site FeaturesContactUs
Awards
CommunitySponsors
MediaCenter
RSS
Sitemap
SiteArchive
ViewMobileSite
PentonPrivacyPolicy
TermsofService
Advertise
Follow Us
Search WindowsITPro.com
DevPro SharePointPro SQLServerPro SuperSiteforWindows IT/DevConnections myITforum
Copyright2015Penton
WindowsITPro.com
Windows ExchangeServer SharePoint Virtualization Cloud SystemsManagement
Related Sites
MicrosoftOfficeFilterPack2013nowavailable,butit'snotneededbyExchange2013
Office365forBusiness:WhattoExpectfor2013