tag:blogger.com,1999:blog-2228947945609574437.post6901480109080136599..comments2024-03-17T16:23:31.499-04:00Comments on Terence Luk: How do I export/import Exchange 2007/2010 receive connectors’ allow relay IPs?Terence Lukhttp://www.blogger.com/profile/02612575579652280306noreply@blogger.comBlogger10125tag:blogger.com,1999:blog-2228947945609574437.post-91044558556935007382017-03-26T16:44:22.356-04:002017-03-26T16:44:22.356-04:00Would be nice if we could find OCSASNFIX. Microso...Would be nice if we could find OCSASNFIX. Microsoft removed it from there site :(Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-2228947945609574437.post-16139134625754628792015-03-12T11:25:39.509-04:002015-03-12T11:25:39.509-04:00Excelent work!
But what if you want to move ip-ra...Excelent work!<br /><br />But what if you want to move ip-ranges from one connector to another? Is there a way to delete the ip-range from the old connector, because you cannot bind the ip-range to two different connectors on the same exchange server ?<br />Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-2228947945609574437.post-27243178337297642282014-09-26T19:15:29.229-04:002014-09-26T19:15:29.229-04:00Nigel Benfell is the man.Nigel Benfell is the man.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-2228947945609574437.post-19457708149175272032014-02-24T17:34:45.568-05:002014-02-24T17:34:45.568-05:00Simpler solution:
$list=(Get-ReceiveConnector &qu...Simpler solution:<br /><br />$list=(Get-ReceiveConnector "Exch1\For Relay Servers").RemoteIPRanges<br /><br />Set-ReceiveConnector "Exch2\For Relay Servers" -RemoteIpRanges $list<br />Nigel Benfellhttps://www.blogger.com/profile/05145918183645126888noreply@blogger.comtag:blogger.com,1999:blog-2228947945609574437.post-70212171669026182262013-07-03T13:15:45.907-04:002013-07-03T13:15:45.907-04:00I took a lot of your helpful information and wrote...I took a lot of your helpful information and wrote a script that does the job...<br /><br />function TransferReceiveConnectors {<br />$SourceServer = "SRV-Mail"<br />$DestinationServer = "SRV-Mail01"<br />$SourceReceiveConnector = ForEach-Object {Get-ReceiveConnector -Server $SourceServer}<br />ForEach ($Connector in $SourceReceiveConnector)<br />{<br />New-ReceiveConnector -Name $Connector.Name -Server $DestinationServer -Bindings $Connector.Bindings -AuthMechanism $Connector.AuthMechanism -PermissionGroups $Connector.PermissionGroups -RemoteIPRanges $Connector.RemoteIPRanges<br />}<br />}<br /><br /><br />Of course, change your source and destination servers as needed... Then call the function by simply typing TransferReceiveConnectors from the powershell command line.Thomas Kayhttp://www.tomscomputersupport.comnoreply@blogger.comtag:blogger.com,1999:blog-2228947945609574437.post-89024845839923167352013-06-27T10:24:47.868-04:002013-06-27T10:24:47.868-04:00Thanks for you post, it enlightened me.
I came up...Thanks for you post, it enlightened me.<br /><br />I came up with this approach<br />http://robertodimas.wordpress.com/2013/06/27/copyexport-exchange-2010-receive-connectors-to-a-new-server/<br /><br />Robertoroberto:Dhttps://www.blogger.com/profile/09800617094525658531noreply@blogger.comtag:blogger.com,1999:blog-2228947945609574437.post-58494320332652237412013-02-07T16:51:56.527-05:002013-02-07T16:51:56.527-05:00After reading this I did some tinkering to end up ...After reading this I did some tinkering to end up with:<br /><br />Export:<br />Get-ReceiveConnector -server [source server] | fl remoteipranges,identity,authMechanism,PermissionGroups<br /><br />This resulted in the export of all six connectors we were using in the format:<br /><br />RemoteIPRanges : {xxx.yy.27.133, xxx.yy.0.10, xxx.yy.32.94, xxx.yy.0.24}<br />Identity : [server]\[connector name]<br />AuthMechanism : Tls, ExternalAuthoritative<br />PermissionGroups : ExchangeServers<br /><br />I could have put that into a text file but viewing in the EMS was fine. I then had to manually substitute this info into commands that looked like<br /><br />C:\Windows\system32>New-ReceiveConnector -Name ConnectWise -Bindings 0.0.0.0:25 -RemoteIPRanges xxx.yy.27.133,xxx.yy.10,xxx.yy.32.94,xxx.yy.0.24 -AuthMechanism Tls,ExternalAuthoritative -PermissionGroups AnonymousUsers<br /><br />Some notes:<br />* When I exported, Custom was sometimes listed as a PermissionGroup but that isn't valid when importing.<br />* I went to the EMC to refresh and spot check. I then exported from the new server and spot checked there.Fast Runnerhttps://www.blogger.com/profile/15000163574863709700noreply@blogger.comtag:blogger.com,1999:blog-2228947945609574437.post-11162340560458034682012-11-12T03:26:03.861-05:002012-11-12T03:26:03.861-05:00Hi,
where you pointing the exported file to impo...Hi,<br /><br /> where you pointing the exported file to import?<br /><br />in your blog, you said to add only one IP address. Can't we add all the ipaddress pointing to export file<br /><br />DeviAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-2228947945609574437.post-33716178047443127372012-09-12T03:23:47.355-04:002012-09-12T03:23:47.355-04:00Excellent information certainly helped me :)
Keep...Excellent information certainly helped me :)<br /><br />Keep it up<br /><br />SurjAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-2228947945609574437.post-7920975171713712402011-09-09T02:48:09.486-04:002011-09-09T02:48:09.486-04:00Very Useful !! - I think you're missing the &...Very Useful !! - I think you're missing the 'pipe' operator "|" though between end of connector name and the format list ?<br />Should it be Get-ReceiveConnector “ServerName\ReceiveConnectorName” | fl RemoteIPRanges. ?<br />Worked great after i put this in just atypo most likely - Just what I needed though, Thanks KonradKonrad ganternoreply@blogger.com