[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 274
  • Last Modified:

Exchange 2013 Internal Relay Powershell Error

Migrating from 2007 to 2013 Exchange.

EX13-01 is MB
EX13-02 is CAS

Followed the site: http://exchangeserverpro.com/exchange-2013-configure-smtp-relay-connector/

The last step is the powershell command. I log into EX13-02 as a domain admin, run the Exchange Management Shell as administrator and enter my command: Get-ReceiveConnector "Internal Relay" | Add-ADPermission -User 'NT AUTHORITY\Anonymous Logon' -ExtendedRights MS-Exch-SMTP-Accept-Any-Recipient

The error I receive is below. I've looked, and I can't find anyone who has had this issue. If I am logged into EX13-02, why does the error reference in EX13-01? Why is it looking at one of my domain controllers as well? Also, yes, my internal Relay is literally called 'Internal Relay.'

The operation couldn't be performed because object 'EX13-01.domain.net\Internal Relay' couldn't be found on
'DC04.domain.net'.
    + CategoryInfo          : NotSpecified: (:) [Get-ReceiveConnector], ManagementObjectNotFoundException
    + FullyQualifiedErrorId : [Server=EX13-01,RequestId=0cf784e7-2524-4445-932f-aad0c96408fa,TimeStamp=10/19/2016 1
   :42:33 PM] [FailureCategory=Cmdlet-ManagementObjectNotFoundException] D7212594,Microsoft.Exchange.Management.Syste
  mConfigurationTasks.GetReceiveConnector
    + PSComputerName        : EX13-02.domain.net
0
CCICT
Asked:
CCICT
  • 4
  • 3
2 Solutions
 
MAS EE MVETechnical Department HeadCommented:
Hi,
First of all why do you need a relay connector?

Second the error looks like you didn't create the connector.
If you already created please give time to replicate.
If there is replicatiomn issue in your AD then you will have to fix the replication first.

Thanks
MAS
0
 
Jakob DigranesSenior ConsultantCommented:
do this

get-receiveconnector
make sure Internal Relay is noted with full name, server\relayName

Is shows EX02 as it is MB-role - and thus has the HUB-transport role

Also - Microsoft recommend collocating roles for Exchange 2013/2016 servers. I'd rather have one 2013 MBX/CAS server, or 2 x MBX/CAS servers with DAG
0
 
CCICTAuthor Commented:
Thanks for the answers. I did run a 'Get-ReceiveConnector' and I did see the connector called 'Internal Relay' listed to my server

EX13-02\Internal Relay               {0.0.0.0:587}                           True

This relay was created a few weeks ago, but I just changed the permissions to anonymous and tried the run the command yesterday.

Where are you seeing in the error that EX13-02 has the MB role? When these were built, we selected only CAS for EX13-02
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
Jakob DigranesSenior ConsultantCommented:
sorry .. my bad. I mixed up EX13-01 and EX-02
0
 
Jakob DigranesSenior ConsultantCommented:
this command then:

Get-ReceiveConnector "EX13-02\Internal Relay" | Add-ADPermission -User 'NT AUTHORITY\Anonymous Logon' -ExtendedRights MS-Exch-SMTP-Accept-Any-Recipient

receive connectors are server specific
0
 
CCICTAuthor Commented:
Thanks, that worked!

Why was it giving me such a hard time about using the original command: Get-ReceiveConnector "Internal Relay" | Add-ADPermission -User 'NT AUTHORITY\Anonymous Logon' -ExtendedRights MS-Exch-SMTP-Accept-Any-Recipient

I was on the correct server with the internal Relay, so why did it default the Ex13-01?
0
 
Jakob DigranesSenior ConsultantCommented:
i doesn't matter which server you're logged in to - you always (more or less) have to specify identity or server.
and receive connectors are server specific
0
 
CCICTAuthor Commented:
Thanks for the help
0

Featured Post

Learn to develop an Android App

Want to increase your earning potential in 2018? Pad your resume with app building experience. Learn how with this hands-on course.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now