Make sure you tell it to ignore your search indexes and other SharePoint areas! See: http://support.microsoft.com/kb/952167 To be sure it is not hitting your index location, you can check where that is currently set by: Central Admin -> Application Management -> Manage service applications...

# Get_UserProfileServices.ps1 # Dump out any info I can glean from the User Profile Synch for SharePoint. # # LukeB # http://technet.microsoft.com/en-us/library/ee721049.aspx # if ((Get-PSSnapin "Microsoft.SharePoint.PowerShell" -ErrorAction SilentlyContinue) -eq $null) { Add-PSSnapin "Microsoft.SharePoint...

In the event of a server death, you may need to move your Search Admin to another server. This is actually fairly easy: $searchapp = Get-SPEnterpriseSearchServiceApplication "Sample Search Service Application" $admin = Get-SPEnterpriseSearchAdministrationComponent -SearchApplication $searchapp...

Josh Gavant is writing a series on CLAIMS that makes it all rather clearer. http://blogs.msdn.com/b/besidethepoint/archive/2012/05/02/sharepoint-claims-ws-and-the-windows-identity-foundation-wif.aspx

In what order does one update when including Language Packs? With Service Packs? With Cumulative Updates? It used to be confusing. Now with 2010 it is straightforward. Get the language packs: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=3411 now update your farm as desired...

yet again I am astonished at how useful the LogParser utility is, when delving into SharePoint performance and troubleshooting. Looking into PSCONFIG logs to spot errors turns out to be surprisingly simple. First example displays the fields in the file, to ensure we have the right bits. Second example...