Home
%3CLINGO-SUB%20id%3D%22lingo-sub-605402%22%20slang%3D%22en-US%22%3EReleased%3A%20September%202016%20Quarterly%20Exchange%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-605402%22%20slang%3D%22en-US%22%3E%3CP%3EToday%20we%20are%20announcing%20the%20latest%20set%20of%20Cumulative%20Updates%20for%20Exchange%20Server%202016%20and%20Exchange%20Server%202013.%20These%20releases%20include%20fixes%20to%20customer%20reported%20issues%20and%20updated%20functionality.%20%3CA%20href%3D%22http%3A%2F%2Fwww.microsoft.com%2Fdownloads%2Fdetails.aspx%3FFamilyID%3Dfe1096f8-6143-4a77-8307-38894dac3187%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3EExchange%20Server%202016%20Cumulative%20Update%203%3C%2FA%3E%20and%20%3CA%20href%3D%22http%3A%2F%2Fwww.microsoft.com%2Fdownloads%2Fdetails.aspx%3FFamilyID%3D0429fd4f-190d-406b-8613-8794d4fd2589%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3EExchange%20Server%202013%20Cumulative%20Update%2014%3C%2FA%3E%20are%20available%20on%20the%20Microsoft%20Download%20Center.%3C%2FP%3E%3CH3%20id%3D%22toc-hId-1562763065%22%20id%3D%22toc-hId-1563569562%22%3EWindows%20Server%202016%20Support%3C%2FH3%3EWindows%20Server%202016%20support%20is%20now%20available%20with%20Exchange%20Server%202016%20Cumulative%20Update%203.%20Customers%20looking%20to%20deploy%20Windows%20Server%202016%20in%20their%20Exchange%20environments%20require%20Exchange%20Server%202016%20Cumulative%20Update%203%20or%20later.%20Domain%20Controllers%20running%20Windows%20Server%202016%20are%20supported%20provided%20Forest%20Functional%20Level%20is%20Windows%20Server%202008R2%20or%20later%20(Edit%2010%2F27%2F2016%3A%20Please%20see%20%3CA%20href%3D%22https%3A%2F%2Fblogs.technet.microsoft.com%2Fexchange%2F2016%2F10%2F27%2Factive-directory-forest-functional-levels-for-exchange-server-2016%2F%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3Ethis%20blog%20post%3C%2FA%3E%20for%20more%20information%20related%20to%20Forest%20Functional%20Level).%20Exchange%20does%20not%20currently%20support%20any%20new%20functionality%20provided%20by%20the%20updated%20operating%20system%20except%20for%20improved%20restart%20support%20in%20the%20Windows%20Installer.%20Installing%20Exchange%20on%20Windows%20Server%202016%20provides%20a%20seamless%20installation%20experience%20including%20prerequisites.%20Exchange%20Server%202013%20will%20not%20be%20supported%20on%20Windows%20Server%202016.%20Windows%20Defender%20is%20on%20by%20default%20in%20Windows%20Server%202016.%20Attention%20to%20malware%20settings%20is%20particularly%20important%20with%20Exchange%20to%20avoid%20long%20processing%20times%20during%20installation%20and%20upgrade%2C%20as%20well%20as%20unexpected%20performance%20issues.%20The%20Exchange%20team%20recommends%20the%20Exchange%20installation%20and%20setup%20log%20folders%20be%20excluded%20from%20scanning%20in%20Windows%20Defender%20and%20other%20Anti-Virus%20software.%20Exchange%20noderunner%20processes%20should%20also%20be%20excluded%20from%20Windows%20Defender.%3CH3%20id%3D%22toc-hId--989393896%22%20id%3D%22toc-hId--988587399%22%3E.Net%204.6.2%20Support%3C%2FH3%3E.Net%204.6.2%20is%20included%20with%20Windows%20Server%202016.%20Customers%20deploying%20Exchange%20on%20Windows%20Server%202016%20must%20use%20.Net%204.6.2%20and%20Cumulative%20Update%203%20or%20later.%20We%20plan%20to%20add%20support%20for%20.Net%204.6.2%20on%20Windows%20Server%202012%20or%20Windows%20Server%202012R2%20in%20our%20December%20releases%20of%20Exchange%20Server%202016%20and%202013.%20.Net%204.6.2%20will%20be%20required%20for%20Exchange%20Server%202016%20and%202013%20on%20all%20supported%20operating%20systems%20in%20March%202017.%20We%20advise%20customers%20to%20start%20evaluating%20requirements%20to%20move%20to%20.Net%204.6.2%20now.%3CH3%20id%3D%22toc-hId-753416439%22%20id%3D%22toc-hId-754222936%22%3EHigh%20Availability%20Improvements%3C%2FH3%3EOne%20of%20the%20challenging%20areas%20in%20some%20on-premises%20environment%20is%20the%20amount%20of%20data%20replicated%20with%20each%20database%20copy.%20In%20Exchange%20Server%202016%20Cumulative%20Update%203%2C%20network%20bandwidth%20requirements%20between%20the%20active%20copy%20and%20passive%20HA%20copies%20are%20reduced.%20The%20%3CA%20href%3D%22https%3A%2F%2Faka.ms%2Fe2013calc%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3EExchange%20Server%20Role%20Requirements%20Calculator%3C%2FA%3E%20has%20been%20updated%20to%20reflect%20these%20improvements.%20The%20local%20search%20instance%20reads%20data%20from%20a%20database%20copy%20on%20the%20local%20server%2C%20also%20known%20as%20%E2%80%9CRead%20from%20Passive%E2%80%9D.%20As%20a%20result%20of%20this%20change%2C%20passive%20HA%20copy%20search%20instances%20no%20longer%20need%20to%20coordinate%20with%20their%20active%20counterparts%20in%20order%20to%20perform%20index%20updates.%20Lagged%20database%20copies%20still%20coordinate%20with%20their%20active%20counterparts%20to%20perform%20index%20updates.%20This%20change%20also%20reduces%20database%20failover%20times%20when%20compared%20to%20Exchange%20Server%202013.%3CH3%20id%3D%22toc-hId--1798740522%22%20id%3D%22toc-hId--1797934025%22%3EInstalling%20from%20a%20Mounted%20.ISO%20using%20Local%20Languages%3C%2FH3%3E.ISO%E2%80%99s%20mounted%20on%20localized%20versions%20of%20the%20operating%20system%20function%20correctly%20with%20Cumulative%20Update%203.%20Support%20for%20local%20language%20setup%20experience%20is%20limited%20to%20the%2011%20server%20languages%20supported%20by%20Exchange%20Server%202016.%3CH3%20id%3D%22toc-hId--55930187%22%20id%3D%22toc-hId--55123690%22%3EPre-Requisite%20Installation%20Behavior%20Updated%3C%2FH3%3EIn%20previous%20releases%20of%20Exchange%20Server%202016%20and%202013%2C%20servers%20were%20placed%20into%20server-wide%20off-line%20monitoring%20states%20during%20pre-requisite%20analysis%20and%20pre-requisite%20installation.%20This%20behavior%20is%20changed%20in%20the%20September%20cumulative%20update%20releases.%20Setup%20will%20now%20place%20a%20server%20in%20off-line%20monitoring%20mode%20when%20installation%20of%20new%20Exchange%20binaries%20begins.%20This%20change%20allows%20customers%20who%20are%20using%20the%20GUI%20upgrade%20experience%20to%20delay%20changing%20the%20monitoring%20state%20until%20after%20pre-requisite%20analysis%20confirms%20the%20server%20is%20ready%20for%20installation.%20The%20monitoring%20state%20will%20be%20configured%20when%20the%20user%20selects%20to%20proceed%20to%20the%20binary%20installation%20step.%20For%20customers%20using%20command%20line%20setup%2C%20placing%20the%20server%20into%20the%20off-line%20monitoring%20state%20is%20also%20delayed%20until%20pre-requisite%20analysis%20is%20completed%20and%20all%20pre-requisites%20are%20met.%20Once%20pre-requisites%20are%20confirmed%2C%20command%20line%20setup%20will%20change%20the%20monitoring%20status%20and%20proceed%20without%20a%20delay%20into%20the%20actual%20binary%20upgrade%20process.%3CH3%20id%3D%22toc-hId-1686880148%22%20id%3D%22toc-hId-1687686645%22%3ELatest%20Time%20Zone%20and%20Security%20Updates%3C%2FH3%3EExchange%20Server%202016%20Cumulative%20Update%203%20and%20Exchange%20Server%202013%20Cumulative%20Update%2014%20include%20the%20security%20updates%20released%20in%20MS16-108.%20All%20of%20the%20September%20Exchange%20releases%20include%20support%20for%20Time%20Zone%20updates%20released%20through%20the%20month%20of%20August.%20Update%20Rollup%2021%20for%20Exchange%20Server%202007%20and%20Update%20Rollup%2015%20for%20Exchange%20Server%202010%2C%20part%20of%20our%20September%20releases%2C%20were%20released%20as%20security%20bulletin%20MS16-108.%3CH3%20id%3D%22toc-hId--865276813%22%20id%3D%22toc-hId--864470316%22%3ERefreshed%20People%20Experience%20in%20Outlook%20on%20the%20web%3C%2FH3%3EExchange%20Server%202016%20Cumulative%20Update%203%20includes%20an%20updated%20view%20of%20Contact%20information%20and%20Skype%20for%20Business%20presence%20information.%20These%20changes%20mirror%20the%20current%20experience%20of%20Office365.%3CH3%20id%3D%22toc-hId-877533522%22%20id%3D%22toc-hId-878340019%22%3ECountdown%20to%20Exchange%20Server%202007%20End%20of%20Life%20(EOL)%3C%2FH3%3EWe%20are%20now%20only%20seven%20months%20away%20from%20Exchange%20Server%202007%20going%20out%20of%20support%20(%3CA%20href%3D%22https%3A%2F%2Fblogs.technet.microsoft.com%2Fexchange%2F2016%2F04%2F11%2Fexchange-server-2007-t-1-year-and-counting%2F%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3EExchange%20Server%202007%20T-1%20year%20and%20counting%3C%2FA%3E).%20Customers%20still%20running%20Exchange%20Server%202007%20should%20be%20implementing%20plans%20to%20move%20to%20Exchange%20Server%202013%20or%20Office%20365%20to%20ensure%20uninterrupted%20access%20to%20support%20and%20product%20fixes.%3CH3%20id%3D%22toc-hId--1674623439%22%20id%3D%22toc-hId--1673816942%22%3ERelease%20Details%3C%2FH3%3EKB%20articles%20which%20contain%20greater%20depth%20on%20what%20each%20release%20includes%20are%20available%20as%20follows%3A%3CUL%3E%0A%20%20%3CLI%3EExchange%20Server%202016%20Cumulative%20Update%203%20(%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2FKB%2F3152589%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3EKB3152589%3C%2FA%3E)%2C%20%3CA%20href%3D%22http%3A%2F%2Fwww.microsoft.com%2Fdownloads%2Fdetails.aspx%3FFamilyID%3Dfe1096f8-6143-4a77-8307-38894dac3187%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3EDownload%3C%2FA%3E%2C%20%3CA%20href%3D%22http%3A%2F%2Fwww.microsoft.com%2Fdownloads%2Fdetails.aspx%3FFamilyID%3D0a585913-91a5-41b4-9f3d-70bee8f9d5c1%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3EUM%20Lang%20Packs%3C%2FA%3E%3C%2FLI%3E%0A%20%20%3CLI%3EExchange%20Server%202013%20Cumulative%20Update%2014%20(%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2FKB%2F3177670%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3EKB3177670%3C%2FA%3E)%2C%20%3CA%20href%3D%22http%3A%2F%2Fwww.microsoft.com%2Fdownloads%2Fdetails.aspx%3FFamilyID%3D0429fd4f-190d-406b-8613-8794d4fd2589%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3EDownload%3C%2FA%3E%2C%20%3CA%20href%3D%22http%3A%2F%2Fwww.microsoft.com%2Fdownloads%2Fdetails.aspx%3FFamilyID%3D97836917-92c2-4f83-8189-2e1ada1a4f52%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3EUM%20Lang%20Packs%3C%2FA%3E%3C%2FLI%3E%0A%3C%2FUL%3EExchange%20Server%202016%20Cumulative%20Update%203%20%3CU%3Edoes%3C%2FU%3E%20include%20updates%20to%20Active%20Directory%20Schema.%20These%20updates%20will%20apply%20automatically%20during%20setup%20if%20the%20permissions%20and%20AD%20requirements%20are%20met%20during%20installation.%20If%20the%20Exchange%20Administrator%20lacks%20permissions%20to%20update%20Active%20Directory%20Schema%2C%20a%20Schema%20Admin%20needs%20to%20execute%20SETUP%20%2FPrepareSchema%20before%20installing%20Cumulative%20Update%203%20on%20the%20first%20Exchange%20server.%20The%20Exchange%20Administrator%20should%20also%20execute%20SETUP%20%2FPrepareAD%20to%20ensure%20RBAC%20roles%20are%20updated%20correctly.%20Exchange%20Server%202013%20Cumulative%20Update%2014%20%3CU%3Edoes%20not%3C%2FU%3E%20include%20updates%20to%20Active%20Directory%2C%20but%20may%20add%20additional%20RBAC%20definitions%20to%20your%20existing%20configuration.%20PrepareAD%20should%20be%20executed%20prior%20to%20upgrading%20any%20servers%20to%20Cumulative%20Update%2014.%20PrepareAD%20will%20run%20automatically%20during%20the%20first%20server%20upgrade%20if%20Setup%20detects%20this%20is%20required%20and%20the%20logged%20on%20user%20has%20sufficient%20permission.%3CH3%20id%3D%22toc-hId-68186896%22%20id%3D%22toc-hId-68993393%22%3EAdditional%20Information%3C%2FH3%3EMicrosoft%20recommends%20all%20customers%20test%20the%20deployment%20of%20any%20update%20in%20their%20lab%20environment%20to%20determine%20the%20proper%20installation%20process%20for%20your%20production%20environment.%20For%20information%20on%20extending%20the%20schema%20and%20configuring%20Active%20Directory%2C%20please%20review%20the%20appropriate%20%3CA%20href%3D%22http%3A%2F%2Ftechnet.microsoft.com%2Flibrary%2Fbb125224(v%3Dexchg.150).aspx%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3ETechNet%3C%2FA%3E%20documentation.%20Also%2C%20to%20prevent%20installation%20issues%20you%20should%20ensure%20that%20the%20Windows%20PowerShell%20Script%20Execution%20Policy%20is%20set%20to%20%E2%80%9CUnrestricted%E2%80%9D%20on%20the%20server%20being%20upgraded%20or%20installed.%20To%20verify%20the%20policy%20settings%2C%20run%20the%20Get-ExecutionPolicy%20cmdlet%20from%20PowerShell%20on%20the%20machine%20being%20upgraded.%20If%20the%20policies%20are%20NOT%20set%20to%20Unrestricted%20you%20should%20use%20the%20resolution%20steps%20in%20%3CA%20href%3D%22http%3A%2F%2Fsupport.microsoft.com%2Fkb%2F981474%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3EKB981474%3C%2FA%3E%20to%20adjust%20the%20settings.%20%3CB%3EReminder%3A%20%3C%2FB%3ECustomers%20in%20hybrid%20deployments%20where%20Exchange%20is%20deployed%20on-premises%20and%20in%20the%20cloud%2C%20or%20who%20are%20using%20Exchange%20Online%20Archiving%20(EOA)%20with%20their%20on-premises%20Exchange%20deployment%20are%20required%20to%20deploy%20the%20most%20current%20(e.g.%2C%202013%20CU14%2C%202016%20CU3)%20or%20the%20prior%20(e.g.%2C%202013%20CU13%2C%202016%20CU2)%20Cumulative%20Update%20release.%20For%20the%20latest%20information%20on%20Exchange%20Server%20and%20product%20announcements%20please%20see%20%3CA%20href%3D%22https%3A%2F%2Ftechnet.microsoft.com%2Flibrary%2Fjj150540(v%3Dexchg.160).aspx%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3EWhat's%20New%20in%20Exchange%20Server%202016%3C%2FA%3E%20and%20%3CA%20href%3D%22https%3A%2F%2Ftechnet.microsoft.com%2Flibrary%2Fjj150489(v%3Dexchg.160).aspx%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3EExchange%20Server%202016%20Release%20Notes%3C%2FA%3E.%20You%20can%20also%20find%20updated%20information%20on%20Exchange%20Server%202013%20in%20%3CA%20href%3D%22http%3A%2F%2Ftechnet.microsoft.com%2Flibrary%2Fjj150540(v%3Dexchg.150).aspx%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3EWhat%E2%80%99s%20New%20in%20Exchange%20Server%202013%3C%2FA%3E%2C%20%3CA%20href%3D%22http%3A%2F%2Ftechnet.microsoft.com%2Flibrary%2Fjj150489(v%3Dexchg.150).aspx%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3ERelease%20Notes%3C%2FA%3E%20and%20product%20documentation%20available%20on%20TechNet.%3CP%20class%3D%22note%22%3ENote%3A%20Documentation%20may%20not%20be%20fully%20available%20at%20the%20time%20this%20post%20was%20published.%3C%2FP%3E%3CSPAN%20class%3D%22author%22%3EThe%20Exchange%20Team%3C%2FSPAN%3E%3C%2FLINGO-BODY%3E

