On-prem Distribution List Migration

Question

On-prem Distribution List Migration

Arni 116

Hello Experts,

Is it possible to migrate our on-prem Distribution List to Exchange Online? Currently, we are managing our DL in our Active Directory which syncs to the cloud. I heard that there's a script that can do this. If you happen to know the script, could you kindly share me that information. I also would like to know if this script method will move the nested group. What would be the cause and effect if there's a way to do it? Your input is greatly appreciated.

Thanks

0 comments

2 answers

Your answer

Answer 1

Arni 116

@Joyce Shen - MSFT thank you for this info. We are currently using the number one method that you've suggested and managing our on-prem DL via Active Directory. We don't have an on-prem Exchange server. We have hybrid because we're still managing DLs using the AD. However, we actually want to get rid of this hybrid including managing Distribution Groups in our AD. The focus right now though is to export all these DLs that is on the AD to Exchange Online so that we only have one place to manage it (e.g. Exchange Online).

I read method number two and in my opinion this is kind of complicated and I will need guidance on this (especially if this is not coming from Microsoft, no guarantee) I would like to try this script by testing a few Distribution group test accounts and see what will happen, but the instructions seemed to be focus on exporting all the DLs. I wonder if that script (e.g. $groups = Get-DistributionGroup -ResultSize Unlimited -IgnoreDefaultScope) can be modify to specific group only, just for testing purposes?

Thank you.

Joyce Shen - MSFT 16,706 Reputation points

2021-07-19T06:52:48.623+00:00

Hi @Arni

Yes, if you want to test only one specific group, Get-DistributionGroup -Identity "group name"
We could also use -filter to choose some groups meet the value, for example

Get-DistributionGroup -Filter "Alias -like 'xxx'"

More information: https://learn.microsoft.com/en-us/powershell/module/exchange/get-distributiongroup?view=exchange-ps
Arni 116 Reputation points

2021-07-22T19:47:11.737+00:00
Hi @Joyce Shen - MSFT

II was trying the script and run into some errors:

Get-DistributionGroup : The term 'Get-DistributionGroup' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the
spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:2 char:11

$groups = Get-DistributionGroup -Identity Test_All -IgnoreDefaultScop ...

~~~~~~~~~~~~~~~~~~~~~

CategoryInfo : ObjectNotFound: (Get-DistributionGroup:String) [], CommandNotFoundException

FullyQualifiedErrorId : CommandNotFoundException

You cannot call a method on a null-valued expression.
At line:11 char:105

... mtpAddress ;Get-DistributionGroupMember -Identity $guid.ToString() -R ...

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo : InvalidOperation: (:) [], RuntimeException

FullyQualifiedErrorId : InvokeMethodOnNull

I was wondering if this should be done in Exchange Management Shell? I was using the PowerShell ISE. Any input is greatly appreciated, thanks.
Joyce Shen - MSFT 16,706 Reputation points

2021-07-23T05:36:46.77+00:00

Hi,

Where did you run the command? Please run the command in Exchange management powershell rather than windows powershell.

And the right permission for this command:
Arni 116 Reputation points

2021-07-23T22:59:48.857+00:00

I@Joyce Shen - MSFT I run the the command in PowerShell ISE remotely. Our Exchange Management Shell is currently not working. I need probably need to submit a ticket on this one for further assistance. I'll keep you posted. Thanks for your help.
Joyce Shen - MSFT 16,706 Reputation points

2021-07-27T05:34:58.54+00:00

Hi,

Are you using the method introduced in official document to Connect to Exchange servers using remote PowerShell ?

It mentions that: After Step 3, the Exchange cmdlets are imported into your local Windows PowerShell session and tracked by a progress bar. If you don't receive any errors, you connected successfully. A quick test is to run an Exchange cmdlet (for example, Get-Mailbox) and review the results.

If you receive errors, check the following requirements:

A common problem is an incorrect password. Run the three steps again, and pay close attention to the user name and password you enter in Step 1.

The account you use to connect to the Exchange server needs to be enabled for remote PowerShell access. For more information, see Control remote PowerShell access to Exchange servers.

TCP port 80 traffic needs to be open between your local computer and the Exchange server. It's probably open, but it's something to consider if your organization has a restrictive network access policy.
Joyce Shen - MSFT 16,706 Reputation points

2021-07-30T07:10:13.577+00:00

Hi @Arni

Is there any update about your issue?

Answer 2

Hi @Arni

Yes, two ways can be used to migrate your distribution groups.

Sync your groups using AAD Connect, however note that we can only manage the groups from on-prem server side.
As you said above, using powershell script to create new group in cloud. So that you can manage them in cloud.

Below is an article which provide related script and step-by-step guide to perform the operation:
Migrate Distribution Groups from Exchange On-Premise to Exchange Online

Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

If an Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Share via

On-prem Distribution List Migration

2 answers

Your answer