Essentials Experience on member server - Office 365 Integration

A. Windows Server Essentials Experience on 2012 R2
B. Office 365 (existing subscription)
Attempt to run wizard for integration with Azure AD/ Office 365 results in "This task must be performed on the domain controller". At this stage there is only one, has ever only been one, domain controller in the forest. Fresh
install of a DC, no previous Essentials components ever existed.
So, how do you run the integration components on the DC?
DC doesn't have the wizard links in the %systemroot%\System32\Essentials directory. Attempting to run it over the network fails (accessing via Explorer). I hesitate to install DIRSYNC to the DC or any other components, thinking it won't have
the Dashboard integration (required). Can't find documentation of the configuration anywhere, but WSEE is supported as a member server, so why is there only documentation for installation to a DC? Even tried using remote dashboard access, obviously
this failed miserably because the remote dashboard is just a RDS published app.
Tried the Office 365 folks asking if they had any documentation for the process, met with "contact the WSE team, not an Office 365 issue", even though it's a connector to their setup, and at least they could have something to indicate whether it's
supported or a "how to". Nada on TechNet, it all refers to the Essentials server, not Essentials Experience. Bing search spits out lots of references to the articles about WSEE on domain member support, but nothing about features within
WSEE supported on a domain member.

I just built this up in Azure.
1 DC VM
1 Essentials VM (member server w/Role)
I can confirm i see the same behaviour.
This is an error from PowerShell which explains perhaps, a little more:
PS C:\Users\dfunk.TR> Enable-WssIntuneIntegration
Enable-WssIntuneIntegration : The service can only be integrated on Essentials server running as single domain
controller in the network.
At line:1 char:1
+ Enable-WssIntuneIntegration
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (:) [Enable-WssIntuneIntegration], InvalidOperationException
+ FullyQualifiedErrorId : InvalidOperation,Microsoft.WindowsServerSolutions.Administration.EnableWssIntuneIntegrat
ion
So, it would seem that these integration features are currently, only applicable to an Essentials network with a single DC, but when that DC is also the Essentials Server.
If only we had bugged it in the recent past..
Robert Pearman SBS MVP
itauthority.co.uk |
Title(Required)
Facebook |
Twitter |
Linked in |
Google+

Similar Messages

Windows Server 2012 Essentials - Office 365 Integration Module Set Up Error

We receive an error when setting up the Office 365 Integration Module. After we type in the admin credentials for Office 365, it attempts to configure, but then states it couldn't complete and try a reboot of the server. We've rebooted multiple
times, but still face same error. The users in Exchange Online get displayed after closing and reopening the Dashboard, but no other settings like subscription/domain information are pulled into the dashboard. When we click in Users on the Dashboard
and attempt to assign an Office 365 account to an AD account, the Dashboard closes. Any ideas on what's happening? This Win 2012 Essentials has all Windows updates applied.
Thanks,
Dave

My Dashboard Issue was resolved (Susan Bradley Helped Generated A Support Ticket) when i asked the SharePoint Online support to revert my Primary's Site Language from Greek to English. I was one of the first to report this problem and i was working with
Server support for almost 2 months. You don't have the option to set the Language of your Primary site while you activate your Office 365 Subscription. It enables the Primary Language from your Location settings i believe.
Once My main SharePoint Master Site was revert to English (US) my Libraries synced OK with no Dashboard Crashing.....

Issue with Office 365 integration module

I have an issue with the Office 365 integration module on one of my customer's Windows Server 2012 Essentials servers.
Recently they switched to a new Office 365 plan, but the integration module still thinks the customer is on the old plan. This doesn't seem to affect functionality at all, so I think it's just cosmetic. On the Office 365 tab of the Windows Server Essentials
dashboard, under Subscription it lists the old plan and says the subscription has expired. Under Licenses it says "your subscription includes 0 licenses" and "0 licenses are assigned to user accounts."
Steps I've tried to resolve this issue:
Created a new Office 365 test user account (after switching plans) and then on the Windows Server 2012 Essentials dashboard clicked 'Change the Office 365 administrator account.' This made no difference.
Uninstalled and then reinstalled the Office 365 integration module. Again, this made no difference.
I suspected there might be an issue in the Office 365 back-end, where the customer's Office 365 account was somehow still associated with the old plan, but they said that wasn't the case.
I opened a service request with Office 365 support about the issue with the server dashboard, but this was their response: "As we are online service support team, we provide limited support on local application extension...you may need to contact the
Windows Server support team for further help."
As it seems to be just a cosmetic issue, I'm not going to open a paid service request with the Windows Server support team, but I'm interested to know if anyone on the forum has struck this issue before or has any suggestions.

