Clearing items from a specific content source. On your Search Service Application, that be the standard SharePoint Search or FAST for SharePoint has a link called Index Reset which will clear all the searchable items in your index. For FAST Search for SharePoint you would have to call Clear-FASTSearchContentCollection on the FS4SP farm as well via PowerShell. This is all fine if you want to remove everything, but sometimes you may want to only remove parts of the index, say only items from a particular content source like SharePoint or your file server. The trick to achieve this is to remove the start addresses from a search location, and then re-add them.
When you remove a start address from a content source, it triggers a delete mechanism which will remove all items from that particular start address. Here’s a sample PowerShell script which will remove all items from my File server content source called File residing on my Search Service Application called FASTContent. $sourceName = "File" $contentSSA = "FASTContent" Whitepaper: SharePoint 2010 User Management - SharePoint 2010.
Introduction Microsoft SharePoint is a platform for building and deploying collaborative solutions. It is a centralized Web portal that tracks content and documents as well as users, audiences, and teams. One of the major challenges for the SharePoint IT administrator is to understand and effectively manage SharePoint user access along with the multiple directory services that coexist within the corporate network, including numerous Web applications, sites, and multiple authentication servers. Since an increasing number of companies are deploying SharePoint on a global enterprise network, connecting a large number of users and, in the process, creating a structure of corporate hierarchy-based users as well as a formidable social network, user access must be regulated and managed effectively. This article provides a detailed look at how users and security are managed and configured within SharePoint.
Contents SharePoint Architecture Figure 1 - SharePoint 2010 Architecture. Pilots, Proof of Concepts, Test, and Pre Production Environments - Joel Oleson's Blog - SharePoint Land.
SP+PS 2010: Understanding Features - Zach Rosenfield's SharePoint Blog. Managing SharePoint 2010 Farm Solutions with Windows PowerShell | SoftArtisans. In SharePoint 2007, you can manage solutions using the stsadm command. In SharePoint 2010, stsadm still works, but is deprecated in favor of PowerShell cmdlets. Whereas with stsadm you use a command-line switch to specify the operation to perform, with PowerShell you use separate cmdlets.
Below are the list of stsadm commands and equivalent PowerShell commands for common tasks to manage a farm solution. SharePoint 2010 also includes support for sandbox solutions. When running a cmdlet, the cmdlet returns right away, but the operation will take some time to complete. To get further information on a cmdlet, for instance add-spsolution, just type get-help add-spsolution in PowerShell. Adding solution to the solution store Prerequisite: None Because of the way PowerShell handles file path, the cmdlet’s -literalpath switch only accepts a full path to the WSP file. Deploying solution Prerequisite: The solution has been added to the solution store. Upgrading solution Retracting solution.
Nice sites. Maintenance. Installation and Configuration.