Script to move send and receive connectors

Hello again,

Im almost at the end of my 2010 to 2016 exchange server migration. So far all the mailboxes have been moved. The last thing I need to do is move the send and receive connectors. I don't want to painfully do each one at a time and was wondering if any had a powershell script that could move it for me. Does anyone have anything like that.

Also, We have 4 2010 exchange boxes. I will be removing 3 of them, but 1 will have to stay. Its a long story. How can I point this one 2010 CAS server to our new exchange 2016 server? Is is done automatically via proxy?

Thanks for the help.
Kenny PlacidoSr System AdministratorAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

timgreen7077Exchange EngineerCommented:
you dont move send and receive connectors. exchange 2016 will create it's own receive connectors and do not modify them. in regards to the send connector you can create a new one for 2016 or use your send connector that you setup for 2010, and set the 2016 servers as the source servers on the send connector. just make sure if you are using a smart host they will accept traffic from 2016 servers, but connectors are not move between exchange environment, but actually all your exchange servers can use your send connector if you don't set the scope property.

Yes exchange 2016 will proxy connections to 2010 CAS servers.
2

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Kenny PlacidoSr System AdministratorAuthor Commented:
Moving the send connectors will be easy. That i figured is a piece of cake. But I do have 3 receive connectors on the old 2010 that have specific coping. One for DMZ, Fortimail (spam filter), and our ADP program. Im guessing i will have to recreate this on the new exchange server?

Ill leave the one 2010 server alone.
0
timgreen7077Exchange EngineerCommented:
Yes those are custom created receive connectors so you will recreate them. don't modify the default 2016 receive connectors or you will be asking for issues.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Todd NelsonSystems EngineerCommented:
If you have custom receive connectors in Exchange 2010, refer to this article to "migrate" them to Exchange 2016 ... https://oddytee.wordpress.com/2016/04/06/migrate-remote-ip-addresses-to-a-new-relay-connector/

How can I point this one 2010 CAS server to our new exchange 2016 server? Is is done automatically via proxy?

For client access and connectivity, Exchange 2010 will not proxy up stream to any version of Exchange.  You will need to configure Exchange 2016 to handle all client access and connectivity.  For mail flow however, mail can still come into 2010 and flow to 2016--this is done automatically--but would recommend pointing the firewall to 2016 and adding the 2016 servers to the send connector(s).  This is dependent on all of the Exchange servers being in the same forest.
1
Aaron GuilmetteTechnology Solutions ProfessionalCommented:
When you deploy a new server, new connectors are created.  However, if you have custom connectors that you need to migrate, you can use a script such as https://gallery.technet.microsoft.com/office/Copy-a-receive-connector-b20b9bef.
1
Kenny PlacidoSr System AdministratorAuthor Commented:
That script will help out for the 3 specific receive connectors that I have to move over. I dont need to modify the script, right?

@Todd, the 2010 exchange server is on the same domain. Only thing i have to change is the send connector source. It is pointing to our old 2010 primary exchange.

I will making all these changes on Thursday night, I will let you all know how it goes.
0
Aaron GuilmetteTechnology Solutions ProfessionalCommented:
You shouldn't need to modify it--it's about specifying the source and target servers and the source connector.

You may want to look at the old send connectors to see what servers have access to them (like what servers are relaying through them or "allowed to use").  Conversely, if you're changing the sending IP address (which you most likely are if you're changing / replacing servers), don't forget to look at the next hop (firewall, router, antispam/mail gateway, etc.) ACL to make sure your new server is able to relay mail outbound.
1
Kenny PlacidoSr System AdministratorAuthor Commented:
Question: I have 2 front end servers with different database. 1 is our primary and 2 is hold another set of databases. Do i have to copy the receive connectors to both or just the primary?

With the one 2010 exchange, it went straight to the primary 2010 then spam filter. Im just moving it to the new 2016, then spam filter. I think i will be ok with that one.
0
timgreen7077Exchange EngineerCommented:
Yes one will be fine.
1
Kenny PlacidoSr System AdministratorAuthor Commented:
Well, it worked about 99%. I have a separate exchange server (2013) and for some odd reason, i can send to it, but i can't receive emails from it. I looked in there barracuda and the sent email was deferred because it is trying to look at the old email server instead of the new one.
0
Kenny PlacidoSr System AdministratorAuthor Commented:
I figured it out. I forgot to change my MX record. Rookie move lol. It's working now. We are good to go. Thank you everyone for your help.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Powershell

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.