Today we are announcing the latest set of Cumulative Updates for Exchange Server 2016 and Exchange Server 2013. These releases include fixes to customer reported issues and updated functionality. Exchange Server 2016 Cumulative Update 3 and Exchange Server 2013 Cumulative Update 14 are available on the Microsoft Download Center.

Windows Server 2016 Support

Windows Server 2016 support is now available with Exchange Server 2016 Cumulative Update 3. Customers looking to deploy Windows Server 2016 in their Exchange environments require Exchange Server 2016 Cumulative Update 3 or later. Domain Controllers running Windows Server 2016 are supported provided Forest Functional Level is Windows Server 2008R2 or later (Edit 10/27/2016: Please see this blog post for more information related to Forest Functional Level). Exchange does not currently support any new functionality provided by the updated operating system except for improved restart support in the Windows Installer. Installing Exchange on Windows Server 2016 provides a seamless installation experience including prerequisites. Exchange Server 2013 will not be supported on Windows Server 2016. Windows Defender is on by default in Windows Server 2016. Attention to malware settings is particularly important with Exchange to avoid long processing times during installation and upgrade, as well as unexpected performance issues. The Exchange team recommends the Exchange installation and setup log folders be excluded from scanning in Windows Defender and other Anti-Virus software. Exchange noderunner processes should also be excluded from Windows Defender.

