Skip to main content

Enable Search indexing on your TFS Sharepoint Team Site

A few weeks ago, one of my customers sent me the following screenshot mentioning that they couldn’t search for information on their Team Foundation Server Sharepoint site.

image

In order for search to work you do need to assign search to an indexer. This typically means specifying the server name where the indexing service is running. If you have a single-server installation then that single server of course.

  • Open the Sharepoint Central Administration website.
  • Go to Operations
    • Click on Services on Server under Topology and Services
    • Click on Start next to the Windows Sharepoint Services Search
      • Enter a Service Account
      • Enter a Content Access Account
      • Leave the default Search Database selected(or select a new one)
      • Configure the indexing Schedule
      • Click Start
  • Go to Application Management
    • Click on Content databases under Web Application Management
    • Click on the Content database
      • Select the server under Search Server
      • Click OK to apply the changes

Popular posts from this blog

DevToys–A swiss army knife for developers

As a developer there are a lot of small tasks you need to do as part of your coding, debugging and testing activities.  DevToys is an offline windows app that tries to help you with these tasks. Instead of using different websites you get a fully offline experience offering help for a large list of tasks. Many tools are available. Here is the current list: Converters JSON <> YAML Timestamp Number Base Cron Parser Encoders / Decoders HTML URL Base64 Text & Image GZip JWT Decoder Formatters JSON SQL XML Generators Hash (MD5, SHA1, SHA256, SHA512) UUID 1 and 4 Lorem Ipsum Checksum Text Escape / Unescape Inspector & Case Converter Regex Tester Text Comparer XML Validator Markdown Preview Graphic Color B

Help! I accidently enabled HSTS–on localhost

I ran into an issue after accidently enabling HSTS for a website on localhost. This was not an issue for the original website that was running in IIS and had a certificate configured. But when I tried to run an Angular app a little bit later on http://localhost:4200 the browser redirected me immediately to https://localhost . Whoops! That was not what I wanted in this case. To fix it, you need to go the network settings of your browser, there are available at: chrome://net-internals/#hsts edge://net-internals/#hsts brave://net-internals/#hsts Enter ‘localhost’ in the domain textbox under the Delete domain security policies section and hit Delete . That should do the trick…

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.