In case you are wondering why the search service needs to crawl the permissions of content, as well as the content itself, it is because it uses these permissions to trim search results for users who do not have access to content. You will see in the policy screen that the “Search Crawler” account has “Full Read” access. You can verify this by looking at any web application in Central Administration (except for central administration web application) and choosing “User Policy” from the ribbon. This way, no matter how draconian the permissions of site collections are, the crawler account will have the access it needs to crawl the content, as well as the permissions of that content. Once you have provisioned the Search Service Application, the default content access (in my case SEVENSIGMA\searchservice), it is granted “Read” access to all web applications via Web Application User Policies as shown below.
#DELETE AND RE DOWNLOAD OFFICE 2011 WINDOWS#
Once the service has been successfully provisioned, we can clearly see the “Default content access account” is based on the “Search service account” as described in the configuration above (the first of the three accounts).įinally, as you can see below, once provisioned, it is the SharePoint farm account that is running the search windows service. You can see this in the screenshots below. Search query and site settings account: SEVENSIGMA\searchqueryss.Search admin web service account: SEVENSIGMA\searchadminws.Search service account: SEVENSIGMA\searchservice.The next set of pictures show the Search Service Application provisioned according to the following configuration: First up, I show below where SharePoint has been installed and the SharePoint Server Search 14 service is disabled and with service credentials of “Local Service”. You can see the pre and post provisioning status below. The reality is that the SharePoint Server Search 14 service account is the farm account. In reading this, suggests that the windows service (“SharePoint Server Search 14”) would run under this account. You can change this account from the Service Accounts page under Security section in Central Administration.” This setting affects all Search Service Applications in the farm. the Windows Service account for the SharePoint Server Search Service. Now the search service account is described as so: “. By default this is the account that will do the crawling of content sources. First up we choose to create a search service application, and then we choose the account to use for the “Search Service Account”. Below shows the point in the GUI based configuration step where this is done. When you provision a search service application as part of a SharePoint installation, you are asked for (among other things), a windows account to use for the search service. If you prefer a more gentle stroll through SharePoint search land, then read on…
#DELETE AND RE DOWNLOAD OFFICE 2011 PRO#
If you consider yourself a legendary IT pro or SharePoint god, feel free to skip this bit. There are articles out on this topic, but none that I found are particularly comprehensive. I thought it was worth explaining the crawl process a little and talking about the most likely ways in which is will break for you, in order of likelihood as I see it. Today I had to troubleshoot a broken SharePoint people search for the first time in a while. So in between trying to get my book fully edited ready for publishing, I might squeeze out the odd technical SharePoint post. I’ve been nerding it up lately SharePointwise, doing the geeky things that geeks like to do like ADFS and Claims Authentication.
0 kommentar(er)