.Net 4.6.2 Support

.Net 4.6.2 is included with Windows Server 2016. Customers deploying Exchange on Windows Server 2016 must use .Net 4.6.2 and Cumulative Update 3 or later. We plan to add support for .Net 4.6.2 on Windows Server 2012 or Windows Server 2012R2 in our December releases of Exchange Server 2016 and 2013. .Net 4.6.2 will be required for Exchange Server 2016 and 2013 on all supported operating systems in March 2017. We advise customers to start evaluating requirements to move to .Net 4.6.2 now.

High Availability Improvements

One of the challenging areas in some on-premises environment is the amount of data replicated with each database copy. In Exchange Server 2016 Cumulative Update 3, network bandwidth requirements between the active copy and passive HA copies are reduced. The Exchange Server Role Requirements Calculator has been updated to reflect these improvements. The local search instance reads data from a database copy on the local server, also known as “Read from Passive”. As a result of this change, passive HA copy search instances no longer need to coordinate with their active counterparts in order to perform index updates. Lagged database copies still coordinate with their active counterparts to perform index updates. This change also reduces database failover times when compared to Exchange Server 2013.

Installing from a Mounted .ISO using Local Languages

.ISO’s mounted on localized versions of the operating system function correctly with Cumulative Update 3. Support for local language setup experience is limited to the 11 server languages supported by Exchange Server 2016.