Not seen this issue myself, you may be right in that it Is just a cosmetic issue, and I would be surprised if a fix was forthcoming even if you opened a case (or we opened a case for you) due to resources having shifted to the Windows 10.
You could grab the OIM logs from programdata\windowsserver\logs and we can see if there is anything obvious in there.
Robert Pearman SBS MVP
itauthority.co.uk |
Title(Required)
Facebook |
Twitter |
Linked in |
Google+

Do Office 365 integration now (2003) or after upgrade (2012 R2)?

A client has Server 2003 Standard and are going to migrate to Office 365 very soon (from a hosted mail provider, POP). They are also due for a server upgrade, likely Server 2012 R2 Standard. To eliminate the hassle of managing two different systems for their
Windows accounts and email accounts I thought I'd run Federation Services for the Office 365 integration. The problem is they are still trying to find a way to budget for the server upgrade, so it's starting to look like I may have to integrate O365 with 2003
instead of 2012 R2.
I assume its better to integrate Office 365 with 2012 R2 than 2003. If so, why?
If I do integrate with 2003, what type of issues can I expect when I finally upgrade to 2012 R2 (i.e., link between AD or federation services and O365 break, can't manage email from Server 2012 R2 dashboard because feature wasn't available in 2003)?

The most important question is, "Does your client currently use Exchange 2003?" Next question is, "Are they planning on running a hybrid Exchange setup?" Information about the current server(s) and its/their role(s) would be good to know too.
At our workplace, We had a 2003/2008/2008 R2 server cluster, with one of the 2003's running Exchange 2003 with 500 mailboxes. If I had known then what I know now, I would have run a cutover migration ASAP. Our AD wasn't current in the Users and Computers
section, so we thought we'd save money by cleaning up the directory, then run a hybrid with the complimentary version of Exchange 2010 that comes with O365 E3. After a while we realized that there were no real advantages for our company to run the hybrid,
so we decided on a cutover. During that conversation, our Exchange server died. We went online with a CSV dump of the AD, archived the old database, and imported PST's on demand.
I take it since your client is strapped for cash, the won't be doling out for Exchange 2010 or 2013. You may also know by now that Exchange 2003
will not run on any edition of Server 2008 or 2012, so they're going to have to drop it.
So, the gameplan I propose to you is this:
1) If you have less that 1,000 mailboxes, run a cutover migration ASAP. If you have unused accounts, clean them out after you make the migration and cancel them in the pricing. The web panel is really easy to use, and the Powershell module is great too.
2a) When (or if) the client is able to acquire 12R2, check the DC first. Some companies have internal domains named "domain" or "company.local". If they plan to do AD Synchronization (I guess for Single Sign-On), that's not going to work. The FQDN must be
mapable to a top-level Internet domain (e.g. .com, .org, .net), and they may have to create a new domain (or even forest) to become compliant. Check this now, and factor it into your pricing.
2b) If 2a is an issue, you may have to install 12 on a separate machine/VM because two forests can't reside on one DC (security issues). If not, upgrade the DC.
3)Run the AD check to make sure the domain is good for synchronization, then sync.
4)It is highly recommended that you do not run federation services on a domain controller, because that would expose it to web traffic. See: http://technet.microsoft.com/en-us/library/cc778681(WS.10).aspx . If possible, run it on a separate machine. 12 Standard
comes with two licenses for 12 running on a Hyper-V host, so you may consider that if the hardware permits. Keep in mind there can be issues with running a domain controller on a virtual machine (I do, and while I know it's not the most secure setup in the
world, most of our firewalling is done at the hardware level). Decide on how you want to situate FS, then bring it online. Recommended practice is to have it in a DMZ, and of course you shouldn't put a DC there.
5) Make sure your certs are good (you have to use a separate subdomain [e.g. fs.company.com] for FS than the internal one), then activate FS. Remember that certificates costs money, but you should only need a domain validation one.
Truth be told, I wouldn't recommend FS for a client that can't afford Server 12. Sit down with them and ask for concrete examples of what they presently do and what they are trying to do. Also ask them if they have the staff to maintain an Active Directory
that is bound to O365 (probably not). During this talk, do not use words like "sync" and "cloud"; they are buzzwords that are certainly misguiding the decision makers. You do not need to have federation in order to use OneDrive with your desktop Excel or to
"access your files from anywhere". If they start to do a lot of SaaS in the future, then they may want to reconsider.
Final Note: Don't bother doing anything with 2003 if you can avoid it. Scrap it as soon as you can. Microsoft ended support for it on the 8th, and O365 support isn't going to help you with it when you eventually need to call (and you will).

