External mail flow incoming & outgoing is working fine, Only internal mail flow is impacted.

Application Log an event id 16025

Log Name: Application
Source: MSExchangeTransport
Date: 10/16/2015 12:59:51 PM
Event ID: 16025
Task Category: Configuration
Level: Error
Keywords: Classic
User: N/A
Computer: XXXXX.XXXX.XXXX
Description:
No DNS servers could be retrieved from network adapter 32ddc2da-4531-4553-b3f0-ebd756d504c0. Check if the computer is connected to a network and Get-NetworkConnectionInfo returns any results.

DNS is configured correctly, Name resolution is working as expected & Network Configuration is correct.
Ran command Get-NetworkConnectionInfo however could not find the GUID mention in the application logs.
We could not find the GUID anywhere on the server, even in the registry.

So where is the GUID coming from and why Exchange is looking at it ?

We ran below command and found the Network Adapter GUID that was listed in application logs

Get-TransportServer -Identity XXXXX | Fl Name,ExternalDNSAdapterGuid,InternalDNSAdapterGuid

Name : XXXXX
ExternalDNSAdapterGuid : 32ddc2da-4531-4553-b3f0-ebd756d504c0
InternalDNSAdapterGuid : 32ddc2da-4531-4553-b3f0-ebd756d504c0

This means Exchange will only us this network adapter for name resolution internally, as there was no network adapter with this guid on the Exchange server, DNS query failed.

How to resolve this ?

We ran below command and restart Microsoft Exchange Transport Services, Mail flow started to work. :D

Set-TransportServer -Identity XXXXX -ExternalDNSAdapterGuid 00000000-0000-0000-0000-000000000000 -InternalDNSAdapterGuid 00000000-0000-0000-0000-000000000000

Why this GUID ?

Putting the GUID as 00000000 means Transport will use any network adapter that is available on the server for DNS query and will not be binded to any single network.

Note : This Resolution May Or May Not Apply Depending On The Error.

You can also look at

https://officeserversandservices.com/2014/09/19/exchange-2013-cu5-edge-issue-with-dns-event-id-2000/

However We Were Able To Ping & Windows Server Was Able To Find All Domain Controller In The Site

Configuring Microsoft Exchange Server

    Preparing Setup                                           COMPLETED
    Stopping Services                                         COMPLETED
    Copying Exchange Files                                    COMPLETED
    Language Files                                            COMPLETED
    Restoring Services                                        COMPLETED
    Language Configuration                                    COMPLETED
    Mailbox role: Transport service                           FAILED
     The following error was generated when "$error.Clear();
          $maxWait = New-TimeSpan -Minutes 8
          $timeout = Get-Date;
          $timeout = $timeout.Add($maxWait);
          $currTime = Get-Date;
          $successfullySetConfigDC = $false;

          while($currTime -le $timeout)
          {
            $setSharedCDCErrors = @();
            try
            {
              Set-SharedConfigDC -DomainController $RoleDomainController -ErrorVariable setSharedCDCErrors -ErrorAction SilentlyContinue;
              $successfullySetConfigDC = ($setSharedCDCErrors.Count -eq 0);

              if($successfullySetConfigDC)
              {
                break;
              }
              Write-ExchangeSetupLog -Info ("An error ocurred while setting shared config DC. Error: " + $setSharedCDCErrors[0]);
            }
            catch
            {
              Write-ExchangeSetupLog -Info ("An exception ocurred while settingshared config DC. Exception: " + $_.Exception.Message);
            }

            Write-ExchangeSetupLog -Info ("Waiting 30 seconds before attemptingagain.");
            Start-Sleep -Seconds 30;
            $currTime = Get-Date;
          }

          if( -not $successfullySetConfigDC)
          {
            Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
          }
        " was run: "System.Exception: Unable to set shared config DC.
   at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
   at Microsoft.Exchange.Management.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.

Log Name:      Application
Source:        MSExchangeADTopology
Date:          7/9/2015 4:09:27 PM
Event ID:      2142
Task Category: (3)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      XXXX.XXXX
Description:
Process Microsoft.Exchange.Directory.TopologyService.exe (PID=2848) Forest xxxxx. Topology discovery failed, error details
No Minimal Required Number of Suitable Directory Servers Found in Forest xxxxx Site xxxxx and connected Sites..

To Resolve This Issue, Follow The Below Steps.

1. Locate Microsoft.Exchange.Directory.TopologyService.exe.config File , By Default It Should Be Under "C:\Program Files\Microsoft\Exchange Server\V15\Bin"

2. Open NotePad As Administrator & Then Open Microsoft.Exchange.Directory.TopologyService.exe.config File

3. Locate "Topology MinimumPrefixMatch"

4. Add MinSuitableServer = "1"

5. Save The File & Restart Microsoft Exchange Active Directory Topology Services.

This Should Resolve The Issue.

Note : This Resolution May Or May Not Apply Depending On The Error.

Log Name: Application
Source: MSExchangeRPC
Date: 6/25/2015 2:24:28 PM
Event ID: 1018
Task Category: General
Level: Information
Keywords: Classic
User: N/A
Computer: xxxxxxxxxxxx
Description:
Outlook connectivity protocols are disabled for the current server. The service is being stopped.

To Resolve This issue, Run The Command 

New-RpcClientAccess -Server "Server Name"

The Services Should Start.

Note: Resolution May Different Based On Situation/Environment & Error

It’s A Default Behavior.

- Box Is Enabled By Default In Outlook, If Delegate Is Added Using Outlook.
- Box Is Not Enabled By Default When Using EMS or EMC.
- To Enable It We Will Need To Use A Script Or Manaually, See:

