{"id":17051,"date":"2010-09-21T00:01:00","date_gmt":"2010-09-21T00:01:00","guid":{"rendered":"https:\/\/blogs.technet.microsoft.com\/heyscriptingguy\/2010\/09\/21\/use-sharepoint-2010-powershell-cmdlets-to-get-and-manage-sites\/"},"modified":"2010-09-21T00:01:00","modified_gmt":"2010-09-21T00:01:00","slug":"use-sharepoint-2010-powershell-cmdlets-to-get-and-manage-sites","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/scripting\/use-sharepoint-2010-powershell-cmdlets-to-get-and-manage-sites\/","title":{"rendered":"Use SharePoint 2010 PowerShell Cmdlets to Get and Manage Sites"},"content":{"rendered":"

 <\/p>\n

Summary<\/strong>: The Microsoft Scripting Guys host guest blogger Niklas Goude as he discusses site management using Windows PowerShell cmdlets.<\/p>\n

 <\/p>\n

\"Hey, Hey, Scripting Guy! How do I manage sites in SharePoint 2010 by using Windows PowerShell cmdlets?<\/p>\n

— KM<\/p>\n

 <\/p>\n

\"Hey, Hello KM, <\/p>\n

Microsoft Scripting Guy Ed Wilson here, once again I will defer the question to our guest blogger for the week, Niklas Goude. <\/p>\n

Niklas Goude is a Windows PowerShell MVP working at Enfo Zipper in Stockholm, Sweden. Niklas has extensive experience in automating and implementing SharePoint environments using Windows PowerShell. He has written a Windows PowerShell book for Swedish IT pros, powershell.se<\/a>, and is currently co-authoring a book with Mattias Karlsson titled, PowerShell for Microsoft SharePoint 2010 Administrators<\/a><\/i>, which will be published in English by McGraw-Hill in October 2010. Parts of this post are taken from Chapter 4 of that book.<\/p>\n

Niklas also runs the blog, powershell.nu<\/a>, where he shares scripts, examples, and solutions for administrative tasks in Windows environments through Windows PowerShell.<\/p>\n

 <\/p>\n

Getting Sites in SharePoint 2010<\/h5>\n

Let’s see how we can manage Sites in a SharePoint 2010 environment. As discussed in yesterday’s post<\/a>, SharePoint 2010 includes more than 500 cmdlets. Some of these are designed to manage site collections and sites. A site in SharePoint 2010 is hosted within a site collection and contains one or more web pages, lists, or libraries to store and present information. The first cmdlet we’ll look at is Get-SPWeb<\/strong>, which is used to retrieve one or more sites. Here’s an example of using the cmdlet:<\/p>\n

\n
PS<\/span> <\/span>><\/span> <\/span>Get-SPWeb<\/span> <\/span>-Identity<\/span> <\/span>http:\/\/SPServer<\/span> <\/p>\n

<\/span>Url<\/span> <\/p>\n

<\/span>—<\/span> <\/p>\n

<\/span>http:\/\/spserver<\/span> <\/div>\n<\/blockquote>\n

The Get-SPWeb<\/strong> cmdlet displays the Url<\/strong> property by default. We can display all properties using the Format-List<\/strong> cmdlet as demonstrated in the following image.<\/p>\n

\"Image<\/a><\/p>\n

The example above displays a lot of cool properties such as Title<\/strong>, Description<\/strong>, Language<\/strong>, when the site was created, and when the last item was modified. <\/p>\n

Modifying Sites in SharePoint 2010<\/strong><\/p>\n

If we want to modify specific properties, we can use the Set-SPWeb<\/strong> cmdlet. Here’s how to change the description of a site:<\/p>\n

\n
PS<\/span> <\/span>><\/span> <\/span>Get-SPWeb<\/span> <\/span>-Identity<\/span> <\/span>http:\/\/SPServer<\/span> <\/span>|<\/span> <\/span>Set-SPWeb<\/span> <\/span>-Description<\/span> “PowerShell is Cool”<\/span> <\/div>\n<\/blockquote>\n

You can use the Set-SPWeb<\/strong> cmdlet to set some of the properties. At some point you’ll want to change additional properties that are not supported by the Set-SPWeb<\/strong> cmdlet. You can do this by storing a site in a variable and then set the properties:<\/p>\n

\n
PS<\/span> <\/span>><\/span> <\/span>$spWeb<\/span> <\/span>=<\/span> <\/span>Get-SPWeb<\/span> <\/span>-Identity<\/span> <\/span>http:\/\/SPServer<\/span> <\/p>\n

<\/span>PS<\/span> <\/span>><\/span> <\/span>$spWeb<\/span>.Title<\/span> <\/span>=<\/span> “PowerShell” <\/p>\n

<\/span>PS<\/span> <\/span>><\/span> <\/span>$spWeb<\/span>.TreeViewEnabled<\/span> <\/span>=<\/span> “True” <\/p>\n

<\/span>PS<\/span> <\/span>><\/span> <\/span>$spWeb<\/span>.Update()<\/span> <\/div>\n<\/blockquote>\n

In the example above, we change the sites title and enable the TreeView<\/strong>. Finally, we use the Update()<\/strong> method to commit the changes. Just as with objects of the type SPSite<\/strong>, SPWeb<\/strong> objects need to be disposed of correctly when stored in variables using either the Dispose()<\/strong> method or the Start-SPAssignment<\/strong> and Stop-SPAssignment<\/strong> cmdlets. The example below demonstrates how to use the Dispose()<\/strong> method:<\/p>\n

\n
PS<\/span> <\/span>><\/span> <\/span>$spWeb<\/span>.Dispose()<\/span> <\/div>\n<\/blockquote>\n

Windows PowerShell makes it real simple to update multiple sites in a site collection through a couple of lines of code. Here’s how to enable the TreeView<\/strong> on all sites in a site collection:<\/p>\n

\n
PS<\/span> <\/span>><\/span> <\/span>Get-SPSite<\/span> <\/span>-Identity<\/span> <\/span>http:\/\/SPServer<\/span> <\/span>|<\/span> <\/span>Get-SPWeb<\/span> <\/span>|<\/span> <\/span>ForEach-Object<\/span> <\/span>{<\/span> <\/p>\n

<\/span>>><\/span> <\/span>$_<\/span>.TreeViewEnabled<\/span> <\/span>=<\/span> <\/span>“True”<\/span> <\/p>\n

<\/span>>><\/span> <\/span>$_<\/span>.Update()<\/span> <\/p>\n

<\/span>>><\/span> <\/span>}<\/span> <\/div>\n<\/blockquote>\n

In the example above we use the ForEach-Object<\/strong> cmdlet to iterate through each site in the site collection and enable the TreeView<\/strong> and finally call the Update()<\/strong> method to commit the changes. <\/p>\n

Creating Sites in SharePoint 2010<\/h5>\n

Creating a new site is a simple procedure when using Windows PowerShell. Simply use the New-SPWeb<\/strong> cmdlet as demonstrated below.<\/p>\n

\n
PS<\/span> <\/span>><\/span> <\/span>New-SPWeb<\/span> <\/span>-Url<\/span> <\/span>http:\/\/SPServer\/NewWeb<\/span> <\/span>-Template<\/span> “STS#0” <\/span>-Name<\/span> “New Site” <\/span>`<\/span>
<\/span>>><\/span> <\/span>-Description<\/span> “My New Site” <\/p>\n

<\/span>Url<\/span> <\/p>\n

<\/span>—<\/span> <\/p>\n

<\/span>http:\/\/spserver\/NewWeb<\/span> <\/div>\n<\/blockquote>\n

In the example above we set the site’s new URL and set the Template to “STS#0”<\/strong>, which corresponds to a team site. We also set the Sites Name<\/strong> and Description<\/strong>. <\/p>\n

<\/h5>\n
Backup & Restore Sites in SharePoint 2010<\/h5>\n

Let’s take a closer look at backup and sestore. When working with sites, we can use the Export-SPWeb<\/strong> cmdlet to export a site:<\/p>\n

\n
PS<\/span> <\/span>><\/span> <\/span>Export-SPWeb<\/span> <\/span>-Identity<\/span> <\/span>http:\/\/SPServer\/NewSite<\/span> <\/span>`<\/span> <\/p>\n

<\/span>>><\/span> <\/span>-Path<\/span> <\/span>C:\\Backup\\spWebBackup.bak<\/span> <\/div>\n<\/blockquote>\n

This example exports an entire site to a backup file. It is also possible to export specific content from a subsite, such as lists, document libraries, and list items. You use the ItemUrl<\/strong> parameter to export lists or list items from a subsite. Here is an example of exporting a list called Calendar<\/strong> from a site:<\/p>\n

\n
PS<\/span> <\/span>><\/span> <\/span>Export-SPWeb<\/span> <\/span>-Identity<\/span> <\/span>http:\/\/SPServer\/NewSite<\/span> <\/span>`<\/span> <\/p>\n

<\/span>>><\/span> <\/span>-ItemUrl<\/span> “Lists\/Calendar” <\/span>-Path<\/span> <\/span>C:\\Backup\\spWebCalendar.bak<\/span> <\/div>\n<\/blockquote>\n

The Export-SPWeb<\/strong> cmdlet also supports the IncludeUserSecurity<\/strong> switch parameter, which allows you to include access control lists for all items. By default, Export-SPWeb<\/strong> exports the last major version of a list item, but you can change this by setting the IncludeVersions<\/strong> parameter to include the current version, last major and minor version, or all versions of each item.<\/p>\n

After you have an export file, you can use the Import-SPWeb<\/strong> cmdlet to import it into a subsite. Importing a subsite works as long as you specify a site collection that contains a matching template; otherwise, an error occurs:<\/p>\n

\n
PS<\/span> <\/span>><\/span> <\/span>Import-SPWeb<\/span> <\/span>-Identity<\/span> <\/span>http:\/\/SPServer\/NewSite<\/span> <\/span>-Path<\/span> <\/span>C:\\Backup\\spWebCalendar.bak<\/span> <\/div>\n<\/blockquote>\n

The Import-SPWeb<\/strong> cmdlet also supports the UpdateVersions<\/strong> parameter, which allows you to specify how to handle items that already exist in a list. The possible values are Append<\/strong>, Overwrite<\/strong>, and Ignore<\/strong>.<\/p>\n

Remove Sites in SharePoint 2010<\/strong><\/p>\n

Finally, let’s take a look at how to remove an existing site. The Remove-SPWeb<\/strong> cmdlet removes a specific site from SharePoint 2010. If the top-level site is deleted, the site collection is also removed. Here is an example of running this cmdlet:<\/p>\n

\n
PS<\/span> <\/span>><\/span> <\/span>Remove-SPWeb<\/span> <\/span>-Identity<\/span> <\/span>http:\/\/SPServer\/NewSite<\/span> <\/span>-Confirm:<\/span>$false<\/span> <\/div>\n<\/blockquote>\n
Summary<\/h5>\n

In this post we’ve covered sites in SharePoint 2010, with examples showing us how to create, modify, backup and restore, and remove sites in SharePoint 2010. It’s also possible to go one step further and automate the creation of sites using a user-friendly SharePoint list, manage lists and libraries, and even items. We’ll see examples of this in the upcoming post. You should also check out PowerShell for Microsoft SharePoint 2010 Administrators<\/i> for a detailed description of how you can manage your SharePoint 2010 environment using Windows PowerShell. (This book will be available in October 2010.)<\/p>\n

KM, that is all there is to using Windows PowerShell cmdlets to manage sites in SharePoint 2010. Guest Blogger Week with Niklas Goude and SharePoint will continue tomorrow.<\/p>\n

We would love for you to follow us on Twitter<\/a> and Facebook<\/a>. If you have any questions, send e-mail to us at scripter@microsoft.com<\/a>, or post your questions on the Official Scripting Guys Forum<\/a>. See you tomorrow. Until then, peace.<\/p>\n

 <\/p>\n

Ed Wilson and Craig Liebendorfer, Scripting Guys<\/strong><\/p>\n","protected":false},"excerpt":{"rendered":"

  Summary: The Microsoft Scripting Guys host guest blogger Niklas Goude as he discusses site management using Windows PowerShell cmdlets.   Hey, Scripting Guy! How do I manage sites in SharePoint 2010 by using Windows PowerShell cmdlets? — KM   Hello KM, Microsoft Scripting Guy Ed Wilson here, once again I will defer the question […]<\/p>\n","protected":false},"author":595,"featured_media":87096,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[56,183,3,59,45],"class_list":["post-17051","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-scripting","tag-guest-blogger","tag-niklas-goude","tag-scripting-guy","tag-sharepoint","tag-windows-powershell"],"acf":[],"blog_post_summary":"

  Summary: The Microsoft Scripting Guys host guest blogger Niklas Goude as he discusses site management using Windows PowerShell cmdlets.   Hey, Scripting Guy! How do I manage sites in SharePoint 2010 by using Windows PowerShell cmdlets? — KM   Hello KM, Microsoft Scripting Guy Ed Wilson here, once again I will defer the question […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/17051","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/users\/595"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/comments?post=17051"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/17051\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media\/87096"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media?parent=17051"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/categories?post=17051"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/tags?post=17051"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}