Demystifying Certificate Based Authentication with ActiveSync in Exchange 2013 and 2016 (On-Premises
Some of the more complicated support calls we see are related to Certificate Based Authentication (CBA) with ActiveSync. This post is intended to provide some clarifications of this topic and give you troubleshooting tips. What is Certificate Based Authentication (CBA)? Instead of using Basic or WIA (Windows Integrated Authentication), the device will have a client (user) certificate installed, which will be used for authentication. The user will no longer have to save a password to authenticate with Exchange. This is not related to using SSL to connect to the server as we assume that you already have SSL setup. Also, just to be clear (as some people have those things confused) CBA is not two-factor authentication (2FA). How does the client certificate get installed on the device? There’s several MDM (Mobile Device Management) solutions to install the client certificate on the device. The most important part of working with CBA is to know where the client certificate will be accepted (or ‘terminated’). How you implement CBA will depend on the response to following questions: Will Exchange server be accepting the client certificate? Will an MDM or other device using Kerberos Constrained Delegation (KCD) be accepting the client certificate? Learn more on the Exchange blog.Released: Exchange Server Role Requirements Calculator 8.4
Today, The Exchange Team released an updated version of the Exchange Server Role Requirements Calculator. This release focuses on bug fixes with the DAG auto-calculation functionality that was introduced in 8.3, as well as, support for ReplayLagMaxDelay. For all other improvements and bug fixes, read the Exchange Team Blog.Released: December 2016 Quarterly Exchange Updates
Today, The Exchange Team announced 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 4 and Exchange Server 2013 Cumulative Update 15 are available on the Microsoft Download Center. Update Rollup 22 for Exchange Server 2007 Service Pack 3 and Update Rollup 16 for Exchange Server 2010 Service Pack 3 are also available. The updates include: - 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 - Latest time zone updates - Important Public Folder fix included in these releases Read more on The Exchange Team blog.The June 2016 Quarterly Exchange Updates are here!
Today Microsoft announced the latest set of Cumulative Updates for Exchange Server 2016 and Exchange Server 2013. In addition to normal fixes to customer reported issues, these releases also include updated functionality. Exchange Server 2016 Cumulative Update 2 and Exchange Server 2013 Cumulative Update 13 are available on the Microsoft Download Center. Read more on the Exchange Blog.Help us test Exchange 2013/2016 to Exchange Online public folder migration
Read more on TechNet. Right on the heels of our recent TAP program announcement, we wanted to see if there are customers who would like to help us validate migration of modern public folders from Exchange 2013/2016 to Exchange Online (EXO). This is a scenario that at this time we do not support, but plan on doing so. Estimated availability of bits for testing those topologies (subject to change): Exchange 2013 public folders > EXO: September 2016 Exchange 2016 public folders > EXO: November 2016 In order to participate, you will need to enroll into the above mentioned TAP program. If you are interested in trying out the migration, please contact the PF migration team atmodernpfmigrationtoexo@service.microsoft.com with the following details: Organization Name Exchange version Total size of Public Folders Number of PF mailboxes Largest Public Folder size Total count of Public Folders Count of Mail enabled Public Folders Which clients are used by users to access PF? Number of users Number of exchange server installations Is Exchange Hybrid setup done? When is the plan to migrate users to EXO? We will review the details and see if we can on-board the organization into TAP/Beta program. We are looking for customers with <250GB of public folder data.
Local domain mailbox migration error
I ran into an issue while migrating from on-premise to O365. On-premise AD domain is “domain.local” so users have their mailboxes smtp address as follows: primary smtp mailto:email%20address%20removed%20for%20privacy%20reasons ( public domain ) aliases smtp proxy: mailto:user@domain.local We setup the hybrid environment and started the mailbox migration but they’re failing with the error that domain.local is not an accepted domain in O365. this is the first time it occurred to us since we made a lot of migration so far What can it be ? obviously is not possible to add domain.local as accepted domain in o365Analyzing Exchange Transaction Log Generation Statistics – Revisited
Almost 4 years ago, The Exchange Team wrote a script called GetTransactionLogStats.ps1, and originally blogged about it here. At the original time of writing, the primary purpose of the script was to collect transaction log generation data, and use that to determine the percentage of transaction logs generated per hour in an environment. This could in turn be used to populate the related fields in the Exchange Server Role Requirements Calculator. Since originally writing this script, there have been significant updates to how the script functions, and also added a handful of new features along the way, which were significant enough that the team wanted to have a new post about it. Of note, the script now: Uses PowerShell Remoting to collect data from many remote servers in Parallel. This significantly speeds up collection speeds. Generates a database heat map, that compares the number of logs generated for each database to the number of logs generated for all databases. This can be used to identify databases that may be overloaded or underloaded. Uses only log generation information from active database copies to determine log generation statistics. Accepts the target servers via a script parameter instead of via a text file. Get more details on the Exchange Team blog.Exchange Hybrid Configuration Wizard - Error 1603 - Connector registration failed
Did any of you encounter this error while installing hcw on an exchange server? Here is the event viewer error details: Connector registration failed: Make sure you are a Global Administrator of your Active Directory to register the Connector. Error: '"The registration request was denied. "'Modern public folder deployment best practices
Since the release of Microsoft Exchange Server 2013, The Exchange Team heard questions regarding the sizing and deployment of modern public folders. It is important to plan migrations for public folders so the client experience with their use is good. This blog post discusses some of the best practices and recommendations regarding modern public folder deployment as well as various related concepts. This blog assumes that customers are already familiar with basic modern public folders concepts but might link to relevant articles. Here is a summary of what's covered: How clients connect to the public folder hierarchy mailbox How to move the public folder data close to the user’s geographical location Summary: deployment considerations Read more on the Exchange Team blog.
