Month: October 2010

FAST Search Server for SharePoint–Number of Items Indexed

Having set up the FAST Search Server for SharePoint, I can tell you it is an interesting ordeal.  Because the product was purchased by Microsoft and productionalized for SharePoint, there are a few gotchas in the product like having to use FQDN domains for the User IDs and some fun with certificates. However, once you’ve got the system up, running and integrated with SharePoint it is a very useful and powerful product. One useful tool in your administration bag is the IndexerInfo.exe, which is useful when retrieving basic information about the number of items indexed or the status of the indexing process. In order to use this tool, you have to log onto the FAST server and run the executable located here: <FASTSearchFolder>\bin\indexerinfo And that will give you some pretty useful basic information about your server’s index, such as total number of items indexed: However, the tool has two drawbacks: You have to log into the server to use it. It doesn’t have a lot of granularity or visibility to SharePoint scopes and permissions. In many cases, a great workaround for this is to use your SharePoint Search which is using the FAST engine and simply query for the ‘#’ character. And this should give you a ball-park figure of how many items are in your index.  You’ll notice though that the numbers are slightly different.  If I were...

Read More

SharePoint 2010 : Connect to Another Farm’s User Profile Service

Recently I had to review and configure two SharePoint 2010 farms to use the same User Profile Service.  The Publishing Farm was a large enterprise level farm that was used company wide.  The other was a smaller, single server farm that ran the Team Foundation Server 2010 SharePoint sites.  Rather than moving the SharePoint assets to the large enterprise farm, The Client wanted the TFS SharePoint farm to utilize the User Profile Services of the larger farm and to have the mysites and profiles features integrated within the smaller TFS sharepoint sites. Now, before any farm can provide its...

Read More

SharePoint 2010–Use PowerShell to Provision a Central Admin site

Recently I was working on a SharePoint 2010 farm where I accidently removed the last server that hosted Central Admin.  Whoops!  Now I had a farm with no Central Admin UI.  Now the Central Admin SharePoint Service is installed on every WFE by default, but is only enabled on the machines that you identify.  I went ahead tried to run the psconfig on the server and tried to re-add it, however the install checks were telling me that it could not be joined due to a patch level inconsistency (more on that in a different post).  End result was that I was sitting with a farm that did not have a Central Admin site configured… The following PowerShell command will provide a list of all servers that have the Central Administration service installed, their status, and the Id: Get-SPServiceInstance | Where-Object {$_.TypeName -eq 'Central Administration'} TypeName Status Id ——– —— – Central Administration Disabled 2d35f287-8d0f-4474-8a38-2dc2365c06e7 Central Administration Disabled 2052cc79-fce8-483a-83e4-9802db535237 The service instance can be started using the following PowerShell command, again restricted to the Id of the service instance I want.  Doing this will provision Central Admin on the WFE that it correlates with: Get-SPServiceInstance | Where-Object {$_.Id –eq ‘2d35f287-8d0f-4474-8a38-2dc2365c06e7’} | Start-SPServiceInstance Get-SPServiceInstance | Where-Object {$_.Id –eq ‘2052cc79-fce8-483a-83e4-9802db535237’} | Start-SPServiceInstance This will start provisioning the service instance, which usually means creating the Central Administration website on the web front-end...

Read More