Protected: Preserving Policy Settings in SharePoint
October 25, 2011
Protected: Watch Your SharePoint Practices
October 24, 2011
Protected: Avoid SharePoint Burnout With Efficient Planning
October 21, 2011
Protected: Give Your SharePoint Documents an ID Card
October 20, 2011
Protected: Survey: SharePoint at Work with Some Surprises
October 18, 2011
Protected: SharePoint APIs: The Key to User Satisfaction
October 17, 2011
FAST Error Message – Makes No Sense
October 14, 2011
A blog devoted to SharePoint and related technologies is shedding light on SharePoint’s failure to handle error messaging. In, “FAST Post Setup Configuration Failed,” several weaknesses of the SharePoint error messaging system are discussed.
The author states,
In one of my recent FAST implementations to a large Government Organization in Western Australia, I faced numerous interesting issues and would like to share them with the SharePoint community [sic] in my next few articles. In my viewpoint, even though FAST is a very powerful and useful component when it comes to integration with SharePoint, it need some major improvements, fixes and specially better error handling.
FAST needs to take another look at their error messaging system. In the meantime, users struggling with less-than-helpful messages may find this article quite helpful.
Emily Rae Aldridge, October 14, 2011
Protected: Attention! Attention! Another SharePoint 2010 Update Package
October 14, 2011
Protected: How Multiple-Users Can Edit One SharePoint Document
October 13, 2011
SharePoint Best Practices and Beyond
October 12, 2011
No matter the extent of your search implementation challenges, our team at Search Technologies has the processes and technologies to deliver results.
A series of Best Practices articles for SharePoint Server 2010 by Microsoft TechNet includes an article on the best practices for enterprise search, “Best Practices for Search in SharePoint Server 2010.” The article also applies to Microsoft Search Server and covers everything from the deployment to antivirus policies.
Some useful information is covered; one learns to test the crawling and querying subsystems after changing any configuration or applying updates:
We recommend that you test the crawling and querying functionality of the server farm after you make configuration changes or apply updates. An easy way to do this is to create a temporary content source that is used only for this purpose. To test, we recommend that you crawl ten items — for example .txt files on a file share — and then perform search queries for those files. Make sure that the test items are currently not in the index.
Management also needs to be aware of planning the search topology, planning for capacity and performance, and planning for findability. Users must be able to easily find what they are looking for, and managed properties and scopes will enhance the end-user search experience. You must start with a well-configured infrastructure. Defragmenting the search database after a series of crawls and queries can help with content management.
Overall, it is important to test the subsystems, be prepared, and review the anti-virus policy to avoid any unexpected problems.
For more articles in the series, see Best practices (SharePoint Server 2010).
You will want to tap into the expertise garnered in more than 100 Fast search deployments by our team at Search Technologies. That’s where Search Technologies comes into the spot light. We have more experience than any other firm in implementing search best practices for SharePoint licensees. Contact us at www.searchtechnologies.com.
Iain Fletcher, Vice President, Search Technologies October 12, 2011
Search Technologies is the world’s largest independent provider of search engine expertise, consulting and implementation services.
-
- Subscribe to Beyond Search
Feature archive
News archive
-
