– A new Outlook on the web compose experience – Support for .Net 4.6.2 – Change to Pre-Requisites installed by Setup – Update on Windows Server 2016 support KB3206632 – Latest time zone updates – Important Public Folder fix included in these releases
Support for .Net 4.6.1 is now available for Exchange Server 2016 and 2013 with these updates. We fully support customers upgrading servers running 4.5.2 to 4.6.1 without removing Exchange. We recommend that customers apply Exchange Server 2016 Cumulative Update 2 or Exchange Server 2013 Cumulative Update 13 before upgrading .Net FrameWork. Servers should be placed in maintenance mode during the upgrade as you would do when applying a Cumulative Update. Support for .Net 4.6.1 requires the following post release fixes for .Net as well.
Note: .Net 4.6.1 installation replaces the existing 4.5.2 installation. If you attempt to roll back the .Net 4.6.1 update, you will need to install .Net 4.5.2 again.
AutoReseed Support for BitLocker
Beginning with Exchange 2013 CU13 and Exchange 2016 CU2, the Disk Reclaimer function within AutoReseed supports BitLocker. By default, this feature is disabled. For more information on how to enable this functionality, please seeEnabling BitLocker on Exchange Servers.
SHA-2 Support for Self-Signed Certificates
The New-ExchangeCertificate cmdlet has been updated to produce a SHA-2 certificate for all self-signed certificates created by Exchange. Creating a SHA-2 certificate is the default behaviour for the cmdlet. Existing certificates will not automatically be regenerated but newly installed servers will receive SHA-2 certificates by default. Customers may opt to replace existing non-SHA2 certificates generated by previous releases as they see fit.
Migration to Modern Public Folder Resolved
The issue reported in KB3161916 has been resolved.
This cumulative update fixes the following issues:
Microsoft Knowledge Base articles. This update also includes new daylight saving time (DST) updates for Exchange Server 2016. For more information about DST, go to Daylight Saving Time Help and Support Center.
Move Public Folder script from 2007/2010 to Office 365 Script created by Ward Vissers www.wardvissers.nl
THIS CODE IS MADE AVAILABLE AS IS, WITHOUT WARRANTY OF ANY KIND. THE ENTIRE RISK OF THE USE OR THE RESULTS FROM THE USE OF THIS CODE REMAINS WITH THE USER
Please Select the Choice You Want
Prepare for Migration (Legacy Exchange Server 00) Add the Office 365 Domain Name 01) Take a snapshot of the original source folder structure 02) Take a snapshot of public folder statistics such as item count, size, and owner. 03) Take a snapshot of the permissions 04) Locate public folders that have a backslash in the name 05) Rename Public Folder 06) Checks the public folder migration status. 07) Set PublicFolderMigrationComplete to False
Generate CSV Files and create Public Folder Mailboxes (Legacy Exchange Server) 11) Export-PublicFolderStatistics PFSizeMap.csv 12) PublicFolderToMailboxMapGenerator PFMailboxMap.csv
Create the public folder mailboxes on Exchange Online 13) Master Public Folder Name 14) Create Public Folder Mailboxen (Check PFMailboxMap.csv)
Migrating the Public Folders 15) Export mail-enabled public folders from Active Directory 16) LegacyExchangeDN Administrator 17) LegacyExchangeDN Public Folder Server 18) External Name Outlook Anywhere 19) Set the XML file 20) Give the CSV file to start the Migration 21) Public Folder Migration Status
Lock down the public folders on the legacy Exchange server for final migration (downtime required) 22) Lock the legacy public folders for finalization
Finalize the public folder migration (downtime required) 23) Finalize the public folder migration (downtime required)
Test and unlock the public folder migration 24) Add Public Folder to Test User 25) Unlock the public folders for all other users 26) Public Folder Migration Complete (Legacy Exchange Server) 27) Public Folders Enabled Local
Final Check 28) Take a snapshot of the original source folder structure. 29) Take a snapshot of the public folder statistics such as item count, size, and owner 30) Take a snapshot of the permissions
The Exchange team is announcing today the availability of Cumulative Update 8 for Exchange Server 2013. The Cumulative Update Package and UM Language Packsare now available on the Microsoft Download Center. Cumulative Update 8 represents the continuation of our Exchange Server 2013 servicing and builds upon Exchange Server 2013 Cumulative Update 7. The release includes fixes for customer reported issues, minor product enhancements and previously released security bulletins. A complete list of customer reported issues resolved can be found in Knowledge Base Article KB3030080. Customers running any previous release of Exchange Server 2013 can move directly to Cumulative Update 8 today. Customers deploying Exchange Server 2013 for the first time may skip previous releases and start their deployment with Cumulative Update 8 directly.
We would like to call your attention to a few items in particular about the Cumulative Update 8 release:
Calendar and Contact Modern Public Folders favorites added in Outlook are now accessible in OWA
Batch Migration of Public Folders to 2013 improves migration throughput and PF migration experience
Smoother migration for EAS clients to O365 with automatic profile redirect upon successful Hybrid migration to O365 (EAS client must support HTTP 451 redirect)
Cumulative Update 8 includes Exchange related updates to Active Directory schema and configuration. For information on extending schema and configuring the 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., CU8) or the prior (e.g., CU7) Cumulative Update release.
This update also includes new daylight saving time (DST) updates for Exchange Server 2010 SP3. For more information about DST, go to the following Microsoft website:
Move Public Folder script from 2007/2010 to Exchange 2013 Script created by Ward Vissers www.wardvissers.nl
THIS CODE IS MADE AVAILABLE AS IS, WITHOUT WARRANTY OF ANY KIND. THE ENTIRE RISK OF THE USE OR THE RESULTS FROM THE USE OF THIS CODE REMAINS WITH THE USER
Please Select the Choice You Want
Prepare for Migration (Legacy Exchange Server) 01) Take a snapshot of the original source folder structure 02) Take a snapshot of public folder statistics such as item count, size, and owner. 03) Take a snapshot of the permissions 04) Locate public folders that have a backslash in the name 05) Rename Public Folder 06) Checks the public folder migration status. 07) Set PublicFolderMigrationComplete to False
Generate CSV Files and create Public Folder Mailboxes (Legacy Exchange Server) 11) Export-PublicFolderStatistics PFSizeMap.csv 12) PublicFolderToMailboxMapGenerator PFMailboxMap.csv
Create the public folder mailboxes on the Exchange 2013 server 13) Master Public Folder Name 14) Create Public Folder Mailboxen (Check PFMailboxMap.csv)
Migrating the Public Folders 15) BadItemLimit (Exchange 2007 Only) 16) Migrate Exchange 2010 public folders 17) To verify that the migration started successfully (AutoSuspend is Compleet)
Lock down the public folders on the legacy Exchange server for final migration (downtime required) 18) Lock the legacy public folders for finalization
Finalize the public folder migration (downtime required) 19) Finalize the public folder migration (downtime required)
Test and unlock the public folder migration 20) Add Public Folder to Test User 21) Unlock the public folders for all other users 22) Public Folder Migration Complete (Legacy Exchange Server) 23) Public Folders Enabled Local
Final Check 24) Take a snapshot of the original source folder structure. 25) Take a snapshot of the public folder statistics such as item count, size, and owner 26) Take a snapshot of the permissions
