Export DL Memberships from Exchange 2013 and Import to 365 via PowerShell
Hi Guys, I am migrating our Distribution lists from Exchange 2013 server to O365. I have the following script to export and import memberships to a SINGLE DL but seeking your kind help to do the same for MULTIPLE DLs (200 in my case). Appreciate if anyone can shed some lights with a modified script here ! Export from Exchange Server 2013 for a single DL: Get-DistributionGroupMember -Identity "Marketing USA" | select Name,Alias | Export-CSV -Path "C:\Temp\ExportedDLMembers.csv" Import DL Membership from above CSV to Office 365 for a single DL: $CSVPath = "C:\Temp\ExportedDLMembers.csv" $Memberships = Import-Csv -Path $CSVPath $Memberships | ForEach-Object { $DistributionList = $_.Name $Member = $_.PrimarySmtpAddress Add-DistributionGroupMember -Identity $DistributionList -Member $Member } How can I achieve the same for MULTIPLE DLs (Export from Exchange server 2013 and import to 365 where Destination DLs are already exists). ? Thank you so much ! Kev
Using the <Start-ADSyncSyncCycle -PolicyType Delta> command remotely.
Hello all, I have an Exchange Hybrid between Office 365 and Exchange 2013 on-prem. For this to work we have the Azure AD Connect application installed on the Exchange server. It syncs every half hour and in order to force a sync, as needed in certain situations, we login to the server remotely and run the command <Start-ADSyncSyncCycle -PolicyType Delta> to force a sync. Works everytime and this makes sure that the Active Directory users attributes related to mailbox parameters are copied between the cloud and on-prem. I have tried initiating a remote Exchange Powershell session from other Exchange servers using <Import-PSSession> and <Enter-PSSession> after creating a New-PSSession. This all works but I get an error when I run the command <Start-ADSyncSyncCycle -PolicyType Delta> in both Import and Enter PSSession options. Any Ideas on what I am doing wrong would be greatly appreciated. I am new to the ocean of Powershell so I am pretty sure it is user error on my part. Thanks
