Resolving issues with slow Outbound mail to Office 365 in a Hybrid connection using a SmartHost or Internal Appliance

You may find that flow to Office 365 hosted users is slow after initial Hybrid Configuration.  But the answer is closer than you think and is only one Cmdlet away with Windows PowerShell.

The actual problem is the mail flow to Office 365 is slow because the connector is defaulting to using DNS for mail sending. In this scenario the server is either sending directly to an internal appliance (such as a Barracuda) or uses a Smarthost on the internet (Such as on SBS 2011 / SBS 2008) and in many SMB configurations.

Normally you would change the connector properties to point the exist SmartHost and the problem would be resolved.


What you will find in the connector created by DEFAULT with the Hybrid wizard is this does NOT solve the problem. You can see the actual problem when you view the connectors with the Get-SendConnector Cmdlet and view a full list of the properties.

Get-SendConnector -identity ‘SmartHost Connector’ | Format-List *


Get-SendConnector -identity ‘Outbound to Office365’ | Format-List *


Note the highlighted areas of the Office 365 connector. By default it’s insistent on a TLS connection and a few additional properties (which are fine if you’re hosting a live Exchnage/DNS configuration)

However in the case of a SmartHost, it may not like this (Bad Smarthost on the internet with lousy Authentication ?) or you’re running an internal box to handle outbound spam which is not configured to accept TLS internally.

Three options you have. (as Yoda would say)

  1. One, get a better SmartHost provider or improve your internal Device security to accept TLS.
  2. The Second option is to recreate the Office 365 Connector from scratch with the same settings and point straight to the SmartHost.
  3. The third (and probably quite a bit easier) is to adjust the connector through PowerShell and disable the requirement for TLS and remove the additional properties left behind by Office 365’s Hybrid wizard (which should be fine for INTERNAL devices)

First make a copy of the Connector should you need to Rollback the process

Get-SendConnector -identity ‘Outbound to Office365’ | Export-Clixml Office365Connector.xml

Then adjust the particular connector name for Office 365 outbound mailflow on your On Premise Exchange environment

Set-SendConnector -identity ‘Outbound to Office365’ -RequireTLS $False -RequireTLS $False -TlsAuthLevel $NULL -TlsDomain $NULL -ErrorPolicies Default

No restart of any services are required and the effect should be immediate. Note as always, any mail stuck in the queue under the old configuration is just good for one thing… NDR’s 😉



The EnergizedTech

Migrating One Note Content from OneDrive (SkyDrive)

Today’s little share is not “PowerShell related” but it’s something I personally encountered and I thought it would be good to share.  I’ve been using OneDrive for a LONG time and when I started using One Note, it defaulted to my OneDrive account.  

This was really cool because the content kept synching, was always accessible remotely or locally.

As I started working for my current employer, I used it to keep track of rough notes on work for various clients.    One challenge however.

It was still on my Personal OneDrive.   I wanted to move my Corporate work to either a Central Sharepoint location or at LEAST to my One Drive for Business.

Here’s the problem I hit against.

If you go to OneDrive and click on the “One Note Notebook” in question there is NO download option.  (Most other documents you usually get that)


The answer is actually pretty simple.  I ran across in the Answers forum on Technet

Create a New Folder in OneDrive (I called my New OneNotes)



Move the One Note document to the Folder



Download the Newly created Folder


At this point once you click on download your browser will want to store away this as a ZIP file.   Store this away to a convenient location for later use.

Now you can have a copy.  Extract the contents of this zip file to a folder and copy the folder to your target location.  It can be

  • Local folder
  • File Share
  • One Drive for Business folder
  • Sharepoint Documents folder

Once you have copied the data to the Target location, you’ll need to open it at least Once for One Note to add to the list of Note Books.   In One Note 2016 just click on “File” and then “Open”


from this point there is a browser for navigating your various file locations.  Navigate to the new one, select your folder in question, then open the “Open Notebook” file just underneath the name of the folder.


Sometimes One Note may prompt you with a message like “A notebook cannot be found at this location.  Do you want to open …..” just click yes.   It’s nothing bad.

At this point you are now looking at your copy of the One Note document.  But you need to switch it from “Archive” to live.    You can tell from the above warning.


Click on the pretty yellow line to continue forward and allow the conversion to occur.  It will prompt you to Convert a Single Selection or the Entire Notebook.  In my case I’d like to convert the Entire Notebook


The process will step through all of your individual sections and convert them up to your modern version of One Note.   At this point you have now made a copy of your PERSONAL One Drive to your Business folder.    From here you can go through and delete sections and content that are yours and leave your business data behind for work.

Also note, this is a COPY.  If you MESSED up? (Oh … oh that just NEVER happens with computers …. Right?  Right? Nudge nudge) . 

Just remember you have a ZIP file you downloaded before.

Share and Enjoy!

The Energized Tech

Using the Office Deployment Tool (ODT) with the RETAIL (not Office 365 version) of Office 2016

Here’s one I ran into today.  It might be documented somewhere but I just couldn’t find it


When targeting software for the Office Deployment Tool almost every version shows this as the Product name



This is for Office 2013 or Office 2016 from Office 365


If you are trying to deploy Office 2013 or 2016 (Click to Run edition) from the MSDN or Volume media change it to



The rest of the file should remain the same.  The same goes for your download.xml file.  Update the PID to reflect “ProPlusRetail” or I believe just pull off the O365 reference.  This will download the proper bits for the media and language.   It should also allow you to accept the proper product key.


Share and enjoy


The Energized Tech