MS Sharepoint Search word-stemming

Word stemming is turned off by default. If you want to turn on word stemming, here's how:
* Go to the search page, enter any old query to return the search results page
* Under Site Actions, select 'Edit page'
* Locate the 'Search Core Results' web part (usually in the bottom zone)
* From the Edit button, select 'Modify shared web part' * In the tool bar on the right hand side, under 'Results Query Options', check the box labeled 'Enable Search Term Stemming

MOSS2007 Admin Toolkit

Download admin toolkit from the below URL

http://blogs.technet.com/b/steve_chen/archive/2009/09/02/sharepoint-administration-toolkit-v4-for-moss-2007.aspx

SharePoint 2010 Multi Language User Interface

http://www.davessharepoint.com/2010/07/sharepoint-2010-multi-language-user.html

Windows 7 Prompting for Authentication When Accessing SharePoint Documents

follow below URL to resolve the problem

http://www.quantumofgeek.com/2010/02/windows-7-prompting-for-authentication-when-accessing-sharepoint-documents/

Disable MySite and MyLinks in Sharepoint (MOSS) 2007

In order to turn off or disable the MySite or MyLinks functionality you need to be an Sharepoint administrator.

Go to the Central Administration Web Page
Click on the link for Shared Services Administration
--If you have more than one SSP, select the one that is running the MySites functionality
Under "User Profiles and My Sites" click Personalization Services Permissions

Select the group you want to limit the functionality for. More than likely you will just have NTAuthority\Authenticated Users.

In the next screen you will see a list of checkboxes,
--To disable MySites uncheck "Create Personal Site"
--To disable MyLinks uncheck "Use Personal Features"

Sharepoint Web Part Maintenence Page URL

You can just append "?contents=1" to the web part page.

SharePoint Used Space Information

SharePoint Used Space Information is a console application which allows to retrieve information about space used (bytes) by all sites and sub-sites for a specific site collection into .csv files.

This tool uses the StorageManagementInformation method of the SPSite class to retrieve the usage information.

Please follow the below link to get the downloadle file from Codeplex

http://spusedspaceinfo.codeplex.com/

User Profiles not in sync with site collections after a name / property change

At one of our customers we had a sync problem with the user profiles and the wss 3.0 user profile store on site collection level. To check which content databases were out of sync we used the common
stsadm -o sync -listolddatabases 5

This shows a list of all the databases that are out of sync. By using
stsadm –o sync –deleteolddatabases 5
you can delete those userprofilesync databases (not the content database itself and by then running something like)
stsadm –o sync –synctiming M:5
stsadm –o sync –sweeptiming M:5

you should see your userprofile syncing in 5 minutes. Except for the fact that in this case it didn’t do the trick. Whenever I used domain\username in the people picker, it resolved to the old username and not the new one. Some blogs talk about a full server restart, but as it is a large production environment (and the fact that the issue isn’t realy blocking business) that was not an option. In the end, adding the user with the domain\accountname to a SharePoint group it resolved to the old name. However, 5 minutes later the old name was replaced with the new name and the profile was in sync again. So if the stsadm command doesn’t get it in sync, add the user to one of your site collection groups and it will sync afterwards.

The SharePoint PeoplePicker isn’t showing users from a trusted domain

After installing SharePoint, and importing all the User Profiles, you’ll find if you are using the People Picker, you’ll only see users from the trusted domain that have successfully logged on the SharePoint 2007 server, rather than all of them. This is rather bizarre, as you’ve imported all the profiles, and can see them!

You actually need to configure the PeoplePicker to do a lookup to the Domain Controllers, as its here the People looks, NOT the SharePoint user profile store. It seems unusual, but true! It’s quite a complex task.

Before you do anything else, work out a list of all of the domains the PeoplePicker needs to look at, INCLUDING the domain SharePoint is installed on. If SharePoint is on Domain1 and you want to see all the Domain1 users and all the users from the trusted domain Domain2, you’re going to need to list them both, something most of the guides online don’t make clear. You’ll also need the fully qualified domain names – doing use the older NetBIOS name. If your domain is exampledomain.local, don’t just use “exampledomain” – we’ll need the full thing.

Next, make sure you have a valid Active Directory user account on each of the domains you want to look at. You don’t need to worry about the domain the SharePoint server is on – the accounts SharePoint should be running under will already have access.

Now, we first need to set up an encryption key, so SharePoint can securely store the usernames and passwords for the other domains. Use the following command on every server in the farm – if you don’t, the other SharePoint servers won’t be able to decrypt the stored user names and passwords:

stsadm –o setapppassword –password MyPassword

Replace MyPassword with your chosen encryption key, of course!

Next, we need to tell each Web Front End server, which domains to use. I always list the current domain SharePoint is a member of first, for ease of reference. Normally, I’d expect at least two entries – the current domain and the trusted domain (or domains) – if there isn’t a trusted domain, why are you doing this???. We’ll need to separate the entries in the domain list with semi-colons.

stsadm -o setproperty -pn peoplepicker-searchadforests -pv domain:domain1.com;domain:domain2.com,domain2\user,password –url https://sharepoint.domain1.com

Here, the url should be replaced by that of your web application – don’t forget to use https if you’ve set the application up to use SSL. Domain names should obviously be replaced with your own, and you should use the usernames and passwords from each domain that you either created or ensured were available earlier. A more realistic looking example might be:

stsadm -o setproperty -pn peoplepicker-searchadforests -pv domain:technet.microsoft.com;domain:kb.microsoft.com,kb\AD_Lookup,LookUp2009 –url https://sharepoint.technet.microsoft.com

Please note this is an entirely hypothetical example, so don’t think of trying the links or usernames!

Fianlly, though this generally isn’t mentioned in most of the other guides, you need to reset IIS before SharePoint will pick up the changes. As always, I prefer the noforce option, just in case.

issreset -noforce

You should now see all of the available people from the domains you’ve selected in the people picker!