Safety Net has a limit
Exchange 2013 introduced another mechanism to help ensure that e-mail gets delivered to users: Safety Net. This feature creates a copy of all inbound messages cross site (by default, but configurable). Exchange stores the messages in yet another .edb file and yet another storage place on the server. You can move the location of the files,
What to name your DAG?
Was helping a customer the other day and the topic of what to name your DAG (Exchange Database Availability Group) was presented. One thought is to just name it ‘DAG’. Works well, but the issue is, when migrating from Exchange Server 2010 to Exchange Server 2013, or 2010 to 2016, or 2013 to 2019, etc.
Controlling bandwidth in a DAG reseed
Q: Is there a way to control bandwidth within a DAG (Database Availability Group) during a reseed process? A: No. However, that’s not the complete story. The question comes up when engineers need to reseed a database (DB). And while there is no native option to control bandwidth, there is a work around. Scenario: One of the
Ever changing life cycle process
Service Packs for Microsoft products, at the time, were provided with 12-24 months of support depending on the product after the release of the next service pack. For Exchange Server 2013, the SP1 is caught in an awkward state of support perpetuity until Exchange 2013 itself hits the end of support lifecycle as there was
To stay hybrid or not to stay hybrid…
That is the question and the answer is: It depends, but most like yes. You need to ensure that you have no on premises dependencies. I’ve had this conversation with more than 5 customers in the past 2 weeks, so thought I’d present the discussion of the options and thought process around removing the Exchange servers from
Dynamic Distribution Groups, Distribution Groups, and Exchange hybrid
I recently ran into a customer that uses: Distribution Groups (DG), leverage Dynamic Distribution Groups (DDG), have started their move to Exchange Online (EXO), while nesting several DDG's inside of DG's. There are known work arounds that you should implement if you are in an Exchange hybrid configuration working with DDG's. Since each realm bifurcates the
DAG’s spread across multi-domains?
Q: Can you spread an Exchange DAG (Database Availability Group) between two domains? A: No. Now the story: Say you have a single forest named: Contoso.com. In that forest, you have two child domains: East.Contoso.com and West.Contoso.com. You also have Exchange servers deployed in both East and West domains, but none in the root domain. Is it possible to host some
cmdlet: Remove-InboxRule
Q: Is there a way to remove an Inbox rule for a mailbox? A: Yes. You can use the Remove-InboxRule cmdlet to remove an Inbox rule from a mailbox. Inbox rules process messages in an Inbox based on conditions specified and take actions. Removing an Inbox Rule can assist in troubleshooting end user’s mailboxes. Remove-InboxRule -Mailbox
cmdlet: Enable-InboxRule
Q: Is there a way to enable an Inbox rule for a mailbox? A: Yes. You can use the Enable-InboxRule cmdlet to enable an Inbox rule. Inbox rules process messages in an Inbox based on conditions specified and take actions. The enable/disable InboxRule cmdelts, assist in troubleshooting end user’s mailboxes. Enable-InboxRule "Move To Junk Mail" -Mailbox
No one received the certificate expiration notification!
Exchange Certificates Prior to Exchange Server 2013, the Exchange application did not automatically notify administrators of a pending upcoming certificate expiring. One of the issues we administrators run into is expiring certificates. If the Exchange environment has a certificate that expires, then typically, trusted access via clients is interrupted. The good news is, you should ask