Shulou(Shulou.com)06/02 Report--

Problem description:

There are two full-role servers (An and B) for Exchange 2013, and a new Exchange 2016 server (C) has been deployed. After configuring Exchange 2016, the following problems occur:

When the DNS record points to server A, you can log in to the 2013 and 2016 mailbox accounts normally; when the DNS record points to server B, you can log in to the 2013 mailbox account normally, and the following error occurs when logging in to the 2016 mailbox account

When DNS points to server C (Exchange 2016), you can log in to the 2016 mailbox account normally. The following error occurs when you log in to the 2013 mailbox account

Solution:

Open EMS and enter gpresult / scope computer / r

If you want to see which groups have deny permission

Get-ADPermission-Identity | where {($.ExtendedRights-like "ms-Exch-EPI-Token-Serialization")-and ($.deny-like "True")} | ft-autosize User,ExtendedRights

After searching, it is found that the customer's Exchange server computer account belongs to the domain Admins group. After it is deleted from the Domain Admins group, the problem of restarting the Exchange server is solved.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.