Pre-Requisite Installation Behavior Updated

In previous releases of Exchange Server 2016 and 2013, servers were placed into server-wide off-line monitoring states during pre-requisite analysis and pre-requisite installation. This behavior is changed in the September cumulative update releases. Setup will now place a server in off-line monitoring mode when installation of new Exchange binaries begins. This change allows customers who are using the GUI upgrade experience to delay changing the monitoring state until after pre-requisite analysis confirms the server is ready for installation. The monitoring state will be configured when the user selects to proceed to the binary installation step. For customers using command line setup, placing the server into the off-line monitoring state is also delayed until pre-requisite analysis is completed and all pre-requisites are met. Once pre-requisites are confirmed, command line setup will change the monitoring status and proceed without a delay into the actual binary upgrade process.

Latest Time Zone and Security Updates

Exchange Server 2016 Cumulative Update 3 and Exchange Server 2013 Cumulative Update 14 include the security updates released in MS16-108. All of the September Exchange releases include support for Time Zone updates released through the month of August. Update Rollup 21 for Exchange Server 2007 and Update Rollup 15 for Exchange Server 2010, part of our September releases, were released as security bulletin MS16-108.

Refreshed People Experience in Outlook on the web

Exchange Server 2016 Cumulative Update 3 includes an updated view of Contact information and Skype for Business presence information. These changes mirror the current experience of Office365.

Countdown to Exchange Server 2007 End of Life (EOL)

We are now only seven months away from Exchange Server 2007 going out of support (Exchange Server 2007 T-1 year and counting). Customers still running Exchange Server 2007 should be implementing plans to move to Exchange Server 2013 or Office 365 to ensure uninterrupted access to support and product fixes.

Release Details

KB articles which contain greater depth on what each release includes are available as follows: Exchange Server 2016 Cumulative Update 3 does include updates to Active Directory Schema. These updates will apply automatically during setup if the permissions and AD requirements are met during installation. If the Exchange Administrator lacks permissions to update Active Directory Schema, a Schema Admin needs to execute SETUP /PrepareSchema before installing Cumulative Update 3 on the first Exchange server. The Exchange Administrator should also execute SETUP /PrepareAD to ensure RBAC roles are updated correctly. Exchange Server 2013 Cumulative Update 14 does not include updates to Active Directory, but may add additional RBAC definitions to your existing configuration. PrepareAD should be executed prior to upgrading any servers to Cumulative Update 14. PrepareAD will run automatically during the first server upgrade if Setup detects this is required and the logged on user has sufficient permission.

Additional Information

