Exchange Server 2019 HA & DR - Design
Hello Team, I'm asked to setup a HA & DR of Exchange Server 2019 (In-House) with only Internal Clients connecting to it. There will be no Internet or external access. There are 2 Sites, A & B connected by Dark Fibre of 10G and though users are around 3000 but their usage is very minimum as it is only for internal purposes. They are keen to have HA & DR and in current setup I had setup HA with 3 servers. I was reading about cross-site DAG and need little assistance in setting up the same. I need to design HA & DR so that if there is a site failure then automatically the DR should continue the work. I thought Active-Active would be best because if anyone of the site fails, say Site A fails, the 40-50% of the users who would have their mailboxes on them would move to Site B. 1. Is it best to setup Active-Active or Active-Passive, benefits, safety, Administrator's Tasks in failover scenario? 2. Is it better to keep even nodes on each side with Witness Server (for Site A - Witness Server will be on B) & Alternate Witness Server ? If anyone has a sample design document with key configuration to keep in mind, if you can share it, please let me know,CVE-2024-49040: Mitigating a Critical Microsoft Exchange Server Vulnerability
CVE-2024-49040 is a spoofing vulnerability identified in Microsoft Exchange Server versions 2016 and 2019. This flaw allows attackers to forge legitimate sender addresses on incoming emails, potentially making malicious messages appear trustworthy. The vulnerability arises from improper verification of the P2 FROM header during email transport, permitting non-RFC 5322 compliant headers to pass through and be displayed as legitimate by email clients like Microsoft Outlook. Recommended Mitigation Steps To protect your organization from this vulnerability, consider the following steps: Apply Security Patches: Enhance Email Security: Educate Users: Implement Strong Password Policies: Monitor Network Traffic: By taking these steps, organizations can significantly reduce the risk of exploitation and protect their sensitive data. It is essential to stay informed about the latest security threats and to adopt a proactive approach to cybersecurity. These patches are available in WSUS. If the concerned team has not yet synchronized, please proceed with the synchronization and apply the latest patches. Alternatively, you can find these patches on the official Note: These patches are applicable for the following Exchange versions: Microsoft Exchange Server 2016 Cumulative Update 23 Microsoft Exchange Server 2019 Cumulative Update 14 Microsoft Exchange Server 2019 Cumulative Update 13
Exchange System Mailboxes after migration to Exchange 365
Hello all, After the migration off the mailboxes to Exchange 365, there are 2 mailboxes in our on-premise environment: extest + DiscoverySearchMailbox. Because of this 2 mailboxes, the Exchange server has the 'Mailbox Server'-role. I think this is not neccesarry. I don't understand why this 2 mailboxes are counted as normal mailbox, because other system mailboxes aren't and also not visible. Does anyone know what the function is off this mailboxes? Kind regards, Arjan
Migration of system mailboxes from 2013 to 2019?
It is a hybrid environment with exchange 2013. User mailboxes have been migrated to exchange online. We want to migrate to exchange 2019. do we need to migrate the system mailboxes from exchange 2013 to 2019? Or do I just need to recreate the system mailboxes in exchange 2019?
I cannot receive external emails after migrating from Exchange Server 2013 to 2019.
Hello everyone, I just followed the step-by-step guide from the following link: Migrating from Exchange 2013 to Exchange 2019 - A Step-by-Step Guide to migrate my Exchange 2013 server to the 2019 version. I completed all the steps mentioned, including creating the connectors, databases, etc. Currently, I have both servers coexisting. I used a test mailbox, which I migrated to one of the databases on the new 2019 server. The problem I'm encountering is that when sending an email from this mailbox to outside the organization, the emails are received. However, when I reply to that email from outside, the replies are not received in the Exchange 2019 mailbox. I used the Microsoft Remote Connectivity Analyzer tool, and it didn't show any errors. When I check the queue on the 2013 server, I can see that all the emails sent from outside are in it. The following error is indicated: Identity: UHPEX2013\Unreachable\309869005505088 Subject: RE: Test Internet Message ID: <email address removed for privacy reasons> From Address: email address removed for privacy reasons Status: Ready Size (KB): 413 Message Source Name: SMTP:Default UHPEX2013 Source IP: 200.123.132.100 SCL: 0 Date Received: 23/05/2024 02:26:42 PM Expiration Time: 25/05/2024 02:26:42 PM Last Error: There is currently no route to the mailbox database. Queue ID: UHPEX2013\Unreachable Recipients: email address removed for privacy reasons;2;3;There is currently no route to the mailbox database.;2;ExternosUHP2EX2019;0. Could you please help me resolve the issue without causing impact or disruption to my productive 2013 server?
Exchange Search failure
While running Test-ExchangeSearch on Exchange Server 2019, we are getting the following error message "Test-ExchangeSearch failed for database DB-XXX at 2024-05-23 07:09:28, SearchTimeInSeconds : 0 and Error : Mapi Error for mailbox database "DB-XXX": [Microsoft.Exchange.Data.Storage.IllegalCrossServerConnectionException]: Cannot open mailbox /o=XXXX/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=XXXXVM-SMBX02/cn=Microsoft System Attendant. Inner error [Microsoft.Mapi.MapiExceptionIllegalCrossServerConnection]: MapiExceptionIllegalCrossServerConnection: Monitoring mailbox [] with application ID [Client=Management] is not allowed to make cross-server calls from [XXXXVM-SMBX04.xxx.abc] to [XXXXVM-SMBX02.xxx.abc]. But when we runTest-ExchangeSearch on the server itself, it passes for the database hosted/mounted on the server but fails for databases mounted/hosted on other Exchange Servers. We have 4 Exchange Server 2019 configured with DAG and have 24 databases.Exchange Server 2019 forward slash OU Name inquiry
Hello guys, Hope you guys all have been doing great. I would like to ask a question below: When forward slash is in OU name there's error when I try to manage user's profile ‘Can’t find the Organizational Unit that you specified and also UPN suffix is blank. I have tried to find MS Tech document and found information below: Can't manage a user in Exchange Admin Center - Exchange | Microsoft Docs One of workaround says use the exchange management shell to manage, I have tried to change ou in attribute editor and tried to change querybased value but error occurs Use the Exchange Management Shell to manage the affected user accounts. Does it any way to keep the slash on OU name? or changing the OU name is the only way that we can resolve the issue? If we want to keep the slash, what would be the impact like mailflow or administration? Thank you for the reply in advance! Hope you all have a good week!
Using Exchange 2013 cmdlets with Exchange 2019 Schema
We have Exchange 2013 with Skype for Business 2015 within our infrastructure. We are working to remove SfB 2015 but will not have this completed within the 90 days of throttling allowance for old Exchange Systemshttps://techcommunity.microsoft.com/t5/exchange-team-blog/throttling-and-blocking-email-from-persistently-vulnerable/ba-p/3815328. We want to install an Exchange 2019 server as the bridge for sending to Exchange Online as we have been told this will suffice in stopping the throttling issue for now. Since Exchange 2019 does not support UM, if we update the Exchange Schema to 2019, can we still use the Exchange 2013 cmdlets that are associated with Unified Messaging until we remove the SfB 2015 existence? All the mailboxes associated with SfB will still be on Exchange 2013 servers.
