Request on Exchange Server SE CU1 Codebase and Trial Version Behavior
Dear Microsoft Exchange Team and Community, I have questions about Exchange Server Subscription Edition (SE): Codebase of Exchange SE CU1 vs. Exchange 2019 CU15 The roadmap says Exchange SE RTM matches Exchange 2019 CU15 codebase, with new features starting in SE CU1. Is SE CU1 a standalone codebase or a direct continuation of Exchange 2019 CU15 with added features? Behavior after Exchange SE trial expiration What happens when the SE trial expires? Are all functions fully retained? Are any services or features restricted or disabled? Will the server remain usable? Thanks for your clarification!
Issues after Exchange 2019 CU15 install
Hello, We have some issues with our Exchange server. After CU15 install we have high(er) CPU usage at the server and slow(er) Outlook (online no cache mode enabled) connection at the client. MAPI over HTTP and Exchange Extended Protection is enabled. Have anybody else who have the same issues?Exchange 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?
Download 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 ?
Exchange 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 out
Exchange 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.
Exchange 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: http://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 DM
Recipient 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: -
