Solved

Slow mail between Exchange 2010 and 2013

Posted on 2015-02-03
21
609 Views
Last Modified: 2015-02-17
I am in the middle of a migration from Exchange 2010 to Exchange 2013.  Everything seems to be correct and I can send email from and to users on the Exchange 2013.  Mail from and to internet addresses with an exchange 2013 box is fine.  Mail between 2013 exchange accounts is fine.  Mail from an exchange 2013 account to a 2010 account is fine.  Only mail from a 2010 account to a 2013 account is slow.  I cannot figure out what is causing this slowness.  The messages seem to take around 10 minutes to arrive in the 2013 box.

Any help would be appreciated.
0
Comment
Question by:pgoldwasser
  • 13
  • 7
21 Comments
 
LVL 4

Expert Comment

by:Alexander Kireev
ID: 40587048
Hello,
Did you check an email headers to see where the email wait?
Also you can use log tracking.
Both Exchanges into one forest/organization?
You should get the route of this emails.
0
 

Author Comment

by:pgoldwasser
ID: 40587050
Both Exchanges are in the same Forest/Doman/Organization.

I will check a header and see what it shows shortly.
0
 

Author Comment

by:pgoldwasser
ID: 40587057
Here is the header from an email send from administrator@abc.com to nitn@abc.com.  Administrator is on the 2010 Exchange and NITN is on the 2013 exchange.

Received: from ABCEXCHVM2.abc.int (10.10.48.31) by ABCEXCHVM2.abc.int
 (10.10.48.31) with Microsoft SMTP Server (TLS) id 15.0.847.32 via Mailbox
 Transport; Tue, 3 Feb 2015 11:55:03 -0500
Received: from ABCEXCHVM2.abc.int (10.10.48.31) by ABCEXCHVM2.abc.int
 (10.10.48.31) with Microsoft SMTP Server (TLS) id 15.0.847.32; Tue, 3 Feb
 2015 11:49:40 -0500
Received: from ABCEXCH02.abc.int (10.10.48.29) by ABCEXCHVM2.abc.int
 (10.10.48.31) with Microsoft SMTP Server (TLS) id 15.0.847.32 via Frontend
 Transport; Tue, 3 Feb 2015 11:49:40 -0500
Received: from ABCEXCH02.abc.int ([fe80::d805:92cc:6647:f2f4]) by
 ABCEXCH02.abc.int ([fe80::d805:92cc:6647:f2f4%12]) with mapi id
 14.03.0224.002; Tue, 3 Feb 2015 11:49:40 -0500
Content-Type: application/ms-tnef; name="winmail.dat"
Content-Transfer-Encoding: binary
From: Administrator <Administrator@abc.com>
To: NITN <nitn@abc.com>
Subject: RE: test

These two exchange servers are on the same subnet in the same network.  The message seems to just be transferred from one machine to the other.  I just need to know why it took 10 minutes.
0
 
LVL 4

Expert Comment

by:Alexander Kireev
ID: 40587074
The email was on "ABCEXCHVM2.abc.int" server. What about Tracking Log Explorer?
0
 

Author Comment

by:pgoldwasser
ID: 40587438
How do I get to the tracking log explorer?
0
 
LVL 4

Expert Comment

by:Alexander Kireev
ID: 40587849
EMC - Tools - Tracking Log Explorer
Check and enter only Message ID and search. You should get an internal routing of email with date and time.

http://exchangeserverpro.com/exchange-2010-message-tracking/
http://exchangeserverpro.com/exchange-2010-message-tracking-log-search-powershell/
0
 
LVL 3

Expert Comment

by:Sudhir Bidye
ID: 40588162
-Send a email from Exchange 2010 to Exchange 2013 with subject Test101
-Run below command in exchange powershell
get-messagetrackinglogs -sender email address -messagesubject "Test101" | fl and let us know the output of this command
0
 

Author Comment

by:pgoldwasser
ID: 40600714
Sorry I left this for a few days, but it seemed to get better.  It seems that the problem is intermittent and that when the slowness happens, it also seems to happen when a message is sent from the same server.  I have an account on the 2013 exchange and I sent an email to another 2013 user.  I sent the message at about 9:17 and he did not get it until about 9:23.  I did a second test at 9:25 and he got it immediately.  So this is very hard to figure out.

Anyway I ran the above powershell command on a test email that was also sent at 9:16 am this morning and was received at 9:23, the same time as my test that was sent at 9:17.  In face the person got a bunch of emails at that time.  Here is the output of the command:

RunspaceId              : a3af1c96-1002-49b6-9431-611b4a9f4510
Timestamp               : 2/10/2015 9:23:49 AM
ClientIp                :
ClientHostname          : METROEXCHVM2.metro.int
ServerIp                :
ServerHostname          : METROEXCHVM2
SourceContext           : 08D20EBC8C7A2FC1;2015-02-10T14:23:49.777Z;ClientSubmitTime:2015-02-10T14:16:40.746Z
ConnectorId             :
Source                  : STOREDRIVER
EventId                 : DELIVER
InternalMessageId       : 2748779069454
MessageId               : <66BC74FBFBF1944BA41AED7D28EE2B7504F36712@METROEXCH02.metro.int>
Recipients              : {steve@metrotranscription.com}
RecipientStatus         : {}
TotalBytes              : 6474
RecipientCount          : 1
RelatedRecipientAddress :
Reference               :
MessageSubject          : TEST 1
Sender                  : howard@metrotranscription.com
ReturnPath              : howard@metrotranscription.com
Directionality          : Originating
TenantId                :
OriginalClientIp        : 74.102.115.76
MessageInfo             : 2015-02-10T14:16:40.762Z;SRV=METROEXCH02.metro.int:TOTAL=0;SRV=METROEXCH02.metro.int:TOTAL=0;
                          SRV=METROEXCHVM2.metro.int:TOTAL=0;SRV=METROEXCHVM2.metro.int:TOTAL=427|QDM=427;SRV=METROEXCH
                          VM2.metro.int:TOTAL=0
MessageLatency          : 00:07:09.1100000
MessageLatencyType      : EndToEnd
EventData               : {[MailboxDatabaseName, Mailbox Database 0206529253], [Mailboxes,
                          4dc7e802-311d-4041-b8c0-0d27f91b3a57], [E2ELatency, 429], [DeliveryPriority, Normal]}