Microsoft recommends all customers test the deployment of any update in their lab environment to determine the proper installation process for your production environment. For information on extending the schema and configuring Active Directory, please review the appropriate TechNet documentation. Also, to prevent installation issues you should ensure that the Windows PowerShell Script Execution Policy is set to “Unrestricted” on the server being upgraded or installed. To verify the policy settings, run the Get-ExecutionPolicy cmdlet from PowerShell on the machine being upgraded. If the policies are NOT set to Unrestricted you should use the resolution steps in KB981474 to adjust the settings. Reminder: Customers in hybrid deployments where Exchange is deployed on-premises and in the cloud, or who are using Exchange Online Archiving (EOA) with their on-premises Exchange deployment are required to deploy the most current (e.g., 2013 CU14, 2016 CU3) or the prior (e.g., 2013 CU13, 2016 CU2) Cumulative Update release. For the latest information on Exchange Server and product announcements please see What's New in Exchange Server 2016 and Exchange Server 2016 Release Notes. You can also find updated information on Exchange Server 2013 in What’s New in Exchange Server 2013, Release Notes and product documentation available on TechNet.

Note: Documentation may not be fully available at the time this post was published.

The Exchange Team
85 Comments
Not applicable
I also wanted to ask could this possibly be caused by the health mailboxes being in the database that is part of the dag? i was thinking maybe i should create a local MB database that does not participate in the DAG and have all of the health/audit/sys mailboxes stay on the host. I thought perhaps the server couldnt bring itself back up because it didnt have access to those mailbox dbs at a time of failure..I looked online and it seems having those mailboxes as part of a DAG is generally ok though.
Not applicable
Hello Microsoft,

What is the procedure to block the installation of .NET 4.6.2 on Windows Server 2012 or Windows Server 2012 R2 until the December Exchange rollups are available?

Not applicable
@sime3000 - We are not publishing steps to block this. The .Net team has informed us that .Net 4.6.2 will not be offered as a mandatory package through Microsoft Update until after the end of the year at the earliest. The Exchange team has already been validating to ensure we have compatibility before this package is forced onto Exchange servers. Customers wishing to run on Windows Server 2016 already require .Net 4.6.2.

Customers who are concerned about this transition always have the option to configure Windows Update to review updates before they are installed. We will still have a hard requirement for this for all Exchange 2013 and 2016 servers with our March '17 releases.

Not applicable
There is a german HowTo for installing Exchange 2016 CU3 on Windows Server 2016. There is also a PowerShell script for automatic Windows Defenter exclusions:

https://www.frankysweb.de/howto-installation-exchange-2016-auf-windows-server-2016/

regards, Frank

Not applicable
Hello,

Does anyone know what means the attribute "OWAVersion" of the OWA Virtual Directory? Exchange 2016 CU3 is still has "Exchange2013".

[PS] C:\Windows\system32>Get-ExchangeServer | fl AdminDisplayVersion

AdminDisplayVersion : Version 15.1 (Build 544.27)

[PS] C:\Windows\system32>Get-OwaVirtualDirectory | fl OWAVersion

OwaVersion : Exchange2013

Not applicable
Did the "Other" Section in OWA under Options get removed with this update? If so where are those settings now located?
Not applicable
Same issue here. Can't find 'other' section in OWA settings. We needed that for access to group management interface. Or at least we thought we needed it. Am I missing something? How should users manage the groups they own now? Go directly to /ecp is the only thing that occurs to me.
Not applicable
Same here. I just noticed after a users called that this was missing. does any one know if this is something that can easily be but back prior to CU4?
Not applicable
Hello Exchange Team,

Its been thirteen weeks since I posted this question and I’m just wondering if I will need to wait two years for an answer as I did with a previous question. I guess you folks must be really busy!

In case you missed it my question was … Why are some redirection functions apparently not working in the Exchange Management shell in both Exchange 2016 and Exchange 2013? e.g. if you run “Get-MailPublicFolder 3> output.txt” to redirect warning messages to a text file, any warning messages will be visible on the screen but the output file will be empty. I've seen others reporting this in various forums but no resolution.

Looking forward to a timely response from Microsoft.

Thanks

Not applicable
Hello Exchange Team,

Its been fourteen weeks since I posted this question and I’m just wondering if I will need to wait two years for an answer as I did with a previous question. I guess you folks must be really busy!

In case you missed it my question was … Why are some redirection functions apparently not working in the Exchange Management shell in both Exchange 2016 and Exchange 2013? e.g. if you run “Get-MailPublicFolder 3> output.txt” to redirect warning messages to a text file, any warning messages will be visible on the screen but the output file will be empty. I’ve seen others reporting this in various forums but no resolution.

Looking forward to a timely response from Microsoft.

Thanks!

Not applicable
Hello Exchange Team,

Its been *fifteen* weeks since I posted this question and I’m just wondering if I will need to wait two years for an answer as I did with a previous question. I guess you folks must be really busy!

In case you missed it my question was … Why are some redirection functions apparently not working in the Exchange Management shell in both Exchange 2016 and Exchange 2013 regardless of rollup level or other factors? e.g. if you run “Get-MailPublicFolder 3> output.txt” to redirect warning messages to a text file, any warning messages will be visible on the screen but the output file will be empty. I’ve seen others reporting this problem in various forums but no acknowledgement of the problem and no resolution from Microsoft.

Looking forward to a timely response from Microsoft.

Thanks a lot !

Not applicable
Hello Exchange Team,

Its been *sixteen* weeks since I posted this question and I’m just wondering if I will need to wait two years for an answer as I did with a previous question. I guess you folks must be really busy!

In case you missed it my question was … Why are some redirection functions apparently not working in the Exchange Management shell in both Exchange 2016 and Exchange 2013 regardless of rollup level or other factors? e.g. if you run “Get-MailPublicFolder 3> output.txt” to redirect warning messages to a text file, any warning messages will be visible on the screen but the output file will be empty. I’ve seen others reporting this problem in various forums but no acknowledgement of the problem and no resolution from Microsoft.

Looking forward to a timely response from Microsoft.

Thanks a lot !

