2016
728 TopicsExchange health set unhealthy
Hello everyone! Some healthprobes on our Exchange 2016 Server have been reporting an unhealty state since the middle of February. OAB.Proxy, EWS.Proxy, Outlook.proxy and OutlookMapiHttp.Proxy. We have no mailboxes on the server, so its not critical, but I would still like to figure out what is going on. They all fail with "The remote server returned an error: (401) Unauthorized" and if I try to invoke the probe i see this in the response: It looks like the SSL validation is not happening. Is it normal for the probe to use localhost for this? When I run "Get-WebServicesVirtualDirectory" both internal and external virtual directry is set to our external url. Any insight is greatly appreciated!63Views0likes2CommentsTwo Exchange servers in one domain
Hello everybody, I want ask you, because I can’t find how “Exchange magic” works. I have two seperate Exchange DAG clusters in one domain, with different DNS records and different Virtual Directories URLs. Servers are on two physically diferent locations, but we create a direct connection between two locations for migration mailboxes in near future. We notice sometimes clients from old enviroment can connect through new enviroment and access to mailboxes on old servers. How is it possible? What communication ongoing between old and new Exchange enviroments? Can somebody explain me specifically? Thank you very much for answer to this mystery.139Views0likes8CommentsUser is unable to login to Mailbox
Hello experts, We are in Hybrid environment and one of the user which was recently re-enabled an AD account as the user is returned back to us, is unable to login to mailbox Steps we done Re-enabled the AD account and moved it to syncing OU and added license to enable mailbox I checked the recipient details in both on-prem and online On-prem results RecipientType : MailUser RecipientTypeDetails : RemoteUserMailbox Online results RecipientType : UserMailbox RecipientTypeDetails : UserMailbox What is the part that is missing here.156Views1like9CommentsLimit unauthenticated mail
The standard configuration in Exchange is that anyone internally can connect to telnet and send unauthenticated e-mail to anyone inside the organization. We want to limit this so that only those applications that need to send unauthenticated mail are allowed to do this. We have Exchange 2016 hybrid and the mail flow is routed via Exchange online. The local Exchange server is only used for administration and relay. With that setup, can we just remove 'anonymous authentication' from the 'Default Frontend' connector and add a connector with the ip addresses of the applications that will be allowed to send? Or will it break the mail flow? Anyone have any tips on how to achieve this? I could create a connector that contains the IP-ranges of our empoyee networks, but that seems a bit backwards.Solved84Views0likes4CommentsDecomm a single EX16 after migration to MS365
We have moved all users off on-prem EX16 8 weeks ago. 3rd party did full migration to MS365, new external Azure AD, no hybrid mode. EX16 has been in maintenance mode for 3 weeks. Have dismounted databases. I am finding lots of conflicting details about decommissioning this server. It was a single server, no DAG, 50 users. Most instructions are for migration to on-prem higher versions with users still tied to local AD and EXCH. I just want to remove it from the environment and retire hardware. Not finding un-install details specific to this scenario. Anyone have some direction?28Views0likes1CommentOOF to personal emails dropped at EOP relay
Issue: When an OutOfOffice recipient is gmail.com, outlook.com, msn.com ,etc, relay is dropped by EOP. Oof is delivered when recipient is an M365 tenant. Any other mail flows no issues to gmail and other personal addresses as well. It's only OOF to personal addresses. Env: Exch 2016 with EOP send/receive (hybrid manually, not hcw) We found 2 blog posts might be relevant, but these instructions did not resolve: https://techcommunity.microsoft.com/blog/Exchange/updated-requirements-for-smtp-relay-through-exchange-online/3851357 https://techcommunity.microsoft.com/blog/exchange/enhanced-filtering-for-connectors---improving-deliverability-and-minimizing-fals/4160483 This is what we see on the smtp protocol log: >,MAIL FROM:<> SIZE=7072, >,RCPT TO:<****@gmail.com> NOTIFY=NEVER, <,250 2.1.0 Sender OK, <,550 5.7.64 TenantAttribution; Relay Access Denied [*****.eurprd03.prod.outlook.com 2025-01-04T14:03:21.934Z *****], >,QUIT, ### We also looked into dkim, but finally found this line: By design, Exchange Online Protection uses the high risk delivery pool (HRDP) to send OOF replies, because OOF replies are lower-priority messages. https://learn.microsoft.com/en-us/exchange/troubleshoot/email-delivery/understand-troubleshoot-oof-replies#what-are-out-of-office-replies We feel this is not likely a connector or ceritifcate or onprem issue, rather something with HRDP and OOF in EOP. Could you confirm we are on the right track now? If not the Exchange Team can help please let me know who. Thanks118Views0likes6CommentsMove request falsely stuck
We are migrating mailboxes cross forest between two Exchange organizations and are having an issue with 3 of them. We were migrating these 3 mailboxes when the target Exchange server had the log disk filling-up, and move request seemed to be stuck. We extended the disk and the move actually completed, we check the get-moverequest for "non completed" and none was reported. We move the mailbox database, on the target DAG, between the two hosts and then, not sure if it's related, the get-moverequest reported three entries in "waitingforjobpickup" even if the migrationa has successfully completed, the mailbox is active on the destination and users are connecting without issue. How can we clear the status correctly or we just can delete the move request ? thanks SC45Views0likes1CommentProblem with the OWA client after update Exchange Server 2016 CU23 24 novembre SU v2
Hello, After applying the Exchange 2016 CU23 November 24 SU v2 update, we are experiencing problems with our OWA customers. Outlook or mobile clients do not have this symptom. Users are automatically disconnected as soon as they want to write a new message by entering the recipient or elements in the message body.Browsing mailbox folders does not cause any disconnection. I should also point out that we encounter this problem whenever our two Exchanges servers are activated. If we switch one Exchange server to maintenance mode and switch the databases to the other server, the problem no longer occurs. Also, access to the ECP interface is not displayed correctly when both servers are active. Do you have any ideas for solving this problem? Thank you.121Views0likes2CommentsInstall exchange server Error :
Hi teams, i have a problem with installing exchange server , I want to install Exchange again on a server that has already uninstalled Exchange after uninstalling exchange i delete manulay the folder C:\Program Files\Microsoft\Exchange Server, now when i try to install exchange server i have this error : also with GUI : any idea , i find also these services in server : any helpSolved68Views0likes1Comment