RunspaceId              : a3af1c96-1002-49b6-9431-611b4a9f4510
Timestamp               : 2/10/2015 9:16:41 AM
ClientIp                :
ClientHostname          :
ServerIp                :
ServerHostname          : METROEXCHVM2
SourceContext           : No suitable shadow servers
ConnectorId             :
Source                  : SMTP
EventId                 : HAREDIRECTFAIL
InternalMessageId       : 2748779069454
MessageId               : <66BC74FBFBF1944BA41AED7D28EE2B7504F36712@METROEXCH02.metro.int>
Recipients              : {steve@metrotranscription.com}
RecipientStatus         : {}
TotalBytes              : 5678
RecipientCount          : 1
RelatedRecipientAddress :
Reference               :
MessageSubject          : TEST 1
Sender                  : howard@metrotranscription.com
ReturnPath              : howard@metrotranscription.com
Directionality          : Originating
TenantId                :
OriginalClientIp        :
MessageInfo             :
MessageLatency          :
MessageLatencyType      : None
EventData               : {[DeliveryPriority, Normal]}

RunspaceId              : a3af1c96-1002-49b6-9431-611b4a9f4510
Timestamp               : 2/10/2015 9:16:41 AM
ClientIp                : 10.10.48.31
ClientHostname          : METROEXCHVM2.metro.int
ServerIp                : 10.10.48.31
ServerHostname          : METROEXCHVM2
SourceContext           : 08D20EBC75E875E3;2015-02-10T14:16:41.420Z;0
ConnectorId             : METROEXCHVM2\Default METROEXCHVM2
Source                  : SMTP
EventId                 : RECEIVE
InternalMessageId       : 2748779069454
MessageId               : <66BC74FBFBF1944BA41AED7D28EE2B7504F36712@METROEXCH02.metro.int>
Recipients              : {steve@metrotranscription.com}
RecipientStatus         : {}
TotalBytes              : 5678
RecipientCount          : 1
RelatedRecipientAddress :
Reference               :
MessageSubject          : TEST 1
Sender                  : howard@metrotranscription.com
ReturnPath              : howard@metrotranscription.com
Directionality          : Originating
TenantId                :
OriginalClientIp        : 74.102.115.76
MessageInfo             : 0cI:
MessageLatency          :
MessageLatencyType      : None
EventData               : {[FirstForestHop, METROEXCHVM2.metro.int], [ProxiedClientIPAddress, 10.10.48.29],
                          [ProxiedClientHostname, METROEXCH02.metro.int], [ProxyHop1,
                          METROEXCHVM2.metro.int(10.10.48.31)], [DeliveryPriority, Normal]}

RunspaceId              : a3af1c96-1002-49b6-9431-611b4a9f4510
Timestamp               : 2/10/2015 9:16:41 AM
ClientIp                :
ClientHostname          : METROEXCHVM2
ServerIp                :
ServerHostname          :
SourceContext           :
ConnectorId             :
Source                  : AGENT
EventId                 : AGENTINFO
InternalMessageId       : 2748779069454
MessageId               : <66BC74FBFBF1944BA41AED7D28EE2B7504F36712@METROEXCH02.metro.int>
Recipients              : {steve@metrotranscription.com}
RecipientStatus         : {}
TotalBytes              : 5757
RecipientCount          : 1
RelatedRecipientAddress :
Reference               :
MessageSubject          : TEST 1
Sender                  : howard@metrotranscription.com
ReturnPath              : howard@metrotranscription.com
Directionality          : Originating
TenantId                :
OriginalClientIp        : 74.102.115.76
MessageInfo             :
MessageLatency          :
MessageLatencyType      : None
EventData               : {[AMA, SUM|v=0|action=|error=|atch=0], [AMA, EV|engine=M|v=0|sig=1.191.4536.0|name=|file=],
                          [CompCost, |AMA=0|ETR=0], [DeliveryPriority, Normal]}

RunspaceId              : a3af1c96-1002-49b6-9431-611b4a9f4510
Timestamp               : 2/10/2015 9:23:49 AM
ClientIp                : 10.10.48.31
ClientHostname          : METROEXCHVM2
ServerIp                : 10.10.48.31
ServerHostname          : METROEXCHVM2.metro.int
SourceContext           : 08D20EBC75E875EA;250 2.0.0 OK;ClientSubmitTime:2015-02-10T14:16:40.746Z
ConnectorId             : Intra-Organization SMTP Send Connector
Source                  : SMTP
EventId                 : SEND
InternalMessageId       : 2748779069454
MessageId               : <66BC74FBFBF1944BA41AED7D28EE2B7504F36712@METROEXCH02.metro.int>
Recipients              : {steve@metrotranscription.com}
RecipientStatus         : {250 2.1.5 Recipient OK}
TotalBytes              : 6480
RecipientCount          : 1
RelatedRecipientAddress :
Reference               :
MessageSubject          : TEST 1
Sender                  : howard@metrotranscription.com
ReturnPath              : howard@metrotranscription.com
Directionality          : Originating
TenantId                :
OriginalClientIp        :
MessageInfo             : 2015-02-10T14:16:40.762Z;LSRV=METROEXCHVM2.metro.int:TOTAL=428|QDM=427
MessageLatency          : 00:07:09.1100000
MessageLatencyType      : LocalServer
EventData               : {[E2ELatency, 429], [Microsoft.Exchange.Transport.MailRecipient.RequiredTlsAuthLevel,
                          Opportunistic], [DeliveryPriority, Normal]}
0
 
LVL 4

Expert Comment

by:Alexander Kireev
ID: 40601155
What we can see there is a source of the problem is HAREDIRECTFAIL.
Do you use Shadow Redundancy?

