SharePoint Secrets

Like SharePoint 2007, you can create host-header based site collections in SharePoint 2010 as well. It means, that you do not necessarily need to create a site-collection under a managed path like /sites/, you can create multiple root-level site collections on same web-application/port by using host-header site collections. All you need to do is point your domain or sub-domain to your web-application and create a matching site-collection that you want. But, like in 2007, it is something that you do by using STSADM, and is not available on Central Admin UI in 2010 as well. Yeah, though you can now also use PowerShell to create one: C:\PS>$w = Get-SPWebApplication http://sitename C:\PS>New-SPSite http://www.contoso.com -OwnerAlias "DOMAIN\username" -HostHeaderWebApplication $w -Title "Contoso" -Template "STS#0" This example creates a host header site collection. Because the template is provided, the root Web of this site collection will be created.

If you haven’t heard, SharePoint 2010 allows you to use FileStream from SQL Server 2008/2008 R2 and the Remote Blob Storage provider so that that you can now use cheap storage to store documents outside of SQL Server! These articles were especially helpful in getting this working: http://blogs.msdn.com/opal/archive/2010/03/24/faq-sharepoint-2010-remote-blob-storage-rbs.aspx http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=174 SQL Server saves all of the blobs in an NTFS directory of your choosing: For fault tolerance you would want this to be a shared drive on a SAN that is shared between the nodes in the Windows cluster. Here are some additional points to keep in mind: 1) These files are not encrypted by default. If you take a file and change the file extension to the appropriate type (PDF, DOCX, etc.), an administrator will be able to view it. 2) If you delete a BLOB in the file system, SharePoint will return a 404 error when you attempt to open the file, but the icon will sti

Content deployment allows you to copy content from a source farm or site collection to a destination farm or site collection. Most content deployment topologies include two or more server farms, to separate the authoring environment from the production environment. Copying files from one site collection to other can be done using Content deployment feature of SharePoint 2010. You can do this either manually or on a predetermined schedule. Some Important things to Note : 1. Content deployment is a one-way process – Content is copied from a source site collection to a destination site collection.The content deployment feature does not support round-trip synchronization from source to destination and back again. 2. Creating new content or changing existing content on the destination site collection can cause content deployment jobs to fail. 3. You cannot deploy(copy) a site to the same content database as the source site – This is because all the GUIDs that are used to define sites, Web p

When you compile a SharePoint solution, it deploys to the SharePoint server and a debugger attaches to debug it. The process used to debug the solution depends on the setting of the Sandboxed Solution property: sandboxed solution or farm solution. For more information, see Sandboxed Solution Considerations . Farm Solutions Farm solutions, which are hosted in the IIS worker process (W3WP.exe), run code that can affect the whole farm. When you debug a SharePoint project whose Sandboxed Solution property is set to "farm solution," the system's IIS application pool recycles before SharePoint retracts or deploys the feature so as to release any files locked by the IIS worker process. Only the IIS application pool serving the SharePoint project's site URL is recycled. In this solution all SharePoint project item types in are available, but deployment needs administrative privileges and the solution must run in FULL TRUST permission LEVEL. Sandboxed Solutions Sandboxed solut

In Internet facing websites, you don’t want anonymous users to access pages such as AllItems.aspx etc. There is a Sharepoint feature ViewFormPagesLockDown which can be enabled to secure your sites. Find out more details about this feature at: http://technet2.microsoft.com/Office/en-us/library/f507f5d6-4c9d-4f98-909f-069c53b9a3f61033.mspx#section6 Activate Feature: stsadm -o activatefeature -url -filename ViewFormPagesLockDown\feature.xml De-Activate Feature: stsadm -o deactivatefeature -url -filename ViewFormPagesLockDown\feature.xml For disabling anonymous access to the Allitems.aspx and EditForm.aspx pages, activate the ViewFormPagesLockDown feature.

Crawl components process crawls of content sources, propagate the resulting index files to query components, and add information about the location and crawl schedule of content sources to their associated crawl databases. Crawl components are associated with a single Search service application. You can distribute the crawl load by adding crawl components to different farm servers. You assign a farm server to participate in crawling by creating a crawl component on that server. If you want to balance the load of servicing crawls across multiple farm servers, add crawl components to the farm and associate them with the servers that you want to crawl content. To add a crawl component to a Search service application Verify that the user account that is performing this procedure is a member of the Farm Administrators group. In Central Administration, in the Application Management section, click Manage service applications . On the Service Applications page, click the name of the Search se

In SharePoint 2010 you can manage site collections through Windows PowerShell. You can create new site collections using the New-SPSite cmdlet: New-SPSite http: // SP –OwnerAlias “ds\admmoss” ` -Template “STS #0” You can retrieve an existing site using the Get-SPSite cmdlet: Get-SPSite http: // SP You can configure a site collection through the Set-SPWeb cmdlet: Get-SPSite http: // SP | Set-SPSite -SecondaryOwnerAlias “ds\kumar” And finally, you can remove a site collection using the Remove-SPSite cmdlet: Remove-SPWeb http: // SP -Confirm : $false Setting the –Confirm switch parameter to $false omits the confirmation returned from PowerShell. If you want to see what happens if you remove a site collection but don’t want to actually remove the site collection you can use the –WhatIf switch parameter. Remove-SPWeb http: // SP –WhatIf The Cmdlet New-SPSite [-Url] -OwnerAlias [-AdministrationSiteType ] [-AssignmentCollection ] [-Confirm [ ]] [-ContentDatabase ] [-Description ][-