SharePoint Secrets

1. Alter your master page to allow HTML5 Edit the masterpage of your site in Sharepoint Designer. Locate the following tag: DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd" > Simply remove everything behind “html” except the closing tag: DOCTYPE html > 2. Remove forced IE 8 rendering Your masterpage has a tag that pretty much says “Force this page to be rendered as an IE 8 browser would”. But IE 8 doesn’t support HTML 5 so get rid of it – delete the following line from your masterpage: < meta http-equiv ="X-UA-Compatible" content ="IE=8" /> 3. Back in your Sharepoint site, add a new Content Editor webpart on the page where you want the magic of HTML 5 to be displayed. Open the HTML editor for the contents (you’ll find it up at the ribbon, looks a little something like this: 4. Put your HTML 5 code into the HTML Source window that appears, click OK.

Error: The management agent failed on run profile "DS_FULLIMPORT" because of connectivity issues. Reason: You will get this error during the profile import from "User Profile Service" of SharePoint 2010. The reason is the domain name may be mismatched with the actual domain name. Because, you will use the domain name like "sensoft" (just an example). But the actual domain may be different in Profile AD. for example, the actual domain name will be "sensoft.local" for "sensoft". So, you have to change the actual domain name in the " Synchronization Service Manager ". Solution: To resolve this error, just follow the below steps: 1. Login into the SharePoint 2010 server. 2. Open the Synchronization Service Manager from C:\Program Files\Microsoft Office Servers\14.0\Synchronization Service\UIShell\miisclient.exe 3. Go to "Management Agents" tab & select the "Active Directory Domain Services" type 4. Doubl...

The “User” in the User Profile Service In a typical business system, a user is determined by the identity presented to the system. Once this identity is confirmed, business system follows a certain set of rules and policies to give appropriate access. But there is rich information about this user’s activity in the system that the corporation overall can benefit from and the user can benefit from. In the User Profile Service, we think of the user at the center of it all as a “person” in the profile store who has a face -through the Profile, My Site, News feed; has a web service that can be crawled - for example for Social search; a store backing the person up and; relationships and a networks in the enterprise. Need for the User Profile Synchronization Service With that mindset, that is “person” at the center, as the cornerstone of the User Profile Service architecture, the question becomes, how does one get started in accumulating interesting information about a user in the user profil...

Planning and implementing Exclusion Filters for SharePoint Server 2010 User Profile Synchronization (UPS) is without doubt one of the most important aspects of any UPS deployment. By making use of Exclusion Filters we can narrow down the objects we sync with. Exclusion Filters reduce the amount of “junk” in the Profile database and can significantly decrease the time taken to perform synchronization runs. I will be posting more about Exclusion Filters in general soon, but for this post I will concentrate on the most commonly used filter – that of the userAccountControl attribute in Active Directory. This is by far the one I am asked about most, and is commonly misunderstood. The userAccountControl attribute is used to store the account options for an AD user object. These options include the status of the account (e.g. disabled, or locked out). Each option is a property flag. These flags are cumulative and thus there is only ever one value for userAccountControl. Therefore it makes sen...

After upgrading our SharePoint 2007 server to 2010 I got this error when doing any people search: No refinements available. Property doesn’t exist or is used in a manner inconsistent with schema settings Small fix: Edit the People Core Result Web Part on the search result page and expand the “Display properties” and make sure “Use Location Virtualization” is checked.

Good article published in Chaks' Croner MOSS 2007 Say for example you have a Site Collection Web Application1 and you have created a series of content types to use. Now, you create Web Application 2 and find the necessity to reuse the content types created in Web Application 1 . There is no way you could share or reference those content types created in Web Application 1 in Web Application 2 . The only way possible is to create or write an application which would install those content types. This situation is pretty common in large organizations. This can be even considered for exposing base content types you use across multiple web applications in the farm. Below is the diagram representing the above chaos: SharePoint 2010 SharePoint 2010 now introduces a new feature called Content Type Hubs .Content Type Hub is a central location where you can manage and publish your content types – so now web applications can subscribe to this hub and pull down the published content types fr...

When you provision a web app in SP2010, you can choose it to use Claims Based Auth or Classic Auth right through the GUI. However, after you have provisioned a web app, there is no GUI to switch from Classic to Claims based. So the below powershell script will let you convert a SP2010 website to claims based auth after it has been provisioned. 1: $w = Get-SPWebApplication "http://sitename" 2: $w.UseClaimsAuthentication = "True" ; 3: $w.Update() The user running the above script should be a member of the SharePoint_Shell_Access role on the config DB, and a member of the WSS_ADMIN_WPG local group.