Tuesday, 9 December 2014

How to Create Mysite in SharePoint 2010

How to Invite External Users to Your SharePoint Site

PowerShell Script to Limit SharePoint Site Templates Available

Restricting Usage of Site Templates in SharePoint


SharePoint Site Collections enable restriction of site templates and page layouts via a simple modification on site settings in the browser. Go to the site settings of a single site or the site collection main site (Site Actions > Site Settings > Modify All Site Settings) and choose Look and Feel -ryhmästä Page layouts and site templates.

This setting can be modied in Publishing Sites or wss-sites with publishing features activated (these features can be activated in site settings:: Site Actions > Site Settings > Site Features, Office SharePoint Server Publishing > Activate, note that this setting is not inherited by subsites).

On the Page layouts and site templates page the usage of site templates and page layouts can be set in three different ways:



https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjIIp4l9tjp9f0ZEkiDC9ewn1ojqFjMMVSGJUNZbwN2T4WuQ4aTibZ20q8oFi2sesizucPsKNQ7xzD4ZlzOPVXoG2ohtvjNdZ3AgBhngMjYl0CsBkjXOjI5shsIm7S8ndoHEh6H-GI5GiI/s1600/sitetemp1.png

  1. Set subsites to inherit templates or layouts from parent site (the site where the setting is modified)
  2. Give the subsites permission to use any templates or layouts
  3. Give the subsites permission to use only specifically determined templates or layouts
Subsites can be reset to inherit these settings by selecting Reset all subsites to inherit… The setting is inherited by existing publishing and wss sites and new publishing sites, but not new wss sites.
If this seems insufficient, one can always take up more severe measures in restricting usage of Site templates and page layouts.
Page layouts aren't a problem, really, since by spcifying the permitted page layouts in the settings of the site collection and inheriting the settings to subsites, the setting really goes all the way through the site collection. And if you want to, you can always manage them further in the Master Page and page layout gallery (in site collection settings Site Actions > Site Settings ja Galleries > Master pages and page layouts) and delete (or move to another location) the page layouts that are not to be used at all:

Site templates, on the other hand, require the tampering of a set of XML files - those of customized Site Definitions (if there are such) and those managing the templates of the whole Web Application.
On the SharePoint server, the \Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\1033\XML directory contains these XML files to modify. Of these, the WEBTEMP.XML file is the one containing settings for site templates, except for the Publishing and Enterpise tabs. Templates can be hidden from view & thus from usage by setting the value of the attribute Hidden to be "TRUE" on those templates you wish to hide.

