The below is an interesting result after installing Exchange. The act of installing Exchange will change how TCP/IP operates on the server with respect to ephemeral connections.
This may manifest itself in a few ways.
For example:
The saying goes that nothing monitors AD better than Exchange. While the symptom is an Exchange issue, the underlying root cause is typically something else. Though as an added "feature" Exchange can also monitor additional elements of your infrastructure and indicate they are also unhealthy...
This is one of those such cases, where an Exchange CU was not installing. In the screenshot below, yo… Read the rest “Exchange Setup Fails – Error 3221685616”
Exchange 2010 SP1 introduced the concept of block mode or granular replication. This minimised the time taken for transactions on the active node to be replicated to passive nodes. Since the feature is enabled by default and is self-managing, there is a good chance that you are benefiting from it without being fully aware of it.
See also understanding High Availability and Site Resilience
The default option for DNS resolution on an Azure virtual network is to use the Azure DNS service. This is perfectly fine for regular Internet requests, if you need the capability to register internal DNS records for Active Directory then you will typically need to run your own DNS service. This is the case here and is also something observed with multiple customers. In each of these cases the … Read the rest “Intermittent Azure DNS Resolution Issues With With New Domain Controller”
This is a post to capture the stages of change in Active Directory when the first Exchange server is installed, and opposingly when the last Exchange server is uninstalled. We will not get into any specific details about the individual changes made to AD, rather this is a 20,000 foot view.
A brand new lab was created using Windows Server 2016 for the DCs and Exchange servers.… Read the rest “Stages of AD Changes When Installing and Uninstalling Exchange”