Microsoft is pushing O365, and it's no secret that's where the new investments are. But, what is the story for those still using SharePoint 2013 on-premises? Should they stay, should they upgrade to 2016, should they move to the cloud, or is going hybrid the end goal and not a step on the way to going all-in for O365?
23. Web Front End Services end user requests, optimized for low latency.
Search Reserved for Search services.
Application Services the backend jobs or the requests triggered by backend
jobs, optimized for high throughput.
Distributed Cache
Special Load Reserved for services to be isolated from other services, I.e. 3rd
party, PerformancePoint, etc.
Single Server
Farm
Provisions all services on the server for a single server
deployment. This role is provided for evaluation and development
purposes.
Minrole
LOB being: fileshare, ERP, custom database
…or me and SharePoint
Here I show two-way bidirectional trust
Also possible with
One way outbound (can see SPO locally)
One way inbound (can see local result in SPO)
Redirect based on audiences
Two environments to maintain
Support
Technical maintenance
Cost?
Available in 2016, but also for 2013 if you install August 2015 PU
S2S – the outbound connection we saw previously
You can kill all but the crawling server(s) and use the index in SPO instead
Can not do ANY entity extraction which Benjamin talked about for metadata enrichment earlier today
Wizard to easy the inbound setup
Are you allowed to store data outside your country?
Example: Norwegian archiving
Create a plan for what your end game is and aim for it…..!! If cloud is your endgame, treat hybrid as a stepping stone.