https://msdn.microsoft.com/en-us/library/dd633621(v=exchg.80).aspx
https://msdn.microsoft.com/en-us/library/office/microsoft.exchange.webservices.data.delegateuser.receivecopiesofmeetingmessages(v=exchg.80).aspx

Eg: FirstName.LastName.Custom@Domain.Com

Using Email Address Policies we cannot add "Custom" as a word however we can do it manually on a single users by going into Exchange management Console , Select the user, go to properties, E-Mail Addresses tab and add it.

How can we do it in bulk ?

Step 1

Create a CSV file and name it as EmailAddress.Csv with two columns:

LoginName, SecondaryAddress

I.e:

LoginName, SecondaryAddress

TestUser, TestUser.Custom@Domain.Com

Step 2

Run the below command to start importing the Csv file

Import-Csv EmailAddress.Csv | Foreach-Object{

$user = Get-Mailbox -Identity $_.LoginName

$user.EmailAddresses+=$_.SecondaryAddress

Set-Mailbox $user -EmailAddresses $user.EmailAddresses

Set-Mailbox $user –EmailAddressPolicyEnabled:$False

Set-Mailbox $user –PrimarySMTPAddress $_.SecondaryAddress 

}

So what does the command do 

1. Add's the email address TestUser.Custom@Domain.Com as secondary address.
2. Disable "Automatically update e-mail addresses based on recipient policy" for the users listed in Csv file
3. Set's the primary smtp address to secondary.

Note: Please test the commands in your Lab and the perform the task in production.

Special Thanks to Ravi Nagaraja in helping me with the commands.

How About Hard Coding Multiple Domain Controller's in Exchange 2010/2013 ??

Most Of The Time, The Command Used Is

Set-ExchangeServer -Identity 'SERVER' -StaticDomainControllers "DC Name", "DC Name" -StaticGlobalCatalogs "DC Name", "DC Name" -StaticConfigDomainController "DC Name", "DC Name"

But It Would Fail As Shown Below, B'Cos You Can't Club Multiple Domain Controller's Together In A Single Command With All The 3 Parameters.

So To Achieve This, You Have To Run The Command Separately

It Would Still Fail On -StaticConfigDomainController As You Can Only Have One StaticConfigDomainController At A Time.

To Verify The Change, Run The Below Command.

To Revert The Changes, Run The Below Command.

Its Is Not Recommended To Hard Code Domain Controller's On Exchange Until n Unless Your Are Troubleshooting A Issue Or Have A Special Configuration Requirement.

Thanks

(Shekhar.Kembavi)

 You Could See The Same Information When You Run The Command Get-DatabaseAvailabilityGroupNetwork | FL

Even If You Have 2 NIC For Mapi & Replication Exchange 2013 DAG By Default Will Only Show One DAG Network "MapiDagNetwork"

This Happens Because Exchange 2013 Configures DAG Network Automatic And To Correct This, Administrator Has To Manually Configure DAG Network

First Thing Is To Check The NIC’s , Network Binding Should Be Correct

On The Replication Network "Register This Connection's Addresses in DNS" Should Be UnCheck

As The DAG Network Is Configured Automatic, Run The Below Command To Set It To Manually

Set-DatabaseAvailabilityGroup E2K13-DAG –ManualDagNetworkConfiguration:$True

Run The Below Command To Discover The DAG Network

Set-DatabaseAvailabilityGroup E2K13-DAG –DiscoverNetworks

Now You Should See 2 DAG Network In EAC (Exchange Admin Console) & Shell (MisConfigured Is Gone)

This Should Not Cause Any Issue However Its Better To Have DAG Networks Configured Correctly.

Thanks

(Shekhar.Kembavi)

There are multiple ways and this is option 1

In This Demonstration, I Have Two Mailbox Servers Part Of DAG (E2K10-DAG) And We Are Changing The Database & Log File Path Of MB1

To Check The Current Mailbox Database & Log File Location, Run Below Command

Get-MailboxDatabase “Database Name” | FL Name,LogFolderPath,EDBFilePath

Suspend The Mailbox Database Copy Associated With The Mailbox Database

Suspend-MailboxDatabaseCopy -Identity “Database Name\Server Name” -SuspendComment "Changing Database Path"

Dismount The Active Mailbox Database

Dismount-Database –Identity “Database Name”

Changing Mailbox Database File Path & Log File Path Through Command Will Fail As It Part Of DAG

Move-DatabasePath -Identity MyDatabase01 -EdbFilePath “Database Location” –LogFolderPath “Log File Location

In This Case, We Need To Change It Through ADSIEDIT, Locate The Mailbox Database And Change The Below Attribute Manually

msExchEDBFile

msExchESEparamLogFilePath

msExchESEparamSystemPath

Manually Copy The Mailbox Database EDB File & Catalog Folder To The New Location

Mount The Active mailbox Database After Moving The File.

Mount-Database –Identity “Database Name” –Force

There Are Two Ways To Bring The Mailbox Database Copy In Healthy State

 1.Reseed The Mailbox Database Copy

Update The Mailbox Database Copy

 2.Create Same Folder Structure On Passive Server And Move Mailbox Database EDB File, Catalog Folder In New Database Location And Log Files To New Log File Location.

Resume The Mailbox Database Copy

Resume-MailboxDatabaseCopy –Identity “Database Name\Server Name”

Mailbox Database Copy Will Come In Healthy State.

Thanks

(Shekhar.Kembavi)