Do you have any autodiscover records configured? If not, create internally (assuming this is where the issue is) and point to your desired Exchange server.

1. How To Know My Microsoft Exchange Server Name

You'll want to make sure your certificate(s) are on both servers (make them both match). Check all your virtual directory URLs in powershell against both servers. Use this resource for autodiscover:You might have to do an IIS reset afterwards.If you don't want to make wholesale DNS changes until this is proven, grab a test machine and just mod the host file to point to new Exchange only. This would be for testing only and should not be a permanent solution. Do you have any autodiscover records configured?

If not, create internally (assuming this is where the issue is) and point to your desired Exchange server. You'll want to make sure your certificate(s) are on both servers (make them both match). Check all your virtual directory URLs in powershell against both servers. Use this resource for autodiscover:You might have to do an IIS reset afterwards.If you don't want to make wholesale DNS changes until this is proven, grab a test machine and just mod the host file to point to new Exchange only.

Sep 6, 2017 - On the Server Settings page, enter the server name given by the client in the Server field, and check the box Use Cached Exchange Mode. If you have the right server, but you still can't log in, check your Mailbox Name. Exchange may have your mailbox stored under a different name from your server login name. You can ask your system administrator about this, or you can do the following: Log in to your Exchange server using Outlook Web Access. Open any mail message.

This would be for testing only and should not be a permanent solution. Yes, i have configured a CNAME autodiscorer record as autodiscover.mudomain,com pointing to New server's FQDN.We have bought 3rd party SSL certificate for exchange and i have installed it on both servers & it is same (one certificate) on both servers. Virtual directory URLs are right on both servers.I tested OWA, its working for both servers. Outlook anywhere is also working.

But the users whose mailboxes i transferred to new exchange server (i transferred a few mailboxes to new exchange to for testing) are every few minutes receiving certificate pop-up and asked to enter password.Also i tried to configure a fresh exchange account (MAPI) for a user whose mailbox is on new server bur during autodiscover it went to the old server, i responded 'no' and then it went to new server and asked for password.Actually, i should not ask for password as the user is a domain user. What is the certificate pop-up? Is it a mismatch warning? That should be remedied by a assigning the certs (which you say you've already done) and making sure the cert services are correct (ie: SMTP, IIS). Then do an iisreset on the new Exchange server.

For some clients, it may take a couple of days to wash out. At least that's been my experience.If you do a configuration test in Outlook and it says autodiscover is pointing to old server, then you still have DNS issues OR you haven't waited long enough since changes were made. Check your TTLs.Also, I would use A-Record for autodiscover, not CNAME. There are self signed certificates for exchange on both servers. And i have installed AD CS role on new server also.Do internal and external URLs for OWA, ActiveSync, Outlook anywhere, ECP, EWS be same or i can configure different URLs for internal and external. E.g oldser.mudomain.com for internal and mail.mudomain.com for external?my email is on new server and is configured as MAPI, when i open outlook i receive thisthis certificate is from old server. If i click no, i am got another for new serverthen i click yes and i am prompted for password.other users (whose mailbox is on new server) are facing same issue.

Asim Anwar wrote:There are self signed certificates for exchange on both servers. And i have installed AD CS role on new server also.Do internal and external URLs for OWA, ActiveSync, Outlook anywhere, ECP, EWS be same or i can configure different URLs for internal and external. E.g oldser.mudomain.com for internal and mail.mudomain.com for external?my email is on new server and is configured as MAPI, when i open outlook i receive thisthis certificate is from old server. If i click no, i am got another for new serverthen i click yes and i am prompted for password.other users (whose mailbox is on new server) are facing same issueI would not install AD CS or any AD role or feature for that matter on an Exchange server.

I would also be using only a 3rd party certificate for the Exchange services: IIS & SMTP. For all other services, I would leave the default certs that Exchange created upon install alone. You shouldn't have to mess with anything else. What is the role of Discovery Search Mailbox which is created by default with exchange installation. Does it affect in any way how outlook clients contact the exchange server, 1st preferred one and then other server (ie. There was already one Discovery Search Mailbox created in Old Exchange and then i manually created another Discovery Search Mailbox in new exchange via Powershell. Also do System Mailboxes play any role in discovery of exchange servers?Yesterday i shutdown the old server and only new server was running.

I didn't got cert pop-up from old server but i got it from new server & also asking for credentials. One thing i noticed that after shutting down old server outlook was slow to open and also send & receive takes more time. It looks like that outlook was 1st trying to look for old server & when not found it went to new server.

How To Know My Microsoft Exchange Server Name

Could it be a troubleshooting point? Asim Anwar wrote:What is the role of Discovery Search Mailbox which is created by default with exchange installation. Does it affect in any way how outlook clients contact the exchange server, 1st preferred one and then other server (ie.

There was already one Discovery Search Mailbox created in Old Exchange and then i manually created another Discovery Search Mailbox in new exchange via Powershell. Also do System Mailboxes play any role in discovery of exchange servers?Yesterday i shutdown the old server and only new server was running.

I didn't got cert pop-up from old server but i got it from new server & also asking for credentials. One thing i noticed that after shutting down old server outlook was slow to open and also send & receive takes more time. It looks like that outlook was 1st trying to look for old server & when not found it went to new server. Could it be a troubleshooting point?The Discovery Search mailbox is created by the Exchange install scripts and is typically used in the search-mailbox cmdlet, though it doesn't have to be. Technically its not an arbitration mailbox like the system mailboxes but it is an Exchange default.

When you have multiple Exchange servers in a single environment, you'll see multiple DiscoverySearch mailboxes. It shouldn't cause any issues.System Mailboxes deal with mailbox migrations/moves, federations, etc.

Discovery of Exchange servers from clients is all accomplished via DNS.If you're still having issues, check your configuration results in Outlook and look for issues there. I would troubleshoot from that point. Furthermore, the users whose mailboxes i moved to new exchange server are being asked for credentials every few minutes, although i have made sure that the option for 'always ask for credentials' in outlook is unchecked for those users. Can it be an issue of exchange CALs? I mean do we need separate CALs for both server?

Lets says we have 80 mailbox users. So we need 80 for old & 80 CALs for new server. Is there any option to transfer exchange CALs from old server to new server? How can i install exchange CALs in exchange server? After i buy a third-part SSL certificate and installed it on both servers & assign the exchange services to these services certificate pop-up is not coming but some users who has outlook 2016 are getting Windows security pop-up and if click cancel it outlook is disconnected from exchange bottom right corner it's showing need password.

I click need password and it connects to exchange but again after few seconds/minutes it comes back. This problem is coming only with Outlook 2013 & 2016 (2007 & 2010 don't have this issue).