Server 2012 essentials Office 365 integration

I have a couple clients on 2012 Essentials that I've migrated from SBS 2011. I have also moved the clients to Office 365. I have the users setup in the dashboard, and assigned to an Office 365 account.Is there a way to check password sync between server and o365? I have had clients change their passwords online, which I know breaks the sync, but shouldn't a change on the computer re-enable that sync? Short of unassigning/reassinging (which makes the user change their password on next login), is there a way to re-sync the passwords? It almost seem easier to just not have any integration as none of the user accounts seem synced at this time, and I've only had one user out of dozens actually change their password online....Compounding the issue is that with multiple devices, such as phones, and tablets, you may be prompted to change your...
This topic first appeared in the Spiceworks Community

Just to update and say i did this, this morning, and it did take a while but my phone did appear in the dashboard.
Including a lot of info about the device!
The Dashboard.Log file seems to contain some logging about the process.
Robert Pearman SBS MVP
itauthority.co.uk |
Title(Required)
Facebook |
Twitter |
Linked in |
Google+

Autodiscover not working correctly when Office 365 integrated with Server Essentials 2012 R2

Hello!
This last weekend I setup our server as new and to ease the creation of users, integrated with our Office 365 (which to this point has worked fine) and imported the users. This had a somewhat unexpected side effect in that the import used the email address
as for the user forename and then synced that change back to Office 365 and so needed to enter this information back in on the dashboard which synced back to Office 365. This may or may not have any relevance to our issue below.
I should also point out that we have our own domain name so within the original Office 365 setup we had just one .onmicrosoft.com user with all the rest setup with our own domain name.
At the weekend when it came to the client install, Outlook (2010 or 2013) would fail on the autodiscover with it asking again for credentials but critically displaying a server name of .contoso.com rather than the office365srvr.contoso.com . As I mention,
Office 365 had been operating fine for some time and DNS records where checked and have been set for sometime. I spoke to Office 365 support and after a while come up with a temporary solution (so that I could complete the client installs) of assigning each
user a onmicrosoft address, using that in the new account wizard to pick up the server correctly and then signing in the the Office 365 .contoso.com credentials.
This worked OK to get us past the weekend (although I am having to reset up profiles on quite number of users where they get disconnected but with no credentials box appearing) but isn't a solution. The clients do not see public folders or their archives
and of course we don't want to keep having to reset the profiles.
I'm think that there must be something in the internal network that needs reconfiguring but I don't know what. I have tried pointing the client to an external DNS server just in case the internal DNS server was throwing the autodiscover out but this has
made no difference.

Ah - solved my own problem.
Despite the domain DNS record looking OK and the Office 365 Portal domain checker not highlighting any issue, it looks as though the autodiscover is picking up an imap account provided by the web host.
I've added an alias on the local DNS server to point to the Office 365 autodiscover server and this has solved the problem.

Exchange Server 2013 and Office 365 Integration

If we are using Exchange Server 2013 on premise, can we have 2 of our users integrated with Office 365 so that they can utilize their Exchange Server email account with the apps and features of Office 365?

Hi,
You can deploy a hybrid environment using Exchange 2013 CU2 or later version with Office 365.
Could you please tell me what do you mean by "we have 2 of our users integrated with Office 365 so that they can utilize their Exchange Server email account with the apps and features of Office 365"?
Here is my understanding: You create these two mailboxes on Exchange 2013, but you need to allow for redirection from the on-premises OWA environment to the Office 365 OWA. If that is your case, you need to specify a target URL for your organization(for
example, www.outlook.com/contoso.com). If I have misunderstood your concern, please let me know.
For more information, here is an article for your reference.
Plan an Exchange Online hybrid deployment in Office 365
http://technet.microsoft.com/en-us/library/hh852414.aspx
Hope it helps.
Best regards,
Amy Wang
TechNet Community Support

Project Server (Office 365) Get Project Risks data

