Search Crawl Scheduling and information
Admins need further control over the search crawl in SharePoint Online. Dates and times when the crawl has run, current status, errors etc are all required by search managers to managed the search service. The ability to run incremental or full crawls and to edit the schedule are also needed.
Paul Brown
shared this idea
7 comments
-
Ali Raza
commented
Agree, SP admins really need access to manage the crawl schedule. One of the toughest question to respond to business users...
-
[Deleted User]
commented
The fact this doesn't exist means its not an enterprise solution in my books.
-
Jennifer Hubley
commented
We also need the ability to access crawl log information, we also cannot tell a user "just wait 24 hours and tell us if it's working now" - the reason we picked SharePoint was to be able to share and collaborate on documents in real time, not a day later. We need the ability to access the crawl logs, and create some error reporting and troubleshooting so we can get to the problem before the customer does.
-
Jessica Guglielmino
commented
The crawl speed is incredibly frustrating when you're sequencing communications across different platforms, all hinging on an intranet article that's not showing up. Placing a ticket doesn't satisfy the time-sensitivity. We need a way to push the crawl.
-
Anonymous
commented
It would be a nice feature to remove preview images from Delve immediately (or at least configurable) after it has been deleted or unshared with you.
-
Anonymous
commented
we face a a problem with our intranet news. Content editors publish a news items and then have to hope that search crawl picks it up quickly to display on intranet news web part. Sometimes it take 15 mins, sometime many ours. We raised a support ticket to Microsoft on this and the answer was to get in touch if it takes more than 24 hours. This is not acceptable for time critical news items which should be visible very quickly and we would like to be able to force the search crawl to pick up high priority items.
-
Kyle Bakker
commented
This is so frustrating. So much so I put a vid about it on the youtubes. https://youtu.be/fBDq2N4ppx4
There is a script now that lets you re-index the farm.
I have attached the script, or you can get it from Git Hub.
https://github.com/wobba/SPO-Trigger-Reindex
It does require the CSOM Package found here: http://aka.ms/spocsom
Depending on when you got the CSOM Package it may have put files in the 15 directory, in which case you can do nothing but run the script.
If you download the recent CSOM package, it is put in the 16 directory, so you need to update the script to correct the path on line 106.
c:\Program Files\Common Files\microsoft shared\Web Server Extensions\16\ISAPI