Create and manage SharePoint site collection quotas using PowerShell

Whilst you can enforce disk quotas on any site collection in SharePoint, I have seen them used most commonly to cap the amount of disk space used in My Sites. Providing a default site quota template from which all My Sites inherit during creation is easy enough, but it can be a pain for administrators to change the template on existing My Sites as the interface used to modify quota templates on site collections is fine for the odd one or two, but there are no options in the SharePoint UI to bulk modify the quota template used on multiple sites. In this article I will explain how to use PowerShell with SharePoint 2010 to create a new quota template, apply it to a single site collection, and then multiple site collections in one hit.

First, run this script below to set up a function for creating new quota templates:

function CreateQuotaTemplate ($Name, $MaxLevelMB, $WarnLevelMB)
{
    $quotaTemplate = New-Object Microsoft.SharePoint.Administration.SPQuotaTemplate
    $quotaTemplate.Name = $Name
    $quotaTemplate.StorageMaximumLevel = ($MaxLevelMB*1024)*1024
    $quotaTemplate.StorageWarningLevel = ($WarnLevelMB*1024)*1024
    $contentService = [Microsoft.SharePoint.Administration.SPWebService]::ContentService
    $contentService.QuotaTemplates.Add($quotaTemplate)
    $contentService.Update()
}

Once you have run the script, type the following command to create a new quota template in your SharePoint farm:

CreateQuotaTemplate –Name “Template Name” –MaxLevelMB MaximumLevelInMB –WarnLevelMB WarningLevelInMB

For example, if we wanted to create a new quota template called “Media Users” with a maximum quota size of 500 MB and warning level of 400 MB, then we can type this command:

CreateQuotaTemplate –Name “Media Users” –MaxLevelMB 500 –WarnLevelMB 400

Now run this script to set up a function for assigning a quota template to a single site collection:

function AssignQuotaTemplate ($Name, $Url)
{
    $contentService = [Microsoft.SharePoint.Administration.SPWebService]::ContentService
    $quotaTemplate = $contentService.QuotaTemplates[$Name]
    Set-SPSite -Identity $Url -QuotaTemplate $quotaTemplate
}

Once this script has been run, you can now use the following command to assign our “Media Users” quota template to a single site collection:

AssignQuotaTemplate –Name “Media Users” –Url http://mysite/personal/phil.childs

Finally, run this script to set up a function for replacing a quota template across all site collections in a web application:

function BulkReplaceQuotaTemplates ($WebApp, $OldTemplate, $NewTemplate)
{
    $contentService = [Microsoft.SharePoint.Administration.SPWebService]::ContentService
    $oldQuotaTemplate = $contentService.QuotaTemplates[$OldTemplate]
    $newQuotaTemplate = $contentService.QuotaTemplates[$NewTemplate]
    $webApplication = Get-SPWebApplication $WebApp
    $webApplication | Get-SPSite -limit all | ForEach-Object {
        if ($_.Quota.QuotaID -eq $oldQuotaTemplate.QuotaID) {   
            Set-SPSite -Identity $_.Url -QuotaTemplate $newQuotaTemplate
        }
    }
}

This function allows you to specify the web application, old quota template you want to replace, and the new quota template you want to replace it with. For example, lets assume that all My Sites in your SharePoint implementation have been created with the default “Personal Site” quota template. We could run a script to simply bulk change all of these site collections to a new quota template, but there may be the odd one or two that have been configured with individual quotas. Therefore, the command below will walk through each site collection in the web application and change the quota template to “Media Users”, but only on site collections that are currently configured with the “Personal Site” quota template – leaving alone any site collections that have been configured with individual quota templates:

BulkReplaceQuotaTemplates -WebApp http://mysite -OldTemplate "Personal Site" -NewTemplate "Media Users”