exchange 2019
18 TopicsExchange Management Shell 2019
Hi All, We have a 4-node Exchange 2019 hybrid environment. On one of the nodes, we've noticed that connecting to the Exchange Management Shell takes an unusually long time, despite normal CPU utilization and all other services running smoothly. Has anyone experienced a similar issue or have any insights on potential causes and solutions?87Views0likes3CommentsDownload Domains - CVE-2021-1730 - issue with missing SAN certificate ?
Hi gents, I have Exchange 2019 with almost recent patch installed Version 15.2 (Build 1544.4) Few months ago I configured required steps to mitigate CVE-2021-1730 and it worked for sure. Now customer reported that during OWA browsing while attempting to download attachment, he's getting an error about unsafe connection ( certificate error occurs when trying to retrieve attachments). In details while clicking on the attachment, default OWA name is redirected from the default url webmail.domain.com to the attachments.webmail.domain.com. Then the error is showing up about the certificate "net::ERR_CERT_COMMON_NAME_INVALID". Currently for OWA site there is attached dedicated certificate with *.domain.com. The url for download domain (internally and externally) is pointing through CNAME url attachments.webmail.domain.com. The name of the domain is included in certificate SAN entry, but it's for whole domain *.domain.com, not explicitely for attachments,webmail.domain.com. Is it possible that despite having asteriks in the certificate domain name, dedicated SAN name is required ?171Views0likes1CommentHow to search and delete specific phishing email from all mailboxes
Hi Everyone! We recently received a couple of phishing emails at our company. We have a 3-node Exchange 2019 cluster. I have been assigned the task of deleting these emails. First, I ran this command to find out the amount of received emails: Get-Mailbox -ResultSize Unlimited | Search-Mailbox -SearchQuery 'subject:"subject of the phishing email"' And I got this error: The path of the destination mailbox or .pst file is required My idea is to test first and then run this command to delete the emails: Get-Mailbox -ResultSize Unlimited | Search-Mailbox -SearchQuery 'subject:"subject of the phishing email" AND from:"email-phishing-sender"' -DeleteContent Am I on the right path? Could you help me with the right steps to do this task? Thanks in advance!Solved681Views0likes3CommentsExchange 2019/outlook 2016
Hello all. We have three exchange servers in different domains but they all fall under the same site(AD site and services) Our DC's for the three domains also follow that topology. I think this impossible but I would like to ask the room. How do i get a outlook client in domain 1 to use the exchange in domain 1 and sof forth. When I open up outlook and show connection status I see connections from exchange servers in the different domains. like the SMTP is the correct domain but the in the server name column I have a few connections like https://mail.domain1.com https://mail.domain2.com and mail.domain3.com all established and connected. Without managing sites and services is there another way match the connection from client in outlook to the domain? I read about send and receive connectors but not sure if this would alleviate the problem. All ideas are welcome as i have been trying to figure this out826Views0likes5CommentsExchange 2019 SMTP Receive Connector
Hi Tech, We have Exchange 2019, SMTP Open Relay Receive Connector. We have around 300+ services using this connector. Recently We engaged a few customers and performed exercise to send email with Authentication. My question here is, How we can find which smtp connection/IP is relaying emails using authentication and which connection/IP is relaying email anonymously/without authentication. I tried finding authentication tags in smtp receive connector's logging without any success. Any idea or direction to achieve this? Thank in Advance.922Views0likes1CommentExchange 2019 CU14 PowerShell and ADDriver log history issues
We have two Exchange 2019 Standard servers in a DAG and after updating from CU12 to CU14 one of those servers no longer logs PowerShell or ADDriver history. For example in the Application Log we see: Event ID 6003 Source MSExchange Common - RpsCmdletLogs: Failed to create the log directory: C:\Program Files\Microsoft\Exchange Server\V15\Logging\CmdletInfra\LocalPowerShell\Cmdlet because of the error: Access to the path 'C:\Program Files\Microsoft\Exchange Server\V15\Logging\CmdletInfra' is denied.. Logs will not be generated until the problem is corrected. Event ID 6003 Source MSExchange Common - ADDriver: Failed to create the log directory: C:\Program Files\Microsoft\Exchange Server\V15\Logging\ADDriver because of the error: Access to the path 'C:\Program Files\Microsoft\Exchange Server\V15\Logging\ADDriver' is denied.. Logs will not be generated until the problem is corrected. These events do not appear on our second Exchange server. The issue is with the first server to be updated and they were both updated from the command line as per this article without any errors: www.alitajran.com/install-exchange-cumulative-update I have checked security permissions are the same for both servers for the paths mentioned. Has anyone seen this or have any ideas how to troubleshoot ? Thanks DM1.8KViews0likes0CommentsRecipient display name show other attribute name after sent.
Hi SME's, Quick check if you guys had this experience before. 1 user issue where after sent an email, in sent item folder, user seeing recipients in "TO" showing different display name. According to user, the display name showing as SAMAccount name instead display name ex: 323232 instead Mr.ABC. Checked on address book, Mr.ABC information is correct, and it is showing correctly during compose as well. It just after sent it out, it is showing different in sent items folder. This only happened for this 1 user. Other users no issue sending to the same recipient. Any thoughts and fix method? This is example image, issue in yellow highlighted: -394Views0likes0CommentsHow to test mail flow in Exchange 2019 in an existing Exchange 2013 environment.(Solved)
Hi experts, I'm trying to complete the upgrade process from Exchange 2013(on-premise) to Exchange 2019(on-premise). I did all the steps that are explained in Best Practice for Upgrade and the Upgrade Assistant from Microsoft experts. Also, I'd like to thank you for them. But what is my question? There are 2 Exchange 2013 servers in my domain with more than 2000 users. I installed new Exchange servers and all work fine in the organization. Regarding our business, I can not take a risk and start mailbox migration directly and would like to test all things in the new environment first, like OWA, Outlook, and all related things to the new environment. I created some databases on the new servers and some users on them to test mail flow on these servers. The problem that I have is, that I can connect directly to new servers in OWA to newserver.mydomain.com and work with test users, and mail flow there works fine. But when I try to use Outlook to test, it can not find new servers. I think my issue is autodiscover record in DNS but I can not change it at the moment, because the old environment is working. When I change this record on the new servers to itself(newserver.mydomain.com) and try to configure a profile on Outlook manually and set the mail servers on the new server directly, Outlook still can not find the servers. What is your suggestion to have a test way in my case? I searched so many articles to find a way but it seems in this way, there is no solution. I don't want to create a new zone for the test, because in the External mail flow test, I will need an SSL certificate. I appreciate any help or ideas that you can provide. Kind Regards, HassanSolved4.3KViews0likes8CommentsExchange Hybrid - On-Prem mailboxes can't send to Online mailboxes
We're now running Exchange Hybrid OnPrem: Exchange 2019 latest patch. On-Prem mailboxes are not able to communicate with mailboxes in Exchange Online in any way. The other way around is working fie though. Mailboxes on-prem: The communication to Exchange Online mailboxes isn't working > Can't send emails to Exchange Online mailboxes, or see free busy of Exchange online mailboxes and can't send calendar invites. Mailboxes in Exchange Online: Receive emails from external sent to: email address removed for privacy reasons - working. Receive emails from external sent to: email address removed for privacy reasons - working. Receive emails form external setn to: email address removed for privacy reasons - NOT working. Receive emails from internal on-prem mailbox - NOT working. No matter to which domain it is sent. Calendars: Users can fully see on-prem calendars and can also send invites. Send emails to external and internal - working. The Exchange on-prem queue shows: DeliveryType: DnsConnectorDeliver Status: Retry NextHopDomain: cadomain.mail.onmicrosoft.com The bounce back emails the on-prem mailbox receives when trying to send to a mailbx that is online: Server at cadomain.mail.onmicrosoft.com (104.47.75.164) returned '400 4.4.7 Message delayed' 3/24/2023 3:38:01 AM - Server at cadomain.mail.onmicrosoft.com (104.47.75.164) returned '450 4.4.316 Connection refused [Message=Socket error code 10061] [LastAttemptedServerName=cadomain.mail.onmicrosoft.com] [LastAttemptedIP=104.47.75.164:25](Socket error code 10061)' This is the on-prem Exchange delivery report: Delivery Report for usernametest2 (usernametest2(at)domain.ca) Submitted3/24/2023 9:25 AM EXCHANGE2019 The message was submitted to on-premExchange.domain.local. Pending 3/24/2023 9:25 AM on-premExchange.domain.local Message was received by on-premExchange.domain.local from on-premExchange.domain.local. 3/24/2023 9:25 AM on-premExchange.domain.local The e-mail address for recipient "usernametest2(at)domain.ca" was updated to the e-mail address "usernametest2(at)cadomain.mail.onmicrosoft.com". The message is in the process of being delivered. Submitted 3/24/2023 9:27 AM on-premExchange.domain.local The message was submitted to on-premExchange.domain.local. Pending 3/24/2023 9:28 AM on-premExchange.domain.local The e-mail address for recipient "usernametest2(at)cadomain.mail.onmicrosoft.com" was updated to the e-mail address "usernametest2(at)domain.ca". The message is in the process of being delivered. 3/24/2023 10:40 AM on-premExchange.domain.local Message delivery is taking longer than expected. There may be system delays. For more information, contact your email admin.9.2KViews1like6Comments