Hi
I'm new to project server online (office 365).
I have a Project server online on Office 365 and I want to query all the projects and its Risks as an excel file. The Risks SharePoint uses OOTB content types and few custom column added to the list. I was told that the OOTB office data connection file for
Risks does not retrieve the custom columns and I was tasked to fix this issue.
I'm completely new to project server and could someone tell me how this can be accomplished. If I create a new data connection file will I be able to use SQL Query or using SQL Query is not allowed in Office 365 since the database is not known.
If using SQL Query is not an option how can I query the OOTB columns + the custom columns for all the projects.
I want to use the ODC file to generate Excel file which then can be used for different views like power pivot etc.,
Kannan

Hello,
You need to use the SharePoint list REST / OData APIs to get any custom columns as only the default Risks / Issues columns are synchronised to Project Online Odata.
Paul
Paul Mather | Twitter |
http://pwmather.wordpress.com | CPS

Office 365 integrations

Hi Guys,
I am about to setup a pilot and wanted to ask a few questions.
I am planning a multi-domain exchange deployment...where I am hosting my main email on site with a domain of company.com and I want to host 1.company.com and 2.company.com on my office 365 Exchange online implementation. To do this do I have to define the
new domains on my current exchange server and then setup the users on office 365?
one of the things that my user base wants is single sign on but they won't be using rich clients. I know this works well for rich clients, but can single sign on also sign on to Office 365 web and one drive?
I will be implementing ADFS and DIrSync for AD replication and ADFS for single sign on.
How does licensing work? if my entire directory replicates to Office 365 and I only want some users over there activated, how do those I want activated. Can I easily activated a bunch of users for only some services at one time? If I deactivate or delete
an account locally, will those changes take at office 365? How does that work with licensing? do my licenses get automatically freed up?

Hi,
For this issue, I recommend you post to Office 365 forum which is staffed by more experts specializing in this kind of problems, you might get better help there. Thanks for understanding.
http://community.office365.com/en-us/forums/default.aspx
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Belinda Ma
TechNet Community Support

Exchange Online Office 365 integration questions

Hi Guys,
I am about to setup a pilot and wanted to ask a few questions.
I am planning a multi-domain exchange deployment...where I am hosting my main email on site with a domain of company.com and I want to host 1.company.com and 2.company.com on my office 365 Exchange online implementation. To do this do I have to define the
new domains on my current exchange server and then setup the users on office 365?
one of the things that my user base wants is single sign on but they won't be using rich clients. I know this works well for rich clients, but can single sign on also sign on to Office 365 web and one drive?
I will be implementing ADFS and DIrSync for AD replication and ADFS for single sign on.
How does licensing work? if my entire directory replicates to Office 365 and I only want some users over there activated, how do those I want activated. Can I easily activated a bunch of users for only some services at one time? If I deactivate or delete
an account locally, will those changes take at office 365? How does that work with licensing? do my licenses get automatically freed up?

Hi Emil,
Thank you for your question.
There are two sentences I don’t understand:
Leave both environments as is
Would this work also (X500 addresses would be written and updated, move requests would work, F/B, etc)?
AD trust is important for us to share organization information between ADs.
AAD has capability which AD and Exchange multi-forest forest environment can be extended to cloud, so we could not run it in both AD environment. There is a alternative solution which use FIM. We could refer to the following link:
http://azure.microsoft.com/en-us/documentation/articles/active-directory-whatis/
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Jim Xu
TechNet Community Support

Creating Distribution List and Member in Office 365

Hi Guys,
My requirements is to write the .Net web-service through which i need to creating the below in office 365 programmatically. Can anyone suggest which way to go. I know there are Rest Web service for it but i need to know whether we can do it through Office
365 API's.
1) Distribution List
2) Member

You cannot create or modify distribution lists in the Global Address List via the Office 365 APIs. You would need to use PowerShell cmdlets to do this.

Project Server (Office 365): timesheet with 0 hours actual work cannot be modified - bug or "feature"

Hi,
One of our PMs is trying to change a task in his project plan and gets the following message: "cannot delete or reassign tasks or assignments with protected actuals" . This would normally be ok since we have setup actual work to be reported only
through the timesheets but....when checking actual work on this task, there is only 1 resource allocated and he reported no hours. Interestingly, it shows 0 in the actual work and it's not empty (as you would expect if you dont report hours).
We tried to recall the timesheets of that resource and resubmit them (without any hours again) but that didnt work either. Idea good ideas?
Thanks
Choc
Chocob21

Hi,
has user changed "Remaining Work" to 0? I have not tested, but I assume that cause 0 displayed as Áctual Work and stops you from deleting task.
Regards
Barbara
To increase the value of this forum, please mark the replies that helped to solve your issue as answer. If you find answers to questions from other forum participants to be helpful, please mark them as helpful. Your participation will help others to find
an appropriate solution faster. Thanks for your support!

