Forum Discussion
Copy receive connectors
I'm migrating from Exchange 2010 to 2016 and I was looking for a way to copy all the Ex2010's Receive Connectors to Ex2016. I found a script on github that should do just that but it fails with the ...
Stefano ColomboI have used the below command successfully at various customers, although not on Exchange 2010. Try them and see if it makes a difference.
Get the current receive connector you want to copy and verify IPs:
(Get-ReceiveConnector -Identity "<ServerName\ConnectorName>").RemoteIPRanges | Sort-Object | Format-Table
Copy the connector to the target server:
New-ReceiveConnector -Name "<Connector Name>" -Server "<TargetServerName>" -Usage Custom -TransportRole FrontEndTransport -PermissionGroups AnonymousUsers -Bindings 0.0.0.0:25 -RemoteIPRanges (Get-ReceiveConnector "<ServerName\ConnectorName>").RemoteIPRanges
Just change your permission groups to what they need to be if not AnonymousUsers.
Hope this helps
Hello Thomas,
Thanks for your suggestion but it’s the same command I tried.
I’m pretty sure, since I used it too in the past, that the issue is related to exchange 2010.
I used that command to copy receive connector between the two exchange 2016 servers that are going to replace the 2010 without any issue,
I solved the problem by creating a script that reads the remote receive connectors and cycle them one at time and using a temporary file for remote IP ranges creates the new connectors on 2016
Thanks for your suggestion but it’s the same command I tried.
I’m pretty sure, since I used it too in the past, that the issue is related to exchange 2010.
I used that command to copy receive connector between the two exchange 2016 servers that are going to replace the 2010 without any issue,
I solved the problem by creating a script that reads the remote receive connectors and cycle them one at time and using a temporary file for remote IP ranges creates the new connectors on 2016
- Hi Stefano,
I suspect that you are correct in you assessment that it is 2010 related, the oldest version I have used it on was 2013. Glad to hear you found a solution though!
