1-Use Custom Columns to Improve Search Results
Categorizing content helps users effectively find documents within the site. This can be done via SharePoint through the use of custom columns or meta data. Create these columns at the global level of the site collection and add them to the required content types. The document libraries or lists associated with these content types will then inherit these custom columns.
These custom columns can also be set as required fields. For example, you may include a column identifying the Sales Territory a document is related to, making it easier for the Sales staff to filter their search results quickly by their relevant territory. This also improves the ranking of the search results.
2-Managing a site in SharePoint 2010 Using PowerShell cmdlets
In SharePoint 2010 you can manage sites through Windows PowerShell. You can create new sites in a site collection using the New-SPWeb cmdlet:
New-SPWeb http://SP/TeamSite -Template "STS#0" –Name "Team Site" `
-Description "Description of Site" –AddToTopNav –UseParentTopNav
You can retrieve an existing site using the Get-SPWeb cmdlet:
Get-SPWeb http://SP/TeamSite
You can configure a site through the Set-SPWeb cmdlet:
Get-SPWeb http://SP/TeamSite | Set-SPWeb -Description "New Description"
And finally, you can remove a site using the Remove-SPWeb cmdlet:
Remove-SPWeb http://SP/TeamSite -Confirm:$false
Setting the –Confirm switch parameter to $false omits the confirmation returned from PowerShell.
3-Use BLOB Caching to increase performance
BLOB caching, or disk-based caching, is an out of the box (OOTB) caching mechanism that is built into the MOSS 2007 and SharePoint Server 2010 platforms. It is commonly used to speed-up access to large and relatively static resources that are stored in content databases, such as images, videos, javascript files, and more. Performance improvements are gained by storing these assets on web front-ends (WFEs) once they’ve been requested by a client. This allows SharePoint to serve subsequent requests for such assets directly from WFEs instead of round-tripping to the content database each time a request for such an asset is received. For most SharePoint sites, this type of caching can significantly lighten the load on your SQL Servers and back-end network.
BLOB Caching is controlled through the web.config file for each of the IIS web sites that is associated with a Web application, and it is not enabled by default. Enabling BLOB caching is as simple as setting the enabled attribute to true in the web.config element as shown below.
4-Backup and restore watch-outs for SQL Server encryption
Starting with SQL Server 2008 Enterprise and Developer editions, databases can be encrypted on disk using transparent data encryption, or TDE. SharePoint has no qualms with TDE, and SharePoint’s databases can be encrypted without issue using TDE.
When backing up and restoring databases that are encrypted, though, be careful. Encryption is handled by SQL Server, and such encryption “flies below the radar” of SharePoint. For backup strategies that target SQL Server databases, be sure your plan includes protection for TDE certificates and keys that are in-use by SQL Server. Failure to include these items leaves you at risk for restoring databases with inaccessible encrypted content.
5-Use a Thesaurus File to create synonyms or replacements in Search Queries
Thesaurus Files are a way for administrators to improve search results by creating synonyms or replacement words used in their queries. For example, you can create a synonym for the word SharePoint so when a user is making a search for the word WSS, you would also get results with the word SharePoint.
The Thesaurus Files are located on the SharePoint server in the folder: %ProgramFiles%\Microsoft Office Servers\14.0\Data\Applications\[GUID]\Config where the [GUID] is the GUID of your Search Service Application.
6-Hide a list in SharePoint '10
You can use Windows PowerShell to hide a list in SharePoint 2010. Simply store an instance of an SPList Object, set the Hidden property to $true and update the SPList object.
PS > $spWeb = Get-SPWeb http://sp01/site
PS > $spList = $spWeb.GetList("http://sp01/site/Lists/MyList")
PS > $spList.Hidden = $true
PS > $spList.Update()
7-Understand database mirroring requirements for disaster recovery purpose
SharePoint 2010 is mirroring aware and utilizes the FailoverPartner keyword in its database connection strings to identify a SQL Server instance that is used for mirroring purposes. Upon learning this, it might be tempting to jump right in and start mirroring SharePoint databases for redundancy. Before doing so, though, you should be aware that the following requirements apply:
Less than 1ms latency between principal and mirror SQL Server instances
1GB/s bandwidth or greater between principal and mirror SQL Server instances
Principal and mirror instances must be running the same version and edition of SQL Server
Mirrored databases must use the Full recovery model
High safety with automatic failover (that is, synchronous mirroring with witness server) is recommended
Mirroring is certainly useful, but as the aforementioned list demonstrates: it shouldn’t be implemented without careful planning and infrastructure design.
8-find information about your SharePoint database
You can use the Get-SPDatabase cmdlet to display information about the SharePoint databases.
PS > Get-SPDatabase
The example above displays all SharePoint databases. If you want to display a specific Database, use the identity parameter followed by the database ID.
PS > Get-SPDatabase -Identity f9213ca2-3604-42e5-b6cf-92740fbed83a
9-Find information about Farm configurations
You can use the Get-SPFarmConfig cmdlet to retrieve global settings for the local farm. The cmdlet returns information for items that are not on the SPFarm Object.
PS > Get-SPFarmConfig
WorkflowBatchSize : 100
WorkflowPostponeThreshold : 15
WorkflowEventDeliveryTimeout : 5
DataFormWebPartAutoRefreshEnabled : True
ASPScriptOptimizationEnabled : True
10-Set Web Applications outgoing email address
 |
You can use PowerShell to set a Web Applications outgoing email address and SMTP Server. Simply use the Set-SPWebApplication cmdlet.
PS > Set-SPWebApplication -Identity http://SP01 `
>> -OutgoingEmailAddress mail@domain.com `
>> -SMTPServer ex01.domain.com |
