Who's Online
20 visitors online now
3 guests, 17 bots, 0 members
Support my Sponsor

Archive for June, 2015

Hybrid Delve and Search are coming to SharePoint 2016 and SharePoint 2013

Hi All,

As you all know that Hybrid Delve and Search are coming to SharePoint 2016 and SharePoint 2013. Hope below additional details can be of help.

 

What is Cloud search service application?

If you plan to use Hybrid Delve and Search feature then you will have to create a Cloud Search Service Application. As far as I know key source behind Delve (Office Graph) for Delve won’t be available On Premises SharePoint.

 

How does it work?

I see a lot of concern where people ask if the crawled content would remain on Cloud server or On-premises SharePoint server. The content itself remains On-Premises and the indexed metadata is unified in a Cloud Index in Office 365. This mean crawled content resides in your environment but their index resides on Office 365 servers.

Now another concern is what happens to sensitive data which will be crawled. Its indexes would move to cloud which may not be accepted to everyone.

For sensitive content it would be recommended to not index this content using the Cloud SSA. The Combining Hybrid search approaches can use the current Query federation approach for the hybrid scenario should this need to be queried from SharePoint Online.

 

What would be an Ideal scenario if you plan to SharePoint 2016 Cloud Search Service Application?

Bill Baer says “I wouldn’t approach the new hybrid search experience as sending the entirety of your content to the unified index in SPO, just the “indexed” content, I.e. the first 100K – as related to selectively sending content to the unified index, yes, that can be achieved with the new hybrid cloud Search SA – the number of servers on-premises as related to scale-related considerations is dependent on your own throughput needs, but can be as few as a single server running either SharePoint 2013 and/or SharePoint 2016 which can serve as a proxy to legacy content sources such as SharePoint 2010. Since the index is unified in SPO and the results returned by Office 365 you can also potentially reduce the scale of your existing search architecture and let the service do the heavy lifting of storing and returning results.”

To summarize, if you have lot of content which does not contain sensitive information and your company is ready for Hybrid approach you can crawl Hugh amount of data but your search architecture would be very small because half of the load(Index and Query) would be taken by Office 365 servers. Here you will get a very good search performance even if you have single SharePoint environment.

 

What is required for Cloud search service application?

You need On-Premises SharePoint environment and Office 365 subscription to use Cloud search service application.

 

Hope this will help you with your SharePoint 2016 planning.

 

No SharePoint Foundation 2016

Hi All,

 

We all know SharePoint Designer 2013 is the last version of SharePoint Designer available to us. Now another big hit is SharePoint Foundation 2013 is also the last free version of SharePoint product available with us.

 

I just got confirmation that Microsoft would not release SharePoint Foundation 2016 along with SharePoint Server 2016. This is a big hit to companies who use SharePoint foundation in their current organization and planned to upgrade to SharePoint Foundation 2016. I very well know that a very big SharePoint market uses SharePoint Foundation because it is free and it has great features.

 

If you use SharePoint Foundation and you want Microsoft to continue SharePoint Foundation product, you can tweet @williambaer or email him at wbaer@microsoft.com. That’s your only chance where you need to show Microsoft how you use SharePoint foundation, how does it benefit you and why Microsoft should continue this product line

 

Hope this will help you with your SharePoint 2016 planning.

Keyword Query text limit in SharePoint Search

Hi All,

I was recently asked if we have any limit for Query text we use to perform search in SharePoint.

After some research I found that the length limit of a KQL query varies depending on how you create it. If you create the KQL query by using the default SharePoint search front end, the length limit is 2,048 characters. However, KQL queries you create programmatically by using the Query object model have a default length limit of 4,096 characters. You can increase this limit up to 20,480 characters by using the MaxKeywordQueryTextLength property or the DiscoveryMaxKeywordQueryTextLength property (for eDiscovery).

Again the length of FAST Query Language queries is limited to 2,048 characters.

This applies to SharePoint 2010, 2013

Reference : https://msdn.microsoft.com/en-us/library/office/ee558911.aspx

Note: You cannot modify this value in Office 365 SharePoint site

 

SharePoint “Add to timeline” option is disabled\Grayed out on Project site

 

Hi All,

Recently I found a issue where “Add to timeline” option is disabled on Project site.

After some research I found that in order to do enable “Add to timeline”, the user must have the permission to “manage” list, the contribution is not enough!

A user with contributor permission will see the option grayed out and won’t be able to use it.

Hope this will be helpful

Prepare Seeds for Tree plantation

Hi All,

Today we will understand how we can prepare some dry seeds in case we wish to plant trees.

We will 1st collect seeds from different fruits and vegetables. I collected some orange seeds as shown below:

tree1

Now we will wash it properly. Motive is to make sure seeds don’t carry any pulp or it might have fungus on it. Check the image below:

tree2

Once we wash the seeds, we will dry them using some napkin or cloth and keep it under sunlight for a day or 2. Seeds must be carefully dried and then stored under the proper conditions in order to give them the best chances of germinating and producing healthy plants when they are planted.

tree3

Dry your seeds thoroughly before storing them. If seeds sweat on insides of jars during storage, they are too wet and must be dried further in order to store successfully.

 

Thanks everyone for helping us save planet.

SharePoint : Redirect to different home page for authenticated users

Hi All,

Today I got a requirement where authenticated users should be redirected to a different page, here is how I achieved it.

Editing the exiting SharePoint Landing page, then add a new content editor Web Part on the page. Now edit the content editor webpart and click on Web part properties on top. Now select “Embed code” under Insert for content editor webpart, add below script in :


<meta http-equiv=”refresh” content=”5;url=http://sharepoint/SitePages/Home.aspx”>


Try to check if your site is redirect to the new site.

If the redirection is working fine then we will restrict this script only for authenticated users. We need to edit the page again and select Edit webpart. Under Advance setting Set Target Audience as “NT Authenticated users”

Hope this helps you.