none
Distribution Group created in Exchange 2016 not delivering to users on Exchange 2010 server RRS feed

  • Question

  • Hello!

    I am currently in the process of migrating our users from Exchange 2010 to Exchange 2016. At the moment, only a handful of users have been migrated over, but the distribution groups are already upgraded to 2016. When a user sends sends an email (that has been migrated to 2016) to a distribution group, a user who is still on 2010 does not receive the email. However, if a user (That is still on Exchange 2010) sends an email to the same distribution group, it delivers to users on Exchange 2010 and users on Exchange 2016.

    If I email the distribution group externally, the account on Exchange 2016 receives the email, the account on Exchange 2010 does not.

    Wednesday, November 6, 2019 7:30 PM

Answers

  • Which user is on Exchange 2010? You can check the message tracking log with specific recipient on Exchange 2010.

    Did you try to create a new distribution group? The same issue?

    Does changing the service MSExchangeTransport to log on as Local System Account also work for you?

    Regards,

    Lydia Zhou


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    • Marked as answer by FJM1995 Tuesday, November 12, 2019 6:18 PM
    Tuesday, November 12, 2019 11:54 AM
    Moderator

All replies

  • Hello!

    I am currently in the process of migrating our users from Exchange 2010 to Exchange 2016. At the moment, only a handful of users have been migrated over, but the distribution groups are already upgraded to 2016. When a user sends sends an email (that has been migrated to 2016) to a distribution group, a user who is still on 2010 does not receive the email. However, if a user (That is still on Exchange 2010) sends an email to the same distribution group, it delivers to users on Exchange 2010 and users on Exchange 2016.

    If I email the distribution group externally, the account on Exchange 2016 receives the email, the account on Exchange 2010 does not.

    What do you mean when you say the distribution groups have been upgraded to 2016?

    Have you done a message trace on the missing messages?

    Wednesday, November 6, 2019 9:05 PM
    Moderator
  • Hi,

    You can use a mailbox created on Exchange 2016 and check if there is a same issue.

    Do you have issues about sending emails to mailboxes on Exchange 2010?

    Do you get any NDRs when users on Exchange 2010 cannot receive emails?

    You can use the following command to check your message tracking logs for mailboxes who didn't receive the message: 

    Get-TransportService|Get-MessageTrackingLog -MessageSubject <subject> -Sender <sender address> -recipients <recipient address>|select timestamp,EventID,Source,Recipients|sort-object Timestamp

    On Exchange 2010, you should use Get-TransportServer instead on Get-TransportService in this command.

    Regards,

    Lydia Zhou


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Thursday, November 7, 2019 7:25 AM
    Moderator
  • I ran the following command:

    Get-DistributionGroup –resultsize unlimited | Set-DistributionGroup –ForceUpgrade

    When I run a message trace, this is what I get:

    11/6/2019 1:50:14 PM   RECEIVE          STOREDRIVER   Test
    11/6/2019 1:50:14 PM   SUBMIT           STOREDRIVER   . Test
    11/6/2019 1:51:47 PM   RECEIVE          STOREDRIVER    test2
    11/6/2019 1:51:47 PM   SUBMIT           STOREDRIVER    test2
    11/6/2019 2:02:57 PM   RECEIVE          STOREDRIVER    Test4
    11/6/2019 2:02:57 PM   SUBMIT           STOREDRIVER  . Test4
    11/6/2019 2:24:37 PM   RECEIVE          STOREDRIVER   test6
    11/6/2019 2:24:37 PM   SUBMIT           STOREDRIVER    test6
    11/6/2019 1:50:14 PM   HAREDIRECTFAIL   SMTP          Test
    11/6/2019 1:50:14 PM   RECEIVE          SMTP          Test
    11/6/2019 1:50:15 PM   AGENTINFO        AGENT         Test
    11/6/2019 1:50:15 PM   DROP             ROUTING       Test
    11/6/2019 1:51:47 PM   HAREDIRECTFAIL   SMTP           test2
    11/6/2019 1:51:47 PM   RECEIVE          SMTP         test2
    11/6/2019 1:51:49 PM   AGENTINFO        AGENT         test2
    11/6/2019 1:51:49 PM   DROP             ROUTING      test2
    11/6/2019 2:02:57 PM   HAREDIRECTFAIL   SMTP          Test4
    11/6/2019 2:02:57 PM   RECEIVE          SMTP        Test4
    11/6/2019 2:02:57 PM   AGENTINFO        AGENT         Test4
    11/6/2019 2:02:57 PM   DROP             ROUTING       Test4
    11/6/2019 2:03:34 PM   HAREDIRECTFAIL   SMTP          Test
    11/6/2019 2:03:35 PM   RECEIVE          SMTP           Test
    11/6/2019 2:03:36 PM   AGENTINFO        AGENT       Test
    11/6/2019 2:03:36 PM   DROP             ROUTING      Test
    11/6/2019 2:24:37 PM   HAREDIRECTFAIL   SMTP         test6
    11/6/2019 2:24:37 PM   RECEIVE          SMTP           test6
    11/6/2019 2:24:40 PM   AGENTINFO        AGENT         test6
    11/6/2019 2:24:40 PM   DROP             ROUTING       test6

    Thursday, November 7, 2019 9:00 PM
  • Hi,

    There are no issues sending to users on Exchange 2010.

    No NDRs with users on 2010. Emails sent to a distribution group work if the user is on 2016, but if the user is still on 2010, the email never shows up.

    Thursday, November 7, 2019 9:03 PM
  • The -force command is only needed if those groups were created before Exchange 2010

    That message trace does really show any errors. search by MessageID instead to get the complete trail to the recipient. Have you checked the queues from 2016 > 2010?

    Is there any NDR? Ensure the DL has this setting to get one:ReportToOriginatorEnabled $true



    Thursday, November 7, 2019 9:22 PM
    Moderator
  • Saturday, November 9, 2019 1:03 PM
    Moderator
  • Which user is on Exchange 2010? You can check the message tracking log with specific recipient on Exchange 2010.

    Did you try to create a new distribution group? The same issue?

    Does changing the service MSExchangeTransport to log on as Local System Account also work for you?

    Regards,

    Lydia Zhou


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    • Marked as answer by FJM1995 Tuesday, November 12, 2019 6:18 PM
    Tuesday, November 12, 2019 11:54 AM
    Moderator
  • Changing the service solved the issue!
    Tuesday, November 12, 2019 6:18 PM