This is actually the only supported action in these XML files - and even this is an exception (More about Microsoft Supported ja unsupported scenarios on the Microsoft site: http://support.microsoft.com/default.aspx/kb/898631 ).
Hiding templates on the Publishing tab is done similiarly in the webtempsps.xml file. The Enterprise tab is a tad more complex thing to modify, as each template has its own XML file, but they are all situated in the same XML directory with these already mentioned files.
Own tabs can be created - or the existing ones "renaimed" (but as a reminder, this is not officially supported) by setting the value of the DisplayCategory attribute: DisplayCategory="Own tab name" in the XML files.

After this, one question remains: how to make the site templates saved in the browser (in the site settings of a wss site Look and Feel > Save site as template) to appear on a tab not named Custom?
The name of the Custom tab can be changed by modifying the value of TemplatePickerControl_Custom in the \Program Files\Common Files\Microsoft Shared\web server extensions\12\Resources\core.[en-US].resx file:

Remember to make backups before tampering with the original files! And after modifying the files, be sure to perform iisreset in order to apply the changes.





Reference:

http://borderingdotnet.blogspot.in/2008/09/restricting-usage-of-site-templates-in.html

SharePoint 2010 Delegated Administration

Have been wanting to try this for a while now and just now got some time to do it today.  The Central Administration site is just a SharePoint site with libraries and links, so I was curious what would happen if you were added to the site as a simple reader.  Here's the results:
As a reader and contributor, you do not gain access to Central administration and you will get the access denied error message.  The real magic comes in being in a specifically names group, there are two groups in the SCA:
  • Farm Administrators
  • Delegated Administrators
Full Control, Contributor and Read permission levels have no role to play in the links on the SCA.  What does matter is what group you reside in.  Being a Farm Administrator allows you to do anything in the SCA.  Being a Delegated lets you do a subset of actions, one of the items you cannot do is to create new Web Applications, but when it comes to the majority of other things, you can do them!  The thing that I would be more insterested in how one would target the links in Quick Launch to specific people.  IE, something like the following:
  • Web Application manager
  • Service Account Manager
  • Service Application Manager (like a global service app manager role rather than manually apply to each one)
  • Backup Restore Manager
  • Content Deployment Manager
Service applications have a completed different architecture to them.  Each service application can have an "Administrator" assigned to it.  I found a great article that describes this process here:
http://www.sharepointanalysthq.com/2010/10/creating-a-delegated-administrator-for-a-service-application/
However, this also doesn't have much in terms of granular controls.  Its all or nothing for most of them.  These need more granular controls setup for them.  Security seems to be an afterthought in SharePoint, has been, probably always will be.

Reference:

http://blogs.architectingconnectedsystems.com/blogs/cjg/archive/2010/12/06/SharePoint-2010-Delegated-Administration.aspx

Creating a delegated administrator for a service application

One awesome thing about Service Apps in SharePoint 2010 is not only that you can have more than one of them for a particular service (for example HR and Marketing having their own Managed Metadata Service) but you can give users permissions to manage these Service Applications in Central Administration without giving them access to the whole kit and kaboodle.
This is the concept of a ‘Delegated Administrator’. A user who we want to manage a particular service application but we don’t want them to be able to see anything else. Obviously this is really useful to the SharePoint administrator because it means less work for us Smile
So lets assume that we have a Managed Metadata Service Application that we want our non admin user, John Smith, to be able to manage. This way we can let John be an administrator just for the Managed Metadata Service without needing to expose all the other functionality.
So firstly we need to get to the Manage Service Applications screen by click on the ‘Manage Service Applications’ link from the home page of Central Admin

image

Then click to the right of whichever Service Application you want to create an Administrator for and select the Administrator button ( Don’t actually click on the text, but just highlight the row):

http://www.sharepointanalysthq.com/wp-content/uploads/2010/09/image2.png


Add in our username, give them full permissions and click ok.

http://www.sharepointanalysthq.com/wp-content/uploads/2010/09/image9.png



 Now if we log in as John we can see that we are within Central Administration but a whole lot is missing, in fact the only thing that we can see is the Service Application that we have access to.


 http://www.sharepointanalysthq.com/wp-content/uploads/2010/09/image10.png


 One more thing to remember is that if you remove a user from administering a Service Application they will still have access to Central Administration, all be it with nothing to see. If you want to completly remove all access for a user you will have to remove them from the delegated administrators group as well.


 http://www.sharepointanalysthq.com/wp-content/uploads/2010/09/image11.png


 So there you go a quick and easy way to allow your users to manage the Service Application that they need to without necessarily giving them access to the rest of Central Administration.




Reference:

http://www.sharepointanalysthq.com/2010/10/creating-a-delegated-administrator-for-a-service-application/

Using Quota Template to manage site collection storage limits (Power Shell, SharePoint 2010)


In this article I am showing you how to set limit for SharePoint 2010 site collection using Quota Template. Here I am using Power Shell to define Quota Template.

A quota Templates defines the storage limit for the maximum amount of data that can be stored in a site collection.

When the site collection reaches the Quota template defined by Administrato, it triggers an e-mail alert to the site collection administrator. Quotas can be saved as quota templates so that we can apply them to any site collection in a SharePoint farm.

Create Quota Template

1. On the Start menu, click All Programs.

2. Click Microsoft SharePoint 2010 Products.

3. Click SharePoint 2010 Management Shell.

4. At the Windows Power Shell command prompt type the following command:

pic1.gif

5. You will get a Power shell command prompt like below

pic2.gif

The Syntax to create Quota Template is as shown

$Customquota = New-Object Microsoft.SharePoint.Administration.SPQuotaTemplate
$Customquota.Name = "ProjectQuota"
$Customquota.StorageMaximumLevel = 1048576
$Customquota.StorageWarningLevel = 524288
$Service = [Microsoft.SharePoint.Administration.SPWebService]::ContentService
$Service.QuotaTemplates.Add($Customquota)
$Service.Update()

  • Name - You have to give the Quota Template name as string value.
  • StorageMaximumLevel –Is the maximum size for your site collection(In Bytes).
  • StorageWarningLevel-Will give email message if the Quota template reaches the value specified in this column(In Bytes)
Please find the command in action
pic3.gif

To change the quota template for a site collection by using Windows Power Shell.

The Syntax Change the Quota Template for a site collection.

Set-SPSite -Identity "Site URL" -QuotaTemplate "Template Name"

  • Site URL- is the URL of the site collection whose quota template you want to change.
  • Template Name -is the name or GUID of the replacement template. 

Reference:

http://www.c-sharpcorner.com/uploadfile/Roji.Joy/using-quota-template-to-manage-site-collection-storage-limits-power-shell-sharepoint-2010/