Logging SMTP Protocol Activity in Exchange 2007 / 2010

Enable protocol logging on a Receive Connector

Set-ReceiveConnector “Connector Name” -ProtocolLoggingLevel verbose

Receive Connector logs default path:

  • Exchange 2010: \Exchange Server\V14\TransportRoles\Logs\ProtocolLog\SmtpReceive
  • Exchange 2007: \Exchange Server\TransportRoles\Logs\ProtocolLog\SmtpReceive

To change:

Set-TransportServer “TRANSPORT SERVER NAME” -ReceiveProtocolLogPath “C:\Directory”

Enable protocol logging on a Send Connector

Set-SendConnector “Send Connector Name” -ProtocolLoggingLevel verbose

Send Connector logs default path:

  • Exchange 2010: \Exchange Server\V14\TransportRoles\Logs\ProtocolLog\SmtpSend
  • Exchange 2007: \Exchange Server\TransportRoles\Logs\ProtocolLog\SmtpSend

To change:

 Set-TransportServer “TRANSPORT SERVER NAME” -SendProtocolLogPath “C:\Directory”

Exchange 2010: Unable to open Exchange Management Console – Initialization Failed

Message:
The attempt to connect to http://exchange.contoso.com’/powershell using ‘Kerberosauthentication failed: Connecting to the remote server failed with the following error message : WinRM cannot process the request…

#1
Close EMC. Open regedit and delete ‘NodeStructureSetting’  from registry: HKEY_CURRENT_USER\SOFTWARE\Microsoft\ExchangeServer\v14\AdminTools.

#2
Make sure that the Kerbauth module (C:\Program Files\Microsoft\Exchange Server\v14\Bin\kerbauth.dll) is not enabled on the default website but is, instead, enabled only for the PowerShell virtual directory.
AND
Make sure that the WSMan module (C:\Windows\system32\wsmsvc.dll) is registered but not enabled at the Server level.

Exchange max e-mail size settings

1. Organization Configuration:

Organization Configuration | Hub Transport | Global Settings tab | Transport Settings

2. Server Configuration:

Server Configuration | Hub Transport | select a HT server | Receive Connectors -> select a connector | Properties

3. Send Connector Configuration

Organization Configuration | Hub Transport | Send Connectors -> select connector | Properties

4. Recipients Configuration:

Recipients Configuration | Mailbox | select mailbox | properties | Mail Flow Settings | Message Size Restrictions

5. Recipients Group Configuration:

Recipients Configuration |Distribution Group | select Group | properties | Mail Flow Settings | Message Size Restrictions

6. Global Setting in ADSIEdit:

Configuration container | Services | Microsoft Exchange |YourOrgName| Global Settings | Message Delivery | Properties

7. Transport Rules:

Organization Configuration | Hub Transport | Transport Rules

 

Exchange 2010: event id 16025 : No DNS servers could be retrieved from network adapter

This Error event indicates the specified network adapter that is configured for internal DNS lookups on the Microsoft Exchange Server Hub Transport server or Edge Transport server is invalid.

To resolve this error, do one of the following:

Open the Exchange Management Console locally on the Hub Transport server or Edge Transport server. Configure the internal DNS lookups to use all available network adapters, or a specific adapter that exists on the Hub Transport server or Edge Transport server.

or

Open the Exchange Management Shell. Run the Get-NetworkConnectionInfo cmdlet locally on the Hub Transport server or Edge Transport server. Note the GUID of the network adapters. Use the GUID of the desired network adapter as the value for the InternalDNSAdapterGUID parameter on the Set-TransportServer cmdlet. If you want to use the DNS settings of all available network adapters, enter a GUID of 00000000-0000-0000-0000-000000000000.

Exchange Server 2010 : Event ID 106 is logged when you start the RPC Client Access service

Error:

Log Name: Application
Source: MSExchange Common
Date: Date_Time_AM_PM
Event ID: 106
Task Category: General
Level: Error
Keywords: Classic
User: N/A
Computer: myExchange2010.example.com
Description:
Performance counter updating error. Counter name is Client: Foreground RPCs Failed, category name is MSExchange RpcClientAccess. Optional code: 3. Exception: The exception thrown is : System.InvalidOperationException: The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly. …

If not, then it should be, solution in Exchange Management Shell:

Add-PSSnapin Microsoft.Exchange.Management.PowerShell.Setup

New-PerfCounters -DefinitionFileName “C:\Program Files\Microsoft\Exchange Server\V14\Setup\Perf\RpcClientAccessPerformanceCounters.xml”

Restart Microsoft Exchange RPC Client Access service.

http://support.microsoft.com/kb/982679/en-us

Exchange 2010 DAG: AddClusterNode() failed with 0x80070005. Error: Access is denied.

If the witness server you specify isn’t an Exchange 2013 Preview or Exchange 2010 server, you must add the Exchange Trusted Subsystem universal security group to the local Administrators group on the witness server. These security permissions are necessary to ensure that Exchange can create a directory and share on the witness server as needed. If the proper permissions aren’t configured, the following error is returned:
Error: An error occurred during discovery of the database availability group topology. Error: An error occurred while attempting a cluster operation. Error: Cluster API “AddClusterNode() (MaxPercentage=12) failed with 0x80070005. Error: Access is denied.”

Update: you must add the Exchange Trusted Subsystem universal security group to the local Administrators group on the source database server.