I propose you to read the articles (https://technet.microsoft.com/en-us/library/dd351027%28v=exchg.150%29.aspx https://technet.microsoft.com/en-us/library/dd351046%28v=exchg.141%29.aspx) about it and decide - do you need the Shadow Redundancy or not.

If not, you can disable it: Set-TransportConfig -ShadowRedundancyEnabled $true


Timestamp               : 2/10/2015 9:23:49 AM
EventId                 : SEND

Timestamp               : 2/10/2015 9:23:49 AM
EventId                 : DELIVER

Timestamp               : 2/10/2015 9:16:41 AM
EventId                 : HAREDIRECTFAIL

Timestamp               : 2/10/2015 9:16:41 AM
EventId                 : RECEIVE

Timestamp               : 2/10/2015 9:16:41 AM
EventId                 : AGENTINFO


HAREDIRECTFAIL indicates that a shadow message failed to be created. This means that the transport service failed at trying to make the specific message redundant (while in transit) at another Exchange 2013 mailbox server (transport service) for whatever reason, probably stated in the source-context field.

So, the mentioned redirection isn't like forwarding at all but rather a protection mechanism for messages in transit. After the message has been successfully delivered, it's called Safety Net. Basically your safe guard isn't functioning for whatever reason, but hopefully message delivery is.

There is more to read up on these HA features here: Transport High Availability
0
 

Author Comment

by:pgoldwasser
ID: 40603155
So this did not seem to help.  I sent an email to the person from an exchange 2013 email account at 8:12 pm and he did not receive until 8:21.  I followed the instructions to turn off shadow redundancy and in fact in the message tracking log that you see below the errors from the previous log is not there.  Can you help me figure this out?

RunspaceId              : 8c14930e-e22b-4968-ac92-9650b0fe8bda
Timestamp               : 2/10/2015 8:12:41 PM
ClientIp                :
ClientHostname          : METROEXCHVM2.metro.int
ServerIp                :
ServerHostname          : METROEXCHVM2
SourceContext           : 08D20EBC8C7A33FC;2015-02-11T01:12:41.473Z;ClientSubmitTime:2015-02-11T01:12:40.207Z
ConnectorId             :
Source                  : STOREDRIVER
EventId                 : DELIVER
InternalMessageId       : 2796023709707
MessageId               : <7322a0b95d37444995ed598347437e84@METROEXCHVM2.metro.int>
Recipients              : {steve@metrotranscription.com}
RecipientStatus         : {}
TotalBytes              : 11650
RecipientCount          : 1
RelatedRecipientAddress :
Reference               :
MessageSubject          : Password
Sender                  : nitn@metrotranscription.com
ReturnPath              : nitn@metrotranscription.com
Directionality          : Originating
TenantId                :
OriginalClientIp        : 108.53.251.105
MessageInfo             : 2015-02-11T01:12:40.207Z;SRV=METROEXCHVM2.metro.int:TOTAL=0;SRV=METROEXCHVM2.metro.int:TOTAL=
                          0;SRV=METROEXCHVM2.metro.int:TOTAL=0;SRV=METROEXCHVM2.metro.int:TOTAL=0
MessageLatency          : 00:00:01.3750000
MessageLatencyType      : EndToEnd
EventData               : {[MailboxDatabaseName, Mailbox Database 0206529253], [Mailboxes,
                          4dc7e802-311d-4041-b8c0-0d27f91b3a57], [E2ELatency, 1], [DeliveryPriority, Normal]}

RunspaceId              : 8c14930e-e22b-4968-ac92-9650b0fe8bda
Timestamp               : 2/10/2015 8:12:40 PM
ClientIp                : fe80::f81e:64f8:490f:7829
ClientHostname          : METROEXCHVM2.metro.int
ServerIp                : fe80::f81e:64f8:490f:7829%12
ServerHostname          : METROEXCHVM2
SourceContext           : 08D20EBC6F140CCE
ConnectorId             :
Source                  : STOREDRIVER
EventId                 : RECEIVE
InternalMessageId       : 0
MessageId               : <7322a0b95d37444995ed598347437e84@METROEXCHVM2.metro.int>
Recipients              : {howard@metrotranscription.com, steve@metrotranscription.com}
RecipientStatus         : {Cc, To}
TotalBytes              : 9470
RecipientCount          : 2
RelatedRecipientAddress :
Reference               :
MessageSubject          : Password
Sender                  : nitn@metrotranscription.com
ReturnPath              : nitn@metrotranscription.com
Directionality          : Originating
TenantId                :
OriginalClientIp        : 108.53.251.105
MessageInfo             : 04I:
MessageLatency          :
MessageLatencyType      : None
EventData               : {[MailboxDatabaseGuid, 98ea4566-0cc9-4e87-b714-1e8f18296932], [ItemEntryId, 00-00-00-00-3B-98
                          -E9-43-63-9E-B2-4B-BB-8B-98-7A-68-54-A5-1C-07-00-45-30-4A-81-F6-79-40-4C-8E-2D-3C-C8-8F-9F-7D
                          -B0-00-00-00-02-73-B2-00-00-E7-91-EA-3E-FA-BF-5E-4A-82-73-33-79-03-44-70-FC-00-00-08-AD-78-24
                          -00-00], [DeliveryPriority, Normal]}

RunspaceId              : 8c14930e-e22b-4968-ac92-9650b0fe8bda
Timestamp               : 2/10/2015 8:12:41 PM
ClientIp                : fe80::f81e:64f8:490f:7829%12
ClientHostname          : METROEXCHVM2
ServerIp                :
ServerHostname          : METROEXCHVM2.metro.int
SourceContext           : MDB:98ea4566-0cc9-4e87-b714-1e8f18296932, Mailbox:a051da50-8730-45dd-92f6-275be96572fc,
                          Event:649318, MessageClass:IPM.Note, CreationTime:2015-02-11T01:12:40.207Z, ClientType:OWA
ConnectorId             :
Source                  : STOREDRIVER
EventId                 : SUBMIT
InternalMessageId       :
MessageId               : <7322a0b95d37444995ed598347437e84@METROEXCHVM2.metro.int>
Recipients              : {howard@metrotranscription.com, steve@metrotranscription.com}
RecipientStatus         : {}
TotalBytes              :
RecipientCount          : 2
RelatedRecipientAddress :
Reference               :
MessageSubject          : Password
Sender                  : nitn@metrotranscription.com
ReturnPath              :
Directionality          : Originating
TenantId                :
OriginalClientIp        : 108.53.251.105
MessageInfo             : 2015-02-11T01:12:40.207Z;LSRV=METROEXCHVM2.metro.int:TOTAL=1
MessageLatency          : 00:00:01
MessageLatencyType      : LocalServer
EventData               : {[ItemEntryId, 00-00-00-00-3B-98-E9-43-63-9E-B2-4B-BB-8B-98-7A-68-54-A5-1C-07-00-45-30-4A-81-
                          F6-79-40-4C-8E-2D-3C-C8-8F-9F-7D-B0-00-00-00-02-73-B2-00-00-E7-91-EA-3E-FA-BF-5E-4A-82-73-33-
                          79-03-44-70-FC-00-00-08-AD-78-24-00-00]}

RunspaceId              : 8c14930e-e22b-4968-ac92-9650b0fe8bda
Timestamp               : 2/10/2015 8:12:41 PM
ClientIp                : 10.10.48.31
ClientHostname          : METROEXCHVM2.metro.int
ServerIp                : 10.10.48.31
ServerHostname          : METROEXCHVM2
SourceContext           : 08D20EBC75E8782C;2015-02-11T01:12:40.676Z;0
ConnectorId             : METROEXCHVM2\Default METROEXCHVM2
Source                  : SMTP
EventId                 : RECEIVE
InternalMessageId       : 2796023709707
MessageId               : <7322a0b95d37444995ed598347437e84@METROEXCHVM2.metro.int>
Recipients              : {howard@metrotranscription.com, steve@metrotranscription.com}
RecipientStatus         : {}
TotalBytes              : 10038
RecipientCount          : 2
RelatedRecipientAddress :
Reference               :
MessageSubject          : Password
Sender                  : nitn@metrotranscription.com
ReturnPath              : nitn@metrotranscription.com
Directionality          : Originating
TenantId                :
OriginalClientIp        : 108.53.251.105
MessageInfo             : 0cI:
MessageLatency          :
MessageLatencyType      : None
EventData               : {[FirstForestHop, METROEXCHVM2.metro.int], [DeliveryPriority, Normal]}

RunspaceId              : 8c14930e-e22b-4968-ac92-9650b0fe8bda
Timestamp               : 2/10/2015 8:12:41 PM
ClientIp                :
ClientHostname          : METROEXCHVM2
ServerIp                :
ServerHostname          :
SourceContext           :
ConnectorId             :
Source                  : AGENT
EventId                 : AGENTINFO
InternalMessageId       : 2796023709707
MessageId               : <7322a0b95d37444995ed598347437e84@METROEXCHVM2.metro.int>
Recipients              : {howard@metrotranscription.com, steve@metrotranscription.com}
RecipientStatus         : {}
TotalBytes              : 11581
RecipientCount          : 2
RelatedRecipientAddress :
Reference               :
MessageSubject          : Password
Sender                  : nitn@metrotranscription.com
ReturnPath              : nitn@metrotranscription.com
Directionality          : Originating
TenantId                :
OriginalClientIp        : 108.53.251.105
MessageInfo             :
MessageLatency          :
MessageLatencyType      : None
EventData               : {[AMA, SUM|v=0|action=|error=|atch=0], [AMA, EV|engine=M|v=0|sig=1.191.4583.0|name=|file=],
                          [CompCost, |AMA=0|ETR=0], [DeliveryPriority, Normal]}

RunspaceId              : 8c14930e-e22b-4968-ac92-9650b0fe8bda
Timestamp               : 2/10/2015 8:12:41 PM
ClientIp                : 10.10.48.31
ClientHostname          : METROEXCHVM2
ServerIp                : 10.10.48.31
ServerHostname          : METROEXCHVM2.metro.int
SourceContext           : 08D20EBC75E8782D;250 2.0.0 OK;ClientSubmitTime:2015-02-11T01:12:40.207Z
ConnectorId             : Intra-Organization SMTP Send Connector
Source                  : SMTP
EventId                 : SEND
InternalMessageId       : 2796023709707
MessageId               : <7322a0b95d37444995ed598347437e84@METROEXCHVM2.metro.int>
Recipients              : {steve@metrotranscription.com}
RecipientStatus         : {250 2.1.5 Recipient OK}
TotalBytes              : 11650
RecipientCount          : 1
RelatedRecipientAddress :
Reference               :
MessageSubject          : Password
Sender                  : nitn@metrotranscription.com
ReturnPath              : nitn@metrotranscription.com
Directionality          : Originating
TenantId                :
OriginalClientIp        :
MessageInfo             : 2015-02-11T01:12:40.207Z;LSRV=METROEXCHVM2.metro.int:TOTAL=0
MessageLatency          : 00:00:01.3750000
MessageLatencyType      : LocalServer
EventData               : {[E2ELatency, 1], [Microsoft.Exchange.Transport.MailRecipient.RequiredTlsAuthLevel,
                          Opportunistic], [DeliveryPriority, Normal]}

RunspaceId              : 8c14930e-e22b-4968-ac92-9650b0fe8bda
Timestamp               : 2/10/2015 8:12:42 PM
ClientIp                :
ClientHostname          :
ServerIp                :
ServerHostname          : METROEXCHVM2
SourceContext           : resubmitting in Delivery
ConnectorId             :
Source                  : QUEUE
EventId                 : RESUBMIT
InternalMessageId       : 2796023709707
MessageId               : <7322a0b95d37444995ed598347437e84@METROEXCHVM2.metro.int>
Recipients              : {steve@metrotranscription.com, howard@metrotranscription.com}
RecipientStatus         : {250 2.1.5 Recipient OK, }
TotalBytes              : 11650
RecipientCount          : 2
RelatedRecipientAddress :
Reference               : {2796023709707}
MessageSubject          : Password
Sender                  : nitn@metrotranscription.com
ReturnPath              : nitn@metrotranscription.com
Directionality          :
TenantId                :
OriginalClientIp        :
MessageInfo             :
MessageLatency          :
MessageLatencyType      : None
EventData               :

RunspaceId              : 8c14930e-e22b-4968-ac92-9650b0fe8bda
Timestamp               : 2/10/2015 8:12:42 PM
ClientIp                :
ClientHostname          : METROEXCHVM2
ServerIp                :
ServerHostname          :
SourceContext           :
ConnectorId             :
Source                  : AGENT
EventId                 : AGENTINFO
InternalMessageId       : 2796023709707
MessageId               : <7322a0b95d37444995ed598347437e84@METROEXCHVM2.metro.int>
Recipients              : {steve@metrotranscription.com, howard@metrotranscription.com}
RecipientStatus         : {}
TotalBytes              : 11650
RecipientCount          : 2
RelatedRecipientAddress :
Reference               :
MessageSubject          : Password
Sender                  : nitn@metrotranscription.com
ReturnPath              : nitn@metrotranscription.com
Directionality          : Originating
TenantId                :
OriginalClientIp        : 108.53.251.105
MessageInfo             :
MessageLatency          :
MessageLatencyType      : None
EventData               : {[AMA, SUM|action=p|error=|atch=0], [CompCost, |ETR=0], [DeliveryPriority, Normal]}

RunspaceId              : 8c14930e-e22b-4968-ac92-9650b0fe8bda
Timestamp               : 2/10/2015 8:21:48 PM
ClientIp                : 10.10.48.31
ClientHostname          : METROEXCHVM2
ServerIp                : 10.10.48.29
ServerHostname          : METROEXCH02.metro.int
SourceContext           : 08D20EBC75E87839;250 2.6.0 <7322a0b95d37444995ed598347437e84@METROEXCHVM2.metro.int>
                          [InternalId=10958] Queued mail for delivery;ClientSubmitTime:2015-02-11T01:12:40.207Z
ConnectorId             : Intra-Organization SMTP Send Connector
Source                  : SMTP
EventId                 : SEND
InternalMessageId       : 2796023709707
MessageId               : <7322a0b95d37444995ed598347437e84@METROEXCHVM2.metro.int>
Recipients              : {howard@metrotranscription.com}
RecipientStatus         : {250 2.1.5 Recipient OK}
TotalBytes              : 11654
RecipientCount          : 1
RelatedRecipientAddress :
Reference               :
MessageSubject          : Password
Sender                  : nitn@metrotranscription.com
ReturnPath              : nitn@metrotranscription.com
Directionality          : Originating
TenantId                :
OriginalClientIp        :
MessageInfo             : 2015-02-11T01:12:40.207Z;LSRV=METROEXCHVM2.metro.int:TOTAL=547|QDI=546;QDI
MessageLatency          : 00:09:08.5910000
MessageLatencyType      : LocalServer
EventData               : {[E2ELatency, 549], [Microsoft.Exchange.Transport.MailRecipient.RequiredTlsAuthLevel,
                          Opportunistic], [DeliveryPriority, Normal]}
0
How to improve team productivity

Quip adds documents, spreadsheets, and tasklists to your Slack experience
- Elevate ideas to Quip docs
- Share Quip docs in Slack
- Get notified of changes to your docs
- Available on iOS/Android/Desktop/Web
- Online/Offline

 
LVL 4

Expert Comment

by:Alexander Kireev
ID: 40603830
Now I see an error on "Intra-Organization SMTP Send Connector" with delay 9 minutes.
This email was sent within a single server?
What happens with cross-servers emails (2010 - 2013) after that you disable Shadow Redundancy?

Which CU on 2013 you are using?
Did you have huge mail queue?
Try to increase a logging level to maximum for "Transport service" and "Mail Transport Service" and look into Event Log.


2/10/2015 8:12:41 PM            METROEXCHVM2            STOREDRIVER            DELIVER                  00:00:01.3750000
2/10/2015 8:12:40 PM            METROEXCHVM2            STOREDRIVER            RECEIVE                  
2/10/2015 8:12:41 PM            METROEXCHVM2            STOREDRIVER            SUBMIT                  00:00:01
2/10/2015 8:12:41 PM            METROEXCHVM2            SMTP                  RECEIVE                  
2/10/2015 8:12:41 PM            METROEXCHVM2            AGENT                  AGENTINFO            
2/10/2015 8:12:41 PM            METROEXCHVM2            SMTP                  SEND                  00:00:01.3750000
2/10/2015 8:12:42 PM            METROEXCHVM2            QUEUE                  RESUBMIT            
2/10/2015 8:12:42 PM            METROEXCHVM2            AGENT                  AGENTINFO            
2/10/2015 8:21:48 PM            METROEXCHVM2            SMTP                  SEND                  00:09:08.5910000
0
 

Author Comment

by:pgoldwasser
ID: 40604165
This was actually between two exchange servers, 2010 and 2013.  It was sent from nitn@metrotranscription.com which is on the 2013 server and sent to steve@ and howard@.  Steve@ is on the 2013 server and howard@ is on the 2010.  Steve got the message immediately, and howard got it nine minutes later.  This was all after I turned off shadow redundancy.

Which CU on 2013 you are using?
Not sure what this means
Did you have huge mail queue?
No the mail queue is pretty small, especially on the 2013 server where there are only three users at the moment.
Try to increase a logging level to maximum for "Transport service" and "Mail Transport Service" and look into Event Log.
Not sure how to do this.
0
 
LVL 4

Expert Comment

by:Alexander Kireev
ID: 40604954
First of all I recommend upgrade your Exchange 2013 to the latest CU (Cumulative update). You need it any way.
https://technet.microsoft.com/en-us/library/jj983803%28v=exchg.150%29.aspx
http://www.microsoft.com/en-us/download/details.aspx?id=45221

Then use "Exchange 2013 Best Practices Analyzer" for checking your environment for Best Practices.
http://community.office365.com/en-us/w/deploy/office-365-best-practices-analyzer-for-exchange-server-2013.aspx
https://justaucguy.wordpress.com/2014/02/28/exchange-2013-service-pack-1-best-practices-analyzer-updated/

Then follow recommendation from BPA.

Then increase the Diagnostic Level for "MSExchangeTransport\SmtpReceive", "MSExchangeTransport\SmtpSend", "MSExchangeTransport\Routing" and "MSExchangeTransport\TransportService" to maximum, send test email again and look into Event Log for errors or warnings. Don't forget decrease it after.  
https://technet.microsoft.com/en-us/library/aa998905%28v=exchg.150%29.aspx
0
 

Author Comment

by:pgoldwasser
ID: 40605427
BPA tells me that OutlookRpcSelfTestMonitor is Unhealthy.  I tried looking that up but could not find any info on it.  

I also get an error that I have to have Office 365 admin credentials to evaluate the Office 265 configuration.  I assume I can forget that one as I do not have Office 365.

Then I get a ton of warnings and informational entries.  I will upload the HTML file with this so you can take a look.  I am lost with this stuff.

Thanks for all of your help!
BPATestResults.html
0
 

Author Comment

by:pgoldwasser
ID: 40605687
I sent another email this morning from  a 2013 account to two 2010 accounts and one 2013 account.  I sent it at 9:26 and one of the 2010 accounts received it at 9:29.  Not horrible, but still too slow.  Earlier the testing was immediate.  Here is the message tracking log (I did increase the logging as above).

RunspaceId              : 5b92b001-0315-4b67-bb01-77a38f207422
Timestamp               : 2/12/2015 9:27:07 AM
ClientIp                : fe80::f81e:64f8:490f:7829
ClientHostname          : METROEXCHVM2.metro.int
ServerIp                : fe80::f81e:64f8:490f:7829%12
ServerHostname          : METROEXCHVM2
SourceContext           : 08D214D22E2C75F7
ConnectorId             :
Source                  : STOREDRIVER
EventId                 : RECEIVE
InternalMessageId       : 0
MessageId               : <5d94c920ea124a4ba1deb7a12d563698@METROEXCHVM2.metro.int>
Recipients              : {steve@metrotranscription.com, howard@metrotranscription.com,
                          Administrator@metrotranscription.com}
RecipientStatus         : {To, Cc, Cc}
TotalBytes              : 6582
RecipientCount          : 3
RelatedRecipientAddress :
Reference               :
MessageSubject          : Testing 9:26
Sender                  : nitn@metrotranscription.com
ReturnPath              : nitn@metrotranscription.com
Directionality          : Originating
TenantId                :
OriginalClientIp        : 108.53.251.105
MessageInfo             : 04I:
MessageLatency          :
MessageLatencyType      : None
EventData               : {[MailboxDatabaseGuid, 98ea4566-0cc9-4e87-b714-1e8f18296932], [ItemEntryId, 00-00-00-00-3B-98
                          -E9-43-63-9E-B2-4B-BB-8B-98-7A-68-54-A5-1C-07-00-45-30-4A-81-F6-79-40-4C-8E-2D-3C-C8-8F-9F-7D
                          -B0-00-00-00-02-73-B2-00-00-E7-91-EA-3E-FA-BF-5E-4A-82-73-33-79-03-44-70-FC-00-00-0D-C8-DE-B6
                          -00-00], [DeliveryPriority, Normal], [AccountForest, metro.int]}

RunspaceId              : 5b92b001-0315-4b67-bb01-77a38f207422
Timestamp               : 2/12/2015 9:27:07 AM
ClientIp                : fe80::f81e:64f8:490f:7829%12
ClientHostname          : METROEXCHVM2
ServerIp                :
ServerHostname          : METROEXCHVM2.metro.int
SourceContext           : MDB:98ea4566-0cc9-4e87-b714-1e8f18296932, Mailbox:a051da50-8730-45dd-92f6-275be96572fc,
                          Event:712372, MessageClass:IPM.Note, CreationTime:2015-02-12T14:27:06.992Z, ClientType:OWA
ConnectorId             :
Source                  : STOREDRIVER
EventId                 : SUBMIT
InternalMessageId       :
MessageId               : <5d94c920ea124a4ba1deb7a12d563698@METROEXCHVM2.metro.int>
Recipients              : {steve@metrotranscription.com, howard@metrotranscription.com,
                          Administrator@metrotranscription.com}
RecipientStatus         : {}
TotalBytes              :
RecipientCount          : 3
RelatedRecipientAddress :
Reference               :
MessageSubject          : Testing 9:26
Sender                  : nitn@metrotranscription.com
ReturnPath              :
Directionality          : Originating
TenantId                :
OriginalClientIp        : 108.53.251.105
MessageInfo             : 2015-02-12T14:27:06.992Z;LSRV=METROEXCHVM2.metro.int:TOTAL-SUB=0.281|SA=0.015|MTSSDPL=0.042|M
                          TSSDSS=0.025
MessageLatency          : 00:00:00.2810000
MessageLatencyType      : LocalServer
EventData               : {[ItemEntryId, 00-00-00-00-3B-98-E9-43-63-9E-B2-4B-BB-8B-98-7A-68-54-A5-1C-07-00-45-30-4A-81-
                          F6-79-40-4C-8E-2D-3C-C8-8F-9F-7D-B0-00-00-00-02-73-B2-00-00-E7-91-EA-3E-FA-BF-5E-4A-82-73-33-
                          79-03-44-70-FC-00-00-0D-C8-DE-B6-00-00]}

RunspaceId              : 5b92b001-0315-4b67-bb01-77a38f207422
Timestamp               : 2/12/2015 9:27:07 AM
ClientIp                : 10.10.48.31
ClientHostname          : METROEXCHVM2.metro.int
ServerIp                : 10.10.48.31
ServerHostname          : METROEXCHVM2
SourceContext           : 08D214D242C253B8;2015-02-12T14:27:07.086Z;0
ConnectorId             : METROEXCHVM2\Default METROEXCHVM2
Source                  : SMTP
EventId                 : RECEIVE
InternalMessageId       : 2950642532408
MessageId               : <5d94c920ea124a4ba1deb7a12d563698@METROEXCHVM2.metro.int>
Recipients              : {steve@metrotranscription.com, howard@metrotranscription.com,
                          Administrator@metrotranscription.com}
RecipientStatus         : {}
TotalBytes              : 7192
RecipientCount          : 3
RelatedRecipientAddress :
Reference               :
MessageSubject          : Testing 9:26
Sender                  : nitn@metrotranscription.com
ReturnPath              : nitn@metrotranscription.com
Directionality          : Originating
TenantId                :
OriginalClientIp        : 108.53.251.105
MessageInfo             : 0cI:
MessageLatency          :
MessageLatencyType      : None
EventData               : {[FirstForestHop, METROEXCHVM2.metro.int], [DeliveryPriority, Normal], [AccountForest,
                          metro.int]}

RunspaceId              : 5b92b001-0315-4b67-bb01-77a38f207422
Timestamp               : 2/12/2015 9:27:07 AM
ClientIp                :
ClientHostname          : METROEXCHVM2
ServerIp                :
ServerHostname          :
SourceContext           :
ConnectorId             :
Source                  : AGENT
EventId                 : AGENTINFO
InternalMessageId       : 2950642532408
MessageId               : <5d94c920ea124a4ba1deb7a12d563698@METROEXCHVM2.metro.int>
Recipients              : {steve@metrotranscription.com, howard@metrotranscription.com,
                          Administrator@metrotranscription.com}
RecipientStatus         : {}
TotalBytes              : 8708
RecipientCount          : 3
RelatedRecipientAddress :
Reference               :
MessageSubject          : Testing 9:26
Sender                  : nitn@metrotranscription.com
ReturnPath              : nitn@metrotranscription.com
Directionality          : Originating
TenantId                :
OriginalClientIp        : 108.53.251.105
MessageInfo             :
MessageLatency          :
MessageLatencyType      : None
EventData               : {[AMA, SUM|v=0|action=|error=|atch=0], [AMA, EV|engine=M|v=0|sig=1.191.4757.0|name=|file=],
                          [CompCost, |AMA=0|ETR=0], [DeliveryPriority, Normal], [AccountForest, metro.int]}

RunspaceId              : 5b92b001-0315-4b67-bb01-77a38f207422
Timestamp               : 2/12/2015 9:29:15 AM
ClientIp                : 10.10.48.31
ClientHostname          : METROEXCHVM2
ServerIp                : 10.10.48.29
ServerHostname          : METROEXCH02.metro.int
SourceContext           : ;250 2.6.0 <5d94c920ea124a4ba1deb7a12d563698@METROEXCHVM2.metro.int> [InternalId=11657]
                          Queued mail for delivery;ClientSubmitTime:2015-02-12T14:27:06.977Z
ConnectorId             : Intra-Organization SMTP Send Connector
Source                  : SMTP
EventId                 : SEND
InternalMessageId       : 2950642532408
MessageId               : <5d94c920ea124a4ba1deb7a12d563698@METROEXCHVM2.metro.int>
Recipients              : {Administrator@metrotranscription.com, howard@metrotranscription.com}
RecipientStatus         : {250 2.1.5 Recipient OK, 250 2.1.5 Recipient OK}
TotalBytes              : 8757
RecipientCount          : 2
RelatedRecipientAddress :
Reference               : {, }
MessageSubject          : Testing 9:26
Sender                  : nitn@metrotranscription.com
ReturnPath              : nitn@metrotranscription.com
Directionality          : Originating
TenantId                :
OriginalClientIp        :
MessageInfo             : 2015-02-12T14:27:06.992Z;LSRV=METROEXCHVM2.metro.int:TOTAL-HUB=128.353
MessageLatency          : 00:02:08.4630000
MessageLatencyType      : LocalServer
EventData               : {[E2ELatency, 128.463], [Microsoft.Exchange.Transport.MailRecipient.RequiredTlsAuthLevel,
                          Opportunistic], [DeliveryPriority, Normal], [AccountForest, metro.int]}

Here is the tracking for an email I sent from a 2013 account to another 2013 account.  I sent at 9:45 am and it is now 9:50 and it has not yet been received.

RunspaceId              : 5b92b001-0315-4b67-bb01-77a38f207422
Timestamp               : 2/12/2015 9:27:07 AM
ClientIp                : fe80::f81e:64f8:490f:7829
ClientHostname          : METROEXCHVM2.metro.int
ServerIp                : fe80::f81e:64f8:490f:7829%12
ServerHostname          : METROEXCHVM2
SourceContext           : 08D214D22E2C75F7
ConnectorId             :
Source                  : STOREDRIVER
EventId                 : RECEIVE
InternalMessageId       : 0
MessageId               : <5d94c920ea124a4ba1deb7a12d563698@METROEXCHVM2.metro.int>
Recipients              : {steve@metrotranscription.com, howard@metrotranscription.com,
                          Administrator@metrotranscription.com}
RecipientStatus         : {To, Cc, Cc}
TotalBytes              : 6582
RecipientCount          : 3
RelatedRecipientAddress :
Reference               :
MessageSubject          : Testing 9:26
Sender                  : nitn@metrotranscription.com
ReturnPath              : nitn@metrotranscription.com
Directionality          : Originating
TenantId                :
OriginalClientIp        : 108.53.251.105
MessageInfo             : 04I:
MessageLatency          :
MessageLatencyType      : None
EventData               : {[MailboxDatabaseGuid, 98ea4566-0cc9-4e87-b714-1e8f18296932], [ItemEntryId, 00-00-00-00-3B-98
                          -E9-43-63-9E-B2-4B-BB-8B-98-7A-68-54-A5-1C-07-00-45-30-4A-81-F6-79-40-4C-8E-2D-3C-C8-8F-9F-7D
                          -B0-00-00-00-02-73-B2-00-00-E7-91-EA-3E-FA-BF-5E-4A-82-73-33-79-03-44-70-FC-00-00-0D-C8-DE-B6
                          -00-00], [DeliveryPriority, Normal], [AccountForest, metro.int]}

RunspaceId              : 5b92b001-0315-4b67-bb01-77a38f207422
Timestamp               : 2/12/2015 9:27:07 AM
ClientIp                : fe80::f81e:64f8:490f:7829%12
ClientHostname          : METROEXCHVM2
ServerIp                :
ServerHostname          : METROEXCHVM2.metro.int
SourceContext           : MDB:98ea4566-0cc9-4e87-b714-1e8f18296932, Mailbox:a051da50-8730-45dd-92f6-275be96572fc,
                          Event:712372, MessageClass:IPM.Note, CreationTime:2015-02-12T14:27:06.992Z, ClientType:OWA
ConnectorId             :
Source                  : STOREDRIVER
EventId                 : SUBMIT
InternalMessageId       :
MessageId               : <5d94c920ea124a4ba1deb7a12d563698@METROEXCHVM2.metro.int>
Recipients              : {steve@metrotranscription.com, howard@metrotranscription.com,
                          Administrator@metrotranscription.com}
RecipientStatus         : {}
TotalBytes              :
RecipientCount          : 3
RelatedRecipientAddress :
Reference               :
MessageSubject          : Testing 9:26
Sender                  : nitn@metrotranscription.com
ReturnPath              :
Directionality          : Originating
TenantId                :
OriginalClientIp        : 108.53.251.105
MessageInfo             : 2015-02-12T14:27:06.992Z;LSRV=METROEXCHVM2.metro.int:TOTAL-SUB=0.281|SA=0.015|MTSSDPL=0.042|M
                          TSSDSS=0.025
MessageLatency          : 00:00:00.2810000
MessageLatencyType      : LocalServer
EventData               : {[ItemEntryId, 00-00-00-00-3B-98-E9-43-63-9E-B2-4B-BB-8B-98-7A-68-54-A5-1C-07-00-45-30-4A-81-
                          F6-79-40-4C-8E-2D-3C-C8-8F-9F-7D-B0-00-00-00-02-73-B2-00-00-E7-91-EA-3E-FA-BF-5E-4A-82-73-33-
                          79-03-44-70-FC-00-00-0D-C8-DE-B6-00-00]}

RunspaceId              : 5b92b001-0315-4b67-bb01-77a38f207422
Timestamp               : 2/12/2015 9:27:07 AM
ClientIp                : 10.10.48.31
ClientHostname          : METROEXCHVM2.metro.int
ServerIp                : 10.10.48.31
ServerHostname          : METROEXCHVM2
SourceContext           : 08D214D242C253B8;2015-02-12T14:27:07.086Z;0
ConnectorId             : METROEXCHVM2\Default METROEXCHVM2
Source                  : SMTP
EventId                 : RECEIVE
InternalMessageId       : 2950642532408
MessageId               : <5d94c920ea124a4ba1deb7a12d563698@METROEXCHVM2.metro.int>
Recipients              : {steve@metrotranscription.com, howard@metrotranscription.com,
                          Administrator@metrotranscription.com}
RecipientStatus         : {}
TotalBytes              : 7192
RecipientCount          : 3
RelatedRecipientAddress :
Reference               :
MessageSubject          : Testing 9:26
Sender                  : nitn@metrotranscription.com
ReturnPath              : nitn@metrotranscription.com
Directionality          : Originating
TenantId                :
OriginalClientIp        : 108.53.251.105
MessageInfo             : 0cI:
MessageLatency          :
MessageLatencyType      : None
EventData               : {[FirstForestHop, METROEXCHVM2.metro.int], [DeliveryPriority, Normal], [AccountForest,
                          metro.int]}

RunspaceId              : 5b92b001-0315-4b67-bb01-77a38f207422
Timestamp               : 2/12/2015 9:27:07 AM
ClientIp                :
ClientHostname          : METROEXCHVM2
ServerIp                :
ServerHostname          :
SourceContext           :
ConnectorId             :
Source                  : AGENT
EventId                 : AGENTINFO
InternalMessageId       : 2950642532408
MessageId               : <5d94c920ea124a4ba1deb7a12d563698@METROEXCHVM2.metro.int>
Recipients              : {steve@metrotranscription.com, howard@metrotranscription.com,
                          Administrator@metrotranscription.com}
RecipientStatus         : {}
TotalBytes              : 8708
RecipientCount          : 3
RelatedRecipientAddress :
Reference               :
MessageSubject          : Testing 9:26
Sender                  : nitn@metrotranscription.com
ReturnPath              : nitn@metrotranscription.com
Directionality          : Originating
TenantId                :
OriginalClientIp        : 108.53.251.105
MessageInfo             :
MessageLatency          :
MessageLatencyType      : None
EventData               : {[AMA, SUM|v=0|action=|error=|atch=0], [AMA, EV|engine=M|v=0|sig=1.191.4757.0|name=|file=],
                          [CompCost, |AMA=0|ETR=0], [DeliveryPriority, Normal], [AccountForest, metro.int]}

RunspaceId              : 5b92b001-0315-4b67-bb01-77a38f207422
Timestamp               : 2/12/2015 9:29:15 AM
ClientIp                : 10.10.48.31
ClientHostname          : METROEXCHVM2
ServerIp                : 10.10.48.29
ServerHostname          : METROEXCH02.metro.int
SourceContext           : ;250 2.6.0 <5d94c920ea124a4ba1deb7a12d563698@METROEXCHVM2.metro.int> [InternalId=11657]
                          Queued mail for delivery;ClientSubmitTime:2015-02-12T14:27:06.977Z
ConnectorId             : Intra-Organization SMTP Send Connector
Source                  : SMTP
EventId                 : SEND
InternalMessageId       : 2950642532408
MessageId               : <5d94c920ea124a4ba1deb7a12d563698@METROEXCHVM2.metro.int>
Recipients              : {Administrator@metrotranscription.com, howard@metrotranscription.com}
RecipientStatus         : {250 2.1.5 Recipient OK, 250 2.1.5 Recipient OK}
TotalBytes              : 8757
RecipientCount          : 2
RelatedRecipientAddress :
Reference               : {, }
MessageSubject          : Testing 9:26
Sender                  : nitn@metrotranscription.com
ReturnPath              : nitn@metrotranscription.com
Directionality          : Originating
TenantId                :
OriginalClientIp        :
MessageInfo             : 2015-02-12T14:27:06.992Z;LSRV=METROEXCHVM2.metro.int:TOTAL-HUB=128.353
MessageLatency          : 00:02:08.4630000
MessageLatencyType      : LocalServer
EventData               : {[E2ELatency, 128.463], [Microsoft.Exchange.Transport.MailRecipient.RequiredTlsAuthLevel,
                          Opportunistic], [DeliveryPriority, Normal], [AccountForest, metro.int]}

There is something very fishy going on here and I need to figure this out.  I have one production user who is on the 2013 server and this is a big hardship.

Thanks
0
 

Author Comment

by:pgoldwasser
ID: 40605699
One last update:  At 9:53 am, a bunch of messages that had been sent in the past 20 minutes were received by my 2013 account.
0
 

Author Comment

by:pgoldwasser
ID: 40605756
One more piece of info.  When I send the email from 2013 OWA (we have only been using OWA), it sits as a draft for a few minutes before it goes.  This seems to be a telltale sign that the email will be delayed.
0
 
LVL 4

Expert Comment

by:Alexander Kireev
ID: 40606478
Did you upgrade your Exchange 2013 to CU7?

What did you find in the Event Log about 2/12/2015 9:29:15 AM? (9:27 - 9:28)? Any Warning or errors?
0
 

Accepted Solution

by:
pgoldwasser earned 0 total points
ID: 40606487
i did upgrade to CU7, but I think I may have solved the problem outside of all of this.  It seems it may have been a DNS issue.  The DNS settings on both exchange servers were different.  I made sure they both had correct DNS settings and for the moment it looks good.  I will check the event log for 2/12/15 9:29:15 just to see if there is anything there.
0
 

Author Comment

by:pgoldwasser
ID: 40606674
I am going to close this question.  I have been testing for hours and it seems stable now.  Thank you Alexander for all of your help.
0
 

Author Closing Comment

by:pgoldwasser
ID: 40613810
It turns out that the problem was due to DNS issues and nothing to do with transport issues.  I solved on my own.
0

Featured Post

Are end users causing IT problems again?

You’ve taken the time to design and update all your end user’s email signatures, only to find out they’re messing up the HTML, changing the font and ruining the imagery. What can you do to prevent this? Find out how you can save your signatures from end users today.

Join & Write a Comment

We are happy to announce a brand new addition to our line of acclaimed email signature management products – CodeTwo Email Signatures for Office 365.
Resolve Outlook connectivity issues after moving mailbox to new Exchange 2016 server
In this video we show how to create a Contact in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Contact ta…
To show how to create a transport rule in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Rules tab.:  To cr…

743 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

10 Experts available now in Live!

Get 1:1 Help Now