Learn Exchange the Guru way !!!


Exchange Receive Connector

Recently I was migrating a customer of mine and found multiple receive connector in the legacy exchange system.

In an environment where we have multiple exchange servers in load balancer mode this take will take your half of the day and almost make you feel unwilling to do it. Isn’t it boring to do?

Let us make it interesting and quick.

Here is what I did for this customer to make it more interesting.

1. Extracted output of the current receive connectors by running the following command

Get-ReceiveConnector –server OldExchangeserver | select identity,bindings,auth*,remoteIP*,PermissionGroups

I got output like below

You might have many IPs in RemoteIPRanges and all might not come in the output. If this is the case then we need expand the limit. Default limit is 16. Run the below mentioned command.

$FormatEnumerationLimit =-1

Now rerun the command  and you will see all IPs from RemoteIPRanges



2. Copied the output to a notepad, now we have input available to make command for output.


3. Made the following command to run in the new exchange system. Something like below:

New-ReceiveConnector -Name NameOftheConnector -AuthMechanism Authentication -RemoteIPRanges RemoteIPs -Bindings -PermissionGroups AnonymousUsers -Server NewExchangesystem

I made multiple commands in another notepad.

Point to be noted values here will accept only , to add multiple values for RemoteIPRanges & AuthMechanism

4. Now I opened EMS with run as administrator and ran the commands.

5. Now same connectors I need for 10 more servers so I preferred to come back to the notepad and replace the server name

6. Now copied the commands and pasted in the EMS.

7. Repeated step 5 and 6 for remaining servers.

8. When I closely observed all receive connectors I found one of the connector had so many IPs in RemoteIPRanges which were not coming properly in the output. So we had 2 options run the command and get it in the csv or copy from ldp. Then update the command. I choose LDP.


Now you will be thinking why I didn’t write a PS1 script. The reason is you need to type so much input to the PS1 script I preferred this way which is more interesting and faster.

I hope this will help.


Prabhat Nigam

Microsoft MVP | Exchange Server

Team @MSExchangeGuru

6 Responses to “Exchange Receive Connector”

  1. NeWay Technologies – Weekly Newsletter #123 – November 27, 2014 | NeWay Says:

    […] Exchange Receive Connector – […]

  2. NeWay Technologies – Weekly Newsletter #123 – November 28, 2014 | NeWay Says:

    […] Exchange Receive Connector – […]

  3. Kishore Says:

    Me too did the same migrating connectors from 2010 Edge to 2013 edge… But lot of customization in old connectors… spent more time

  4. Natesh Says:

    Hi Prabhat,

    We in the process of consolidation of 2 office location. We have 1 FE and 2 MBX on each location.
    We are planning to move to new location. I would like to know the best practice to move the FE roles to the new location. Connectivity between the new location and the 1 of the existing location is to on P2P.

    Let me know if this approach works.

    Location A and B
    New location C

    Move all the Mailbox from location B to Location A, where I have the internet facing (FE) is currently located. Then, configure a New FE on the new location C. New location will have new set of VLAN and IP range.

    Question: What are the changes to made on the exchange FE?

    Many thanks in advance


  5. Exchange 2016: Mail Routing « Says:

    […] I have written the above blog about creating receive connectors from PowerShell because there can be 10 new servers and all servers may require 4 to 5 receive connect which leads to 30 to 40 receive connector. In this scenario PowerShell save your time. Check this blog here. […]

  6. Prabhat Nigam Says:


    This approach does not work. you need to keep both CAS and MBX in the same AD site.

Leave a Reply




Do NOT follow this link or you will be banned from the site!