Reviewing HTTPS Namespace Configurations.Typically users only need to know the URL for Outlook web access, with names such as or commonly used. Using DNS aliases is also simpler for end users to remember. Using DNS aliases allows the namespace to be moved during server replacement, load-balanced across multiple servers if the environment scales out to a high availability deployment, and also allows the namespace to be migrated to a new version of Exchange during an upgrade project.
So if there is a namespace problem, it’s best to discover it up front.ĭuring the initial deployment of your existing Exchange environment the namespaces should have been reconfigured to use DNS aliases instead of real server names, even for single server deployments. Namespace configuration and SSL certificates go hand in hand, because the namespaces in use for Exchange need to be included on the SSL certificates being used on the server.Ī mis-configured namespace makes a migration to a new Exchange server more difficult, and can result in poor user experience during the transition. POP and IMAP use their own secure login that is also encrypted using SSL certificates. Most client connectivity to the Exchange namespaces occurs over HTTPS and therefore requires correctly configured SSL certificates. The client access namespaces for Exchange are the DNS names that clients connect to with Outlook, web browsers, mobile devices and so on. During your review of your existing environment as you prepare to migrate to Exchange 2016, you should take the opportunity to review your client access namespace configuration.
0 kommentar(er)