Not applicable
Hello Exchange Team,

Its been *seventeen* weeks since I posted this question and I’m just wondering if I will need to wait two years for an answer as I did with a previous question. I guess you folks must be really busy!

In case you missed it my question was … Why are some redirection functions apparently not working in the Exchange Management shell in both Exchange 2016 and Exchange 2013 regardless of rollup level or other factors? e.g. if you run “Get-MailPublicFolder 3> output.txt” to redirect warning messages to a text file, any warning messages will be visible on the screen but the output file will be empty. I’ve seen others reporting this problem in various forums but no acknowledgement of the problem and no resolution from Microsoft.

Looking forward to a timely response from Microsoft.

Thanks a lot !

Not applicable
Hello Exchange Team,

Its been *nineteen* weeks since I posted this question and I’m just wondering if I will need to wait two years for an answer as I did with a previous question. I guess you folks must be really busy!

In case you missed it my question was … Why are some redirection functions apparently not working in the Exchange Management shell in both Exchange 2016 and Exchange 2013 regardless of rollup level or other factors? e.g. if you run “Get-MailPublicFolder 3> output.txt” to redirect warning messages to a text file, any warning messages will be visible on the screen but the output file will be empty. I’ve seen others reporting this problem in various forums but no acknowledgement of the problem and no resolution from Microsoft.

Looking forward to a timely response from Microsoft.

Thanks a lot !

Not applicable
Hello Exchange Team,

Its been *twenty-one* weeks since I posted this question and I’m just wondering if I will need to wait two years for an answer as I did with a previous question. I guess you folks must be really busy!

In case you missed it my question was … Why are some redirection functions apparently not working in the Exchange Management shell in both Exchange 2016 and Exchange 2013 regardless of rollup level or other factors? e.g. if you run “Get-MailPublicFolder 3> output.txt” to redirect warning messages to a text file, any warning messages will be visible on the screen but the output file will be empty. I’ve seen others reporting this problem in various forums but no acknowledgement of the problem and no resolution from Microsoft.

Looking forward to a timely response from Microsoft.

Thanks a lot !

Not applicable
Hello Exchange Team,

Its been *twenty* weeks since I posted this question and I’m just wondering if I will need to wait two years for an answer as I did with a previous question. I guess you folks must be really busy!

In case you missed it my question was … Why are some redirection functions apparently not working in the Exchange Management shell in both Exchange 2016 and Exchange 2013 regardless of rollup level or other factors? e.g. if you run “Get-MailPublicFolder 3> output.txt” to redirect warning messages to a text file, any warning messages will be visible on the screen but the output file will be empty. I’ve seen others reporting this problem in various forums but no acknowledgement of the problem and no resolution from Microsoft.

Looking forward to a timely response from Microsoft.

Thanks a lot !

Not applicable
Hello Exchange Team,

Its been *eighteen* weeks since I posted this question and I’m just wondering if I will need to wait two years for an answer as I did with a previous question. I guess you folks must be really busy!

In case you missed it my question was … Why are some redirection functions apparently not working in the Exchange Management shell in both Exchange 2016 and Exchange 2013 regardless of rollup level or other factors? e.g. if you run “Get-MailPublicFolder 3> output.txt” to redirect warning messages to a text file, any warning messages will be visible on the screen but the output file will be empty. I’ve seen others reporting this problem in various forums but no acknowledgement of the problem and no resolution from Microsoft.

Looking forward to a timely response from Microsoft.

Thanks a lot !

Not applicable
Hello Exchange Team,

Its been *twenty-two* weeks since I posted this question and I’m just wondering if I will need to wait two years for an answer as I did with a previous question. I guess you folks must be really busy!

In case you missed it my question was … Why are some redirection functions apparently not working in the Exchange Management shell in both Exchange 2016 and Exchange 2013 regardless of rollup level or other factors? e.g. if you run “Get-MailPublicFolder 3> output.txt” to redirect warning messages to a text file, any warning messages will be visible on the screen but the output file will be empty. I’ve seen others reporting this problem in various forums but no acknowledgement of the problem and no resolution from Microsoft.

Looking forward to a timely response from Microsoft.

Thanks a lot !

Not applicable
Exchange 2016 Setup /PrepareSchema von CU 2 auf CU 3:

Process C:\Windows\system32\ldifde.exe finished with exit code 8224.

[ERROR] There was an error while running 'ldifde.exe' to import the schema file 'C:\Windows\Temp\ExchangeSetup\Setup\Data\PostExchange2003_schema78.ldf'.

ldifde.log:

26: CN=ms-Exch-Country-List,CN=Schema,CN=Configuration,DC=demo4,DC=biz

Entry DN: CN=ms-Exch-Country-List,CN=Schema,CN=Configuration,DC=demo4,DC=biz

Der Eintrag wurde einwandfrei geändert.

27: (null)

Entry DN: (null)

Fehler für Eintrag mit Beginn in Zeile 310: Fehler beim Vorgang

26 Einträge wurden erfolgreich geändert.

26 entries were applied correctly. Entry 27 has an error in line 310:

dn:

changetype: ntdsSchemaModify

replace: schemaUpdateNow

schemaUpdateNow: 1

-

Any ideas?

Not applicable
Hi Team,

I was exploring the ExchangeSetup.log file to find out why a particular server was taking a long time to be fully installed. I ended finding that the setup desperately tries to start and wait for the NaSvc service... 36 times with a timeout of 25 seconds. So in the end, 15 minutes wasted until moving forward.

NaSvc is the Network Connectivity Assistant, and can't be started manually (despite having a startup type of Manual). So, is the wait worth it ?

Here's an example:

[10-16-2016 21:29:51.0289] [2] Will wait '25000' milliseconds for the service 'NcaSvc' to reach status 'Running'.

