Administering SharePoint 2013 with PowerShell: Site Collections

​ New-SPSite –Url “http://intranet.sharepoint.local/dept/hrweb” –OwnerAlias “domain\JaneHRMangerDoe”

​ New-SPSite –Url “http://hrweb.sharepoint.local” –OwnerAlias “Domain\JaneHRManagerDoe” –HostHeaderWebApplication “http://intranet.sharepoint.local”

​ Get-SPSite “http://hrweb.sharepoint.local”

​ Get-SPSite –webapplication “http://my.sharepoint.local” –Limit All

​ Get-SPContentDatabase “hr_ContentDB” | Get-SPSite

​ Get-SPSite –ContentDatabase “hr_ContentDB”

​ Get-SPSite  –WebApplication “my.sharepoint.local” –Filter {$_.MaintenanceMode –eq $True}

How to Save a SharePoint 2013 Site Collection as a Variable

Assignment collections don’t have to be overly complicated. There’s a simple rule: If you’re saving a SPWeb or SPSite into a variable and taking operations on it, then there is a chance that large amounts of memory will be consumed. Use the assignment collection to identify memory management (think of it like a trash bucket), and then empty the trash bucket often.

​ $memorybucket = Start-SPAssignment

$HRSite = Get-SPSite “http://hrweb.sharepoint.local” –AssignmentCollection $memorybucket

$HRSite | Move-SPSite –DestinationDatabase “hr_contentDB”

Stop-SPAssignment –Identity $memorybucket

Administering Sharepoint 2013 Site Collections with PowerShell

Now that you’ve gotten your site collections saved into a variable or ready to send through the pipeline, here’s what you can do with them.

Note: I find it easier to read and understand PowerShell code that uses a Get-SPSite command to find the site collections, then pipes them into the administrative cmdlet. This is a preference, not a requirement. You can specify the site collection to use in these commands by using the –Identity parameter.

Find Additional URLs for a Host Header Site Collection

If you have a host header site collection, it could have up to five URLs bound to it just like a SharePoint web application can have.

​ Get-SPSite “http://hr.sharepoint.local”| Get-SPSiteUrl

Add Additional URLs to a Host Header Site Collection

If this sounds like a great idea to you, you can also add in an alternate URL for your host header site collection.

​ Get-SPSite “http://hr.sharepoint.local” | New-SPSiteURL –Url “http://hr.local” –Zone “Intranet”

The five zones you can add a URL to are “Default, Internet, Intranet, Extranet, and Custom.”

Setting Settings on an SPSite

Modifying settings on a site collection is done with the Set-SPSite command. There are a lot of settings for a SPSite, and many can be set with this command. I’ll show you the usage and a few of the things you’re sure to find useful.

​ Get-SPSite “http://hr.local” | Set-SPSite –OwnerAlias “domain\NewHRManagerUser”

Changing the Maximum Size of a Site Collection

Use the –MaxSize of the Set-Site command to set the quota manually. You can also use the –WarningSize parameter to set an alarm for you when their approaching capacity. Specify the sizes in MB.

​ Get-SPSite “http://hr.local” | Set-SPSite –MaxSize 25000 –WarningSize 15000

Set a Site Collection to Read Only in SharePoint 2013

Using the –LockState parameter of Set-SPSite you can set a site collection to be read only.

​ GetSPSite “http://hr.local” | Set-SPSite –LockState ReadOnly

Similarly, you can make a site completely inaccessible with –LockState NoAccess, or allow for updates and deletions of existing content but prohibit new content with –LockState NoAdditions. When you’re ready for users to have full access again, use –LockState Unlock to restore full read/write functionality.

Moving a SPSite

There’s two ways to “move” a SPSite. First, you can move the data from one content database to another. This is done with the Move-SPSite command. I describe it in the article on managing content databases and briefly demonstrate it in the How to Save a SharePoint 2013 Site Collection as a Variable section above.

For completeness, here it is again.

​ Get-SPSite “http://hr.sharepoint.local” | Move-SPSite –DestinationDatabase “HR_Content”

However, it’s likely that you’ll actually want to move the location of a SharePoint 2013 site collection from one location to another. For that, you can use the –URL parameter of the Set-SPSite cmdlet.

​ Get-SPSite “http://intranet.sharepoint.local/dept/hr” | Set-SPSite –Url “http://hr.sharepoint.local”

Backing Up a Site Collection

Use the Backup-SPSite cmdlet to backup your site collection.  You need to provide a location to which to save the backup.

​ Get-SPSite “http://hr.sharepoint.local” | Backup-SPSite –Path “D:\Backup\hr\sitebackup.bak”

Note: If you’re using SQL Server Enterprise Edition you can use the –UseSQLSnapshot parameter to keep the site Read-Write during the backup process. Without that parameter, sites will be in read-only mode while they are backed up.

Restoring a Site Collection

You can restore a site collection to either the same URL or a different URL.  You need to specify the path of the site collection backup, and where to restore the site collection to.  You will use some of the same parameters you use to create new site collections, including specifying an existing content database to use or creating a new one.

​ Restore-SPSite –Path “D:\Backup\hr\sitebackup.bak” –Url “http://hr.sharepoint.local” –ContentDatabase “HR_Content”

Removing a site collection

To remove a site collection, use the Remove-SPSite command.

​ Get-SPSite “http://intranet.sharepoint.local/hr” | Remove-SPSite

What Else Can You Do? Well… Everything!

Obviously, each of these commands could get a lot deeper coverage, but this should get you up and running with an awesome overview of what you can do with PowerShell when it comes time to administer your sites. As you get familiar with the techniques, you’ll quickly see that there’s really no comparison between the GUI and PowerShell when you have to manage site collections at a larger scale.

Routine management can sometimes be done more quickly using the GUI, especially if you’re not familiar with PowerShell and you only have to work on a small number of site collections. But when you have to find maybe hundreds of site collections and modify them all, you just can’t beat scripting with PowerShell for its effectiveness and efficiency.

Did I miss something?  Did I get something wrong (or right)? Tell me about it in the comments below, or come find me on Twitter, Facebook, or my personal blog.