Office 365 Features after Windows Server Standard Transition

Hi all,
I am looking to transition from Windows Server 2012 R2 Essentials to Standard as per
http://technet.microsoft.com/en-us/library/jj247582.
The article calls out explicitly that the media features are removed from the web access site and disabled in the dashboard after the transition but there is no clarification of anything relating to Office 365.
Does the built-in version of DirSync in Essentials continue to function for synchronising on-premise passwords and users to the Office 365 Tenant after the transition?
I would assume that they do given that there is no mention of the features in the transition article but I would like some reassurance. It would be nice to hear from someone who has actually attempted this to know if there are
any other features or faults in the process?
Richard Green | MCSA 2012, MCSE 2003, MCTS Desktop Virtualization, VCP5-DV http://richardjgreen.net

yes, the office 365 integration components continue yo work.
Hi Cliff, thanks for the response.
Do you know what happens when the media features are removed? When the media features are first enabled, it creates three new shares called Music, Pictures and Videos on the server.
When the media features are removed by the Standard transition, are these shares disabled, removed or are the underlying NTFS folders actually deleted at all? Obviously I would have a backup going into this but it would be nice to understand the behaviour
fully.
If might be worth an update to the TechNet article to explain the behaviour to the media shared folders as well as the media feature itself.
Richard Green | MCSA 2012, MCSE 2003, MCTS Desktop Virtualization, VCP5-DV http://richardjgreen.net

[Forum FAQ] How to install and configure Windows Server Essentials Experience role on Windows Server 2012 R2 Standard via PowerShell locally and remotely

As we all know,
the Windows Server Essentials Experience role is available in Windows Server 2012 R2 Standard and Windows Server 2012 R2 Datacenter. We can add the Windows Server
Essentials Experience role in Server Manager or via Windows PowerShell.
In this article, we introduce the steps to install and configure Windows
Server Essentials Experience role on Windows Server 2012 R2 Standard via PowerShell locally and remotely. For better analyze, we divide this article into two parts.
Before installing the Windows Server Essentials Experience Role, please use
Get-WindowsFeature
PowerShell cmdlet to ensure the Windows Server Essentials Experience (ServerEssentialsRole) is available. (Figure 1)
Figure 1.
Part 1: Install Windows Server Essentials Experience role locally
Add Windows Server Essentials Experience role
Run Windows PowerShell as administrator, then type
Add-WindowsFeature ServerEssentialsRole cmdlet to install Windows Server Essentials Experience role. (Figure 2)
Figure 2.
Note: It is necessary to configure Windows Server Essentials Experience (Post-deployment Configuration). Otherwise, you will encounter following issue when opening Dashboard.
(Figure 3)
Figure 3.
2. Configure Windows Server Essentials Experience role
(1) In an existing domain environment
Firstly, please join the Windows Server 2012 R2 Standard computer to the existing domain through the path:
Control Panel\System\Change Settings\”Change…”\Member of. (Figure 4)
Figure 4.
After that, please install Windows Server Essentials Experience role as original description. After installation completed, please use the following command to configure Windows
Server Essentials:
Start-WssConfigurationService –Credential <Your Credential>
Note: The type of
Your Credential should be as: Domain-Name\Domain-User-Account.
You must be a member of the Enterprise Admin group and Domain Admin group in Active Directory when using the command above to configure Windows Server Essentials. (Figure 5)
Figure 5.
Next, you can type the password for the domain account. (Figure 6)
Figure 6.
After setting the credential, please type “Y” to continue to configure Windows Server Essentials. (Figure 7)
Figure 7.
By the way, you can use
Get-WssConfigurationStatus
PowerShell cmdlet to
get the status of the configuration of Windows Server Essentials. Specify the
ShowProgress parameter to view a progress indicator. (Figure 8)
Figure 8.
(2) In a non-domain environment
Open PowerShell (Run as Administrator) on the Windows Server 2012 R2 Standard and type following PowerShell cmdlets: (Figure 9)
Start-WssConfigurationService -CompanyName "xxx" -DNSName "xxx" -NetBiosName "xxx" -ComputerName "xxx” –NewAdminCredential $cred
Figure 9.
After you type the commands above and click Enter, you can create a new administrator credential. (Figure 10)
After creating the new administrator credential, please type “Y” to continue to configure Windows Server Essentials. (Figure 11)
After a reboot, all the configurations will be completed and you can open the Windows Server Essentials Dashboard without any errors. (Figure 12)
Figure 12.
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Part 2: Install and configure Windows Server Essentials Experience role remotely
In an existing domain environment
In an existing domain environment, please use following command to provide credential and then add Server Essentials Role: (Figure 13)
Add-WindowsFeature -Name ServerEssentialsRole
-ComputerName xxx -Credential DomainName\DomainAccount
Figure 13.
After you enter the credential, it will start install Windows Server Essentials role on your computer. (Figure 14)
Figure 14.
After the installation completes, it will return the result as below:
Figure 15.
Next, please use the
Enter-PSSession
cmdlet and provide the correct credential to start an interactive session with a remote computer. You can use the commands below:
Enter-PSSession –ComputerName
xxx –Credential DomainName\DomainAccount (Figure 16)
Figure 16.
Then, please configure Server Essentials Role via
Add-WssConfigurationService cmdlet and it also needs to provide correct credential. (Figure 17)
Figure 17.
After your credential is accepted, it will update and prepare your server. (Figure 18)
Figure 18.
After that, please type “Y” to continue to configure Windows Server Essentials. (Figure 19)
Figure 19.
2. In a non-domain environment
In my test environment, I set up two computers running Windows Server 2012 R2 Standard and use Server1 as a target computer. The IP addresses for the two computers are as
below:
Sevrer1: 192.168.1.54
Server2: 192.168.1.53
Run
Enable-PSRemoting –Force on Server1. (Figure 20)
Figure 20.
Since there is no existing domain, it is necessary to add the target computer (Server1) to a TrustedHosts list (maintained by WinRM) on Server 2. We can use following command
to
add the TrustedHosts entry:
Set-Item WSMan:\localhost\Client\TrustedHosts IP-Address
(Figure 21)
Figure 21.
Next, we can use
Enter-PSSession
cmdlet and provide the correct credential to start an interactive session with the remote computer. (Figure 22)
Figure 22.
After that, you can install Windows Server Essentials Experience Role remotely via Add-WindowsFeature ServerEssentialsRole cmdlet. (Figure 23)
Figure 23.
From figure 24, we can see that the installation is completed.
Figure 24.
Then you can use
Start-WssConfigurationService cmdlet to configure Essentials Role and follow the steps in the first part (configure Windows Server Essentials Experience in a non-domain environment) as the steps would be the same.
The figure below shows the status of Windows Server Essentials.
Figure
25.
Finally, we have successfully configured Windows Server Essentials on Server1. (Figure 26)
Figure 26.
More information:
[Forum
FAQ] Introduce Windows Powershell Remoting
Windows Server Essentials Setup Cmdlets
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Search SharePoint 2013 On-Prem with Office 365