[10-16-2016 21:30:16.0452] [2] Service 'NcaSvc' failed to reach status 'Running' on this server after waiting for '25000' milliseconds.

[10-16-2016 21:30:16.0452] [2] [WARNING] Service checkpoint has not progressed. Previous checkpoint='0'- Current checkpoint='0'.

(that, multiple times, e.g. a total of 36 times.

[10-16-2016 21:44:58.0609] [2] Service 'NcaSvc' failed to reach status 'Running' on this server after waiting for '25000' milliseconds.

[10-16-2016 21:44:58.0609] [2] [WARNING] Service 'NcaSvc' failed to reach status 'Running' on this server.

[10-16-2016 21:44:58.0609] [2] Ending processing start-setupservice

Not applicable
Sorry, typo on the service's name it's NcaSvc, not NaSvc.

And issue seems to happen with Exchange Server 2016 on Windows Server 2016. Didn't find the same traces with Exchange Server 2016 on Windows Server 2012 R2.

Not applicable
Seeing the same thing here on CU4 w/ Server 2016. After 15 minutes of checking it moved on.
Not applicable
After upgrading Exchange 2016 to CU3 users complain that search in Public Folders doesn't work. Advanced Search works as usual and a little bit faster but it is not comfortable for often use.
Not applicable
Yesterday I had conversation with MS support and engineer said that this is known issue with Exchange 2016 CU3 and they are working to fix that problem ASAP because there are too much complains regarding search in public folders.
Not applicable
Hi Oleg,

we do see the same issue. Our Premier Support case number is: 116102914867996. Can you share your number so that the engineers can work together - thanks!

Not applicable
Thank you for posting this. We are experiencing this problem as well. It took a few weeks before anyone noticed because the search will find items right up to the date the CU3 was installed. Please keep us informed, and perhaps a link to the fix once MS posts it.
Not applicable
The same problem in 2013 CU14
Not applicable
UCMA 4.0 is listed as a prerequisite for Exchange 2016 on Windows 2016 https://technet.microsoft.com/en-us/library/bb691354(v=exchg.160).aspx

However UCMA 4.0 was released four years ago and is clearly not supported on Windows 2016 according to the UCMA 4.0 requirements on this page https://www.microsoft.com/en-us/download/details.aspx?id=34992

So how is UCMA 4.0 a supported prerequisite for Exchange 2016 on Windows 2016 ?

Looking forward to your timely response.

Not applicable
UCMA 4.0 is listed as a prerequisite for Exchange 2016 on Windows 2016 https://technet.microsoft.com/en-us/library/bb691354(v=exchg.160).aspx

However UCMA 4.0 was released four years ago and is clearly not supported on Windows 2016 according to the UCMA 4.0 requirements on this page https://www.microsoft.com/en-us/download/details.aspx?id=34992

So how is UCMA 4.0 a supported prerequisite for Exchange 2016 on Windows 2016 ?

Looking forward to your timely response.

Not applicable
Hello Exchange Team,

UCMA 4.0 is listed as a prerequisite for Exchange 2016 on Windows 2016 https://technet.microsoft.com/en-us/library/bb691354(v=exchg.160).aspx

However UCMA 4.0 was released four years ago and is clearly not supported on Windows 2016 according to the UCMA 4.0 requirements on this page https://www.microsoft.com/en-us/download/details.aspx?id=34992

So how is UCMA 4.0 a supported prerequisite for Exchange 2016 on Windows 2016 ?

Looking forward to your timely response.

Not applicable
Hi there Exchange team,

I had an install issue where the arbitration mailboxes weren't properly created in an Exchange 2010 multi-domain environment and that stopped the Exchange 2016 CU3 install on the Hub Transport service on the first install (this blog shows the problem well: https://social.technet.microsoft.com/Forums/en-US/af60d888-c1b5-40f2-a5cf-af6038fad5ab/error-during-mailbox-role-transport-service?forum=Exch2016SD)

I could only fix this issue by allowing the Exchange 2010 Schema domain prep to run again by temporarily updating the AD Schema from Exchange 2016 back to Exchange 2010 as that was the only way to properly create the missing/corrupt objects. So that's issue one that may happen to others.

Then I tried to continue with Exchange install and it kept failing as the installer set all the Exchange services to Disabled at the beginning of the resumed install. I couldn't uninstall so I simply quickly set all services to automatic once install was restarted again and finally the install completed.

So a couple interest Exchange 2016 clean install issues that may affect others: Fixing arbitration mailboxes on previous Exchange version and then installer issues since Exchange 2016 is partially installed.

-Larry

Not applicable
Hello

looking at the ExchangeSetup.log i found this

[10/20/2016 21:36:43.0445] [1] Executing:

$keyPathRoot = “HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols”;

$keyPath = $keyPathRoot + “\SSL 2.0\Server”;

if (!(Test-Path $keyPath))

{

New-Item -path $keyPathRoot”\SSL 2.0″ -ItemType key -Name “Server” -Force;

}

Set-ItemProperty -path $keyPath -name “Enabled” -value 0x0 -Type DWORD -Force;

$keyPath = $keyPathRoot + “\SSL 3.0\Server”;

if (!(Test-Path $keyPath))

{

New-Item -path $keyPathRoot”\SSL 3.0″ -ItemType key -Name “Server” -Force;

}

Set-ItemProperty -path $keyPath -name “Enabled” -value 0x0 -Type DWORD -Force;

$keyPath = $keyPathRoot + “\TLS 1.0\Server”;

if (!(Test-Path $keyPath))

{

New-Item -path $keyPathRoot”\TLS 1.0″ -ItemType key -Name “Server” -Force;

}

Set-ItemProperty -path $keyPath -name “Enabled” -value 0x1 -Type DWORD -Force;

$keyPath = $keyPathRoot + “\TLS 1.1\Server”;

if (!(Test-Path $keyPath))

{

New-Item -path $keyPathRoot”\TLS 1.1″ -ItemType key -Name “Server” -Force;

}

Set-ItemProperty -path $keyPath -name “Enabled” -value 0x1 -Type DWORD -Force;

Set-ItemProperty -path $keyPath -name “DisabledByDefault” -value 0x0 -Type DWORD -Force;

$keyPath = $keyPathRoot + “\TLS 1.2\Server”;

if (!(Test-Path $keyPath))

{

New-Item -path $keyPathRoot”\TLS 1.2″ -ItemType key -Name “Server” -Force;

}

Set-ItemProperty -path $keyPath -name “Enabled” -value 0x1 -Type DWORD -Force;

Set-ItemProperty -path $keyPath -name “DisabledByDefault” -value 0x0 -Type DWORD -Force;

$keypath = “HKLM:\SOFTWARE\Policies\Microsoft\Cryptography\Configuration\SSL\00010002”;

if (!(Test-Path $keyPath)) { New-Item $keyPath -Force }

Set-ItemProperty -path $keyPath -name “Functions” -value “TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P384,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256,TLS_RSA_WITH_AES_256_CBC_SHA256,TLS_RSA_WITH_AES_128_CBC_SHA256,TLS_RSA_WITH_AES_256_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_3DES_EDE_CBC_SHA,TLS_RSA_WITH_RC4_128_SHA,TLS_RSA_WITH_RC4_128_MD5” -Force;

looks like Microsoft is helping customers secure their server without mentioning it anywhere.

Not applicable
Hi,

when will be fixed Exchange management shell error for DAG computers .

https://social.technet.microsoft.com/Forums/lync/en-US/142ff1ab-242c-4436-a870-068720b5580f/exchange-server-2016-windows-server-2016-datacenter-iis-apppools-constantly-crashing?forum=Exch2016PS

Not applicable
Hello all,

I had two Exchange 2016 servers in my infrastructure and I started to upgrade them to Exchange 2016 CU3.

One of the servers has been updated successfully, but the second one ran into a problem at 'Client Access Front End service' stage.

You can see the CMD output below.

F:\>Setup /m:upgrade /IAcceptExchangeServerLicenseTerms

Welcome to Microsoft Exchange Server 2016 Cumulative Update 3 Unattended Setup

Copying Files...

File copy complete. Setup will now collect additional information needed for installation.

Languages

Management tools

Mailbox role: Transport service

Mailbox role: Client Access service

Mailbox role: Unified Messaging service

Mailbox role: Mailbox service

Mailbox role: Front End Transport service

Mailbox role: Client Access Front End service

Performing Microsoft Exchange Server Prerequisite Check

Configuring Prerequisites COMPLETED

Prerequisite Analysis COMPLETED

Configuring Microsoft Exchange Server

Language Files COMPLETED

Restoring Services COMPLETED

Language Configuration COMPLETED

Exchange Management Tools COMPLETED

Mailbox role: Transport service COMPLETED

Mailbox role: Client Access service COMPLETED

Mailbox role: Unified Messaging service COMPLETED

Mailbox role: Mailbox service COMPLETED

Mailbox role: Front End Transport service COMPLETED

Mailbox role: Client Access Front End service FAILED

The following error was generated when "$error.Clear();

.

"$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1" -AppPoolName:"MSExchangeServicesAppPool"

-Version:"v4.0";

get-WebServicesVirtualDirectory -server $RoleFqdnOrName | set-WebServicesVirtualDirectory

-windowsAuthentication:$true -WSSecurityAuthentication:$true -OAuthAuthentication:$true

" was run:

"System.Runtime.InteropServices.COMException (0x800700B7): Filename: \\?\C:\Program Files\Microsoft\Exchange

Server\V15\FrontEnd\HttpProxy\EWS\web.config

Line number: 8

Error: Cannot add duplicate collection entry of type

'add' with unique key attribute 'key' set to 'HttpProxy.ProtocolType'

at

Microsoft.Web.Administration.Interop.IAppHostAdminManager.GetAdminSection(String bstrSectionName, String bstrPath)

at

Microsoft.Web.Administration.Configuration.GetSectionInternal(ConfigurationSection section, String sectionPath, String

locationPath)

at

Microsoft.Exchange.Management.SystemConfigurationTasks.ExchangeServiceVDirHelper.EwsAutodiscMWA.EnableOrDisableCafeEndpo

int(Configuration

configuration, String endpointName, Boolean enableEndpoint)

at

Microsoft.Exchange.Management.SystemConfigurationTasks.ExchangeServiceVDirHelper.EwsAutodiscMWA.OnSetManageWCFEndpoints(

Task

task, EndpointProtocol protocol, Boolean enableWSSecurity, ExchangeVirtualDirectory adVirtualDirectory)

at

Microsoft.Exchange.Management.SystemConfigurationTasks.SetWebServicesVirtualDirectory.InternalProcessRecord()

at

Microsoft.Exchange.Configuration.Tasks.Task.b__b()

at

Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean

terminatePipelineIfFailed)

at Microsoft.Exchange.Configuration.Tasks.Task.ProcessTaskStage(TaskStage taskStage,

Action initFunc, Action mainFunc, Action completeFunc)

at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()

at System.Management.Automation.CommandProcessor.ProcessRecord()".

The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the

:\ExchangeSetupLogs folder.

F:\>

At this stage I cannot do anything with the server, and /owa is not working anymore. It seems that I have a corrupt installation.

Do you have any ideas how can I solve the error and ran the installation task again?

Regards,

Mircea

Not applicable
We installed Exchange 2016 on Windows 2016 and are happy to report that it's working fine.

The only kink is that we migrated over a user with an Office 365 in-place archive mailbox which doesn't work in OWA with the new server/database. We attempted to rerun the Hybrid wizard but it doesn't seem to be supported in Windows 2016?