FIX - Outlook 2013,2016,2019 fails open mailbox Exchange 2019 on-prem in offline LAN
Exchange 2019 on-prem + Outlook 2013/2016/2019 in offline LAN Symptoms: - OWA works - ECP works - Autodiscover works - Test-MAPIConnectivity is successful - Outlook profile can be created - Outlook fails to open the mailbox / “Cannot start Microsoft Outlook” / “The set of folders cannot be opened” / “The attempt to log on to Microsoft Exchange has failed” - Environment has no internet connection Root cause: The Windows client had a default gateway configured, but the gateway IP did not respond to ping. In our case the client received 192.168.1.1 as default gateway, but this IP was unreachable in the offline network. Fix: Set the client default gateway to an existing reachable IP address, for example the Exchange/DC server IP 192.168.1.5. Internet access is not required, but the default gateway must be reachable/responding. After changing: Default gateway: 192.168.1.5 DNS: 192.168.1.5 mail/autodiscover DNS or hosts pointing to Exchange 2019 Result: Outlook 2013, Outlook 2016 and Outlook 2019 connected to Exchange 2019 successfully.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. "'
Exchange 2019 Certificate Error
Hello guys, I plan to migrate my users on Exchange 2019, currently, i have 2 Exchange 2013 servers. As soon as i installed the exchange Server 2019, I changed all the virtual directories and i also runned the command to make sure the users doesn't connect on the new server. But now every users who uses Microsoft Outlook from the environment have a pop up that says that the certificate is not valid, and its normal because I can't apply the services SMTP and IIS on my wildcard certificate. Indeed, when i enable the services SMTP and IIS on my new certificate, it doesn't apply. I tried to enable from the ECP, it says "Are you sure you want to replace the existing certificate", when i say yes, it doesn't change anything, the smtp service is still unchecked. I also tried to stop IIS and restart IIS, restart the server but it doesn't changed anything, and I also tried to enable the services directly with the powershell command with the correct thumbprint of the wildcard certificate as it is said on the event viewer : "Enable-ExchangeCertificate -Server "EX01-2019" -Thumbprint A6BC992FDD... -Services SMTP,IMAP,IIS -Force" But it still don't work, when i check the certificate, only the service IIS is active. I had to uninstall completely the exchange server, because users were complaining about the pop up. Have anyone faced this problem before? Thank you very much for your advices guys
Microsoft Exchange refers to an older certificate that no longer exists, ID 12023.
We have one Microsoft Exchange 2013 server. The Windows Application log periodically displays the ID 12023 entry, which states that Microsoft Exchange could not load the certificate with the thumbprint 3E8XXXXXXXXXXXXXXXXXXXXXXXXXXXX from the local computer's personal certificate store. This certificate was deleted because it expired, and a new self-signed Auth certificate was created. Now, when running the Get-AuthConfig | Format-List CurrentCertificateThumbprint, PreviousCertificateThumbprint, NextCertificateThumbprint command, only the current certificate is displayed. The Microsoft Exchange 2013 server is running. The question is, what should I do to remove the ID 12023 entry from the Windows Application log?
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 o365
How to know if Exchange oAuth Metadata is refresh
Hi, I have an environment with Exchange 2013 hybrid coexistence with Exchange 2019 now. oAuth is enabled. I am suspecting the current environment, servers won't refresh the oAuth Metadata themselves. Is there any logs I can trace that? What event ID indicate the metadata is updated?
Decomissioning a single not anymore used Exchange Server 2013
About 1,5 years ago we moved all the email database to MS365 and since then used online the cloud solution. This was and is not a hybrid connection between the on-premises Exchange server and MS365. Now I want to delete all mailboxes of on-premises server and uninstall it. I am looking at this tutorial in this relation: https://techcommunity.microsoft.com/t5/exchange-team-blog/decommissioning-exchange-server-2013/ba-p/3613793. With some differences (e.g. disabling and deleting mailboxes instead of migrating them) this seems to be a good way. But another tutorial suggests that a single server should be left for management (though this tutorial considers a hybrid installation with 2016/2019 EX-srv): https://www.alitajran.com/remove-last-exchange-server/ My question is: How do I remove (or at least minimize) a no-more used Exchange Server 2013 installation und Windows Server 2012 R2. Thank you in advance.
Autodiscover SSL Certificate showing as expired - Exchange Hybrid
We are having issues with our Autodiscover, we only just noticed this issue yesterday, which is when our old SSL cert expired. After noticing this, I checked IIS on both Hybrid Exchange Servers and noticed the old SSL cert was bound to the web services, changed this to the new cert, restarted the web services, also restarted the server. But yet no change to the certificate associated with autodiscover! Our SSL cert was updated 2 weeks ago, via the cert store and running hybrid configuration wizard. Mail flow seems to be fine, I can see in the smtp send logs that the tls connector is using our new SSL certificate with the correct credentials. Does anyone have any insight into this?
Can't get Exchange inbox to sync on Android Outlook app
I have been dealing with this issue for a year. I am an IT Tech and I cannot get my email to sync on my phone and the other techs can't figure it out either. I downloaded the Outlook app on my phone and set my work account up manually (adding server and domain name, etc) and by choosing Exchange. But the inbox will not sync. I tried it on my wife's phone as well but it also will not sync the inbox so I have a feeling that there is something wrong with my account. My coworker logged into his account on my phone and his inbox immediately synced, so I don't think it is an issue with my phone but possibly an issue with my account. I even deleted my email account in the EAC and created a new one but I am having the same problem. My organization uses Exchange 2013. Things I have tried on my phone- restarting phone, changing settings in the Android Outlook settings: battery is set to unrestricted, "allow data usage while data saver is on" is set to on, and turning off "remove permissions if app is unused". Is there a setting in either the Microsoft 365 admin center or the Exchange admin center that I need to change?