We're trying to understand federated search in SharePoint 2013, when it comes to Office 365. We have both a SharePoint 2013 on-prem environment, and an Office 365 environment. The 2 are completely separate, and have not been configured to use a hybrid model.
Is it possible to configure a Result Source in either the SharePoint environment or the Office 365 environment to index the other? Reading this
article from Technet, it indicates that you can configure a remote SharePoint farm as a Result Source:
"Remote SharePoint provides
results from the index of a search service in another farm."
But I've read on another
thread on here that this is not possible from O365.
I'm hoping that someone can provide some guidance, or point me in the right direction.
Thanks,
cflbasser

Yes, you can receive search results from an on-premise SharePoint Server 2013 farm within SharePoint Online.
Hybrid search between SharePoint Server and SharePoint online uses federated search results. Neither the on-premise farm nor SPO crawl the other location, they just send a federated search query over the fence and wait for the results.
You can search in either direction (one-way hybrid search) or both ways (bidirectional hybrid search).
The one-way search can either be SharePoint Server sending search queries to SPO or SPO sending queries to SharePoint Server which also needs a reverse proxy for securely publishing your on-premise farm to SPO.
Bi-directional hybrid search just combines both one-way methods together so either location can receive search results from the other location.
Here are some further resources to help you plan and implement hybrid search:
Hybrid for SharePoint Server 2013
Configure hybrid Search for SharePoint Server 2013
Chris O'Brien has an excellent article that describes the actual search experience. Check out Office 365 SharePoint hybrid - what you
DO and DO NOT get
Jason Warren
@jaspnwarren
jasonwarren.ca
habaneroconsulting.com/Insights

Essentials Experience on member server - Office 365 Integration

Similar Messages

Maybe you are looking for