I’m signing in to my Office 365 portal with my global administrator account from the development machine where I have a SharePoint Server 2013 Enterprise farm upgraded to October CU 2015. In the SharePoint admin center I try to configure hybrid > Hybrid SharePoint Sites.
And then the error occurs:
SharePoint Hybrid Team Sites
An error has occurred.
One of the prerequisites is not met: the PowerShell command for SPO365LinkSettings does not exist in the SharePoint farm. Current SharePoint farm version is 15.0.4753.1000. As a prerequisite you should first upgrade to SharePoint 2013 with September 2015 product update and then re-run the wizard.
Klicken Sie hier, um mehr über die neuesten Informationen zu den Voraussetzungen für SharePoint-Hybrid zu erfahren.
The link at the bottom is German, but I only got English, Swedish and Norwegian language packs installed (The second run gave an English result).
I already have the server patched to SharePoint 2015 CU, and I can’t find any Product Update for September 2015. Is this a wrong error message? Or is it something else I miss?
All the following is in place (checked twice).
Prerequisites to using the Hybrid Picker:
- Be sure that an on-premises SharePoint Server 2013 farm has July PU or later properly installed (on-premises)
- Make sure that ports 80 and 443 are open in the firewall for outbound communications (on-premises)
- Log in to your SharePoint Server farm with an account that can access Central Administration as a Farm Administrator (on-premises)
- When you must log in to Office 365, use an account who is Global Administrator (Office 365)
- Accounts being synchronized must have at least one of the following properties: an e-mail address, a SIP address, or SMTP address. (on-premises)
You need to run and configure these services:
- App Management Service
- Subscription Settings Service
- Search Service Application
- User Profile Service
on your on-premises SharePoint Server farm to avoid error messages while using the Hybrid Picker. In Central Administration, click Manage Services on server to check whether these services are in a started state.
My guess is that this can't be done on SharePoint 2013 since the cmdlet
Get-SPO365LinkSettings is only mentioned in combination with SharePoint 2016. See What's new in SharePoint 2016?