Solved

Modify Send Connector on Office 365

Posted on 2014-01-06
4
3,638 Views
Last Modified: 2014-01-07
I need to modify one of the send connector we have setup in our Office 365 implimentation, to require TLS. I have tried using the below powershell commands, but these all error with:
"Set-SendConnector : The operation couldn't be performed because object 'PartnerCo Outbound' couldn't be found on 'DomainController1.ourdomain.local"

#connect to Exchange Online
$LiveCred = Get-Credential
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell/ -Credential $LiveCred -Authentication Basic -AllowRedirection
Import-PSSession $Session –AllowClobber
add-pssnapin Microsoft.Exchange.Management.PowerShell.E2010

#modify send connector
Set-sendconnector –identity “PartnerCo Outbound” –requiretls $true
#Using Online Domain as a prefix:
Set-sendconnector –identity “CloudDomain\PartnerCo Outbound” –requiretls $true
#Using GUI:
Set-sendconnector –identity 74930198-55f9-4e5b-ba36-7fb3cf473f1e –requiretls $true

How can I connect to Office 365 and modify the send connector?
0
Comment
Question by:bjblackmore
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
4 Comments
 
LVL 40

Expert Comment

by:Vasil Michev (MVP)
ID: 39759904
Remove the

add-pssnapin Microsoft.Exchange.Management.PowerShell.E2010

Open in new window


part of your script, using this will send the cmdlets to your on-prem server
0
 

Author Comment

by:bjblackmore
ID: 39760258
Thanks for the reply.

If I remove that line from the script, the cmdlet is not recognised.

I get an error: "The term 'Set-sendconnector' is not recognised as the name of a cmdlet, function, script file, or operable program."

set-sendconnector error
0
 
LVL 40

Accepted Solution

by:
Vasil Michev (MVP) earned 500 total points
ID: 39760300
Sorry, I dind't read the rest of the post it seems. The correct cmdlets to use with Exchange Online are the following:

Set-InboundConnector or Set-OutboundConnector

http://technet.microsoft.com/en-us/library/jj200710(v=exchg.150).aspx
0
 

Author Closing Comment

by:bjblackmore
ID: 39761491
Thanks, that seems to have sorted it!
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article aims to explain the working of CircularLogArchiver. This tool was designed to solve the buildup of log file in cases where systems do not support circular logging or where circular logging is not enabled
Phishing attempts can come in all forms, shapes and sizes. No matter how familiar you think you are with them, always remember to take extra precaution when opening an email with attachments or links.
This Experts Exchange lesson shows how to use VBA to loop through rows in Excel.  In order to sort, filter, and use database features, there needs to be a value in each column for every row. When data arrives with values missing, code to copy values…
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online. The email signature template has been downloaded from: www.mail-signatures…

756 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question