User received security alert, server pointing to the wrong exchange server

Question

User received security alert, server pointing to the wrong exchange server

Jing Quan 0

We are using Exchange Server 2013 and wanted to migrate to Exchange Server 2016. User are facing the issue after I import a wildcard certificate to the new exchange server which I export from the old exchange server. Users are facing this alert when opening the outlook. Database are not migrated to the new Exchange Server 2016 and currently we are still using Exchange Server 2013. May I know if anyone faced these issue before? Is it because of the autodiscover or DNS?

1 answer

Your answer

Answer 1

Anonymous

Hello @Jing Quan ,

The problem encountered may be related to the autodiscover/DNS settings. In order to troubleshoot, you could try the following steps first:

Check the Autodiscover service configuration:

Open the Exchange Management Shell on the Exchange server.
Run the command "Get-ClientAccessService |fl uri" to verify that the autodiscover service is configured correctly.
Check that the Autodiscover service URL matches the Exchange server's URL.

Check DNS configuration:

Run the command "nslookup -type=srv _autodiscover._tcp.yourdomain.com" to verify that the autodiscovered DNS records are configured correctly.
Check that the DNS records point to the correct server and that the SSL certificate matches the name of the server and site.

Check the Exchange Server logs for any errors or warnings related to certificates or Autodiscover.

Hope the above information is helpful to you！

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment". Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Jing Quan 0 Reputation points

2024-02-06T14:33:31.0466667+00:00

We tried to run the command "nslookup -type=srv _autodiscover._tcp.yourdomain.com" to verify that the autodiscovered DNS records are configured correctly, but the record does not exist. These are not configured for the old server as well. Before we encountered these issues, we had imported the existing certificate to the new certificate already and we also tried to migrate the database over to the new server where we encountered Error: MigrationTransientException: MapiExceptionMdbOffline: Unable to get mailbox information. ‎(hr=0x80004005, ec=1142)‎ Diagnostic context: Lid: 49384 Lid: 51176 StoreEc: 0x476 Lid: 40680 StoreEc: 0x476 Lid: 43980 Lid: 58295 StoreEc: 0x476 Lid: 50103 Lid: 48311 StoreEc: 0x476 Lid: 43959 Lid: 60343 StoreEc: 0x476 --> MapiExceptionMdbOffline: Unable to get mailbox information. ‎(hr=0x80004005, ec=1142)‎ Diagnostic context: Lid: 49384 Lid: 51176 StoreEc: 0x476 Lid: 40680 StoreEc: 0x476 Lid: 43980 Lid: 58295 StoreEc: 0x476 Lid: 50103 Lid: 48311 StoreEc: 0x476 Lid: 43959 Lid: 60343 StoreEc: 0x476 May I know if is it because we tried to migrate data over to the new server that caused this issue?
Anonymous

2024-02-26T07:04:45.01+00:00

Sorry for the late reply!

Based on the error information you provided, you may end up getting this error when trying to migrate their mailboxes from one Exchange Server to another. This error may be due to various reasons, you could follow my previous methods provided in this post, and if the problem persists, you could try running Outlook using the cmdlet Outlook.exe /cleanfinders. As for the auto-discover DNS record, if the record does not exist, it may be the reason why users are having problems opening Outlook. You may need to create a new auto-discover DNS record for the new Exchange Server. You may also try using the “Test E-mail AutoConfiguration” tool to check if the autodiscover records are configured correctly.

Share via

User received security alert, server pointing to the wrong exchange server

1 answer

Your answer