{"id":80745,"date":"2016-11-10T00:01:31","date_gmt":"2016-11-10T08:01:31","guid":{"rendered":"https:\/\/blogs.technet.microsoft.com\/heyscriptingguy\/?p=80745"},"modified":"2019-02-18T09:10:21","modified_gmt":"2019-02-18T16:10:21","slug":"manage-sharepoint-online-site-collections-and-the-web-templates-with-powershell","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/scripting\/manage-sharepoint-online-site-collections-and-the-web-templates-with-powershell\/","title":{"rendered":"Manage SharePoint Online site collections and the web templates with PowerShell"},"content":{"rendered":"

Summary:<\/strong> PowerShell commands can\u00a0manage site collections and the web templates that\u00a0create site collections.<\/span><\/p>\n

Christopher Weaver is a Microsoft Premier Field Engineer (PFE) who focuses on SharePoint and Office 365 solutions for large enterprise Premier customers. He has been doing PowerShell and SharePoint with Microsoft for nine years. In his spare time, he enjoys backpacking, hiking, kite surfing, and spending time with his kids and dog. You can follow him on his blog at https:\/\/blogs.technet.microsoft.com\/christwe\/<\/a>.<\/p>\n

Hello All,<\/p>\n

As we prepare our SharePoint Online environment for migration, we will need to be able to manage site collections and the web templates we use to create those site collections.\u00a0 First, let\u2019s look at the available cmdlets in this category.<\/p>\n

Get-SPOWebTemplate<\/strong> \u2013 Gets all site templates that are available, or you can get specific templates based on different parameters.\u00a0 In the example, we get the default Team Site web template.<\/p>\n

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

Get-SPOWebTemplate -Name STS#0<\/code><\/p>\n

Get-SPOSite<\/strong> \u2013 Gets one or more site collections. You could then take that object and pass it to another cmdlet or use its members.<\/p>\n

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

Get-SPOSite https:\/\/mmr258720.sharepoint.com<\/code><\/p>\n

New-SPOSite<\/strong> \u2013 Creates a new site collection. It has many parameters, so you can set several properties automatically at creation time.<\/p>\n

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

New-SPOSite -url https:\/\/mmr258720.sharepoint.com\/sites\/test1 -Owner admin@mmr258720.onmicrosoft.com -StorageQuota 26214400<\/code><\/p>\n

Remove-SPOSite<\/strong> \u2013 Moves a site collection to the recycle bin to permanently delete the site collection. Before the site is permanently deleted, you need to run the Remove-SPODeletedSite<\/strong> command or wait approximately 90 days.\u00a0 During this time, the site collection will not count towards storage quotas.<\/p>\n

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

Remove-SPOSite https:\/\/mmr258720.sharepoint.com\/sites\/test1<\/code><\/p>\n

Set-SPOSite<\/strong> \u2013 Allows you to set many different properties on an existing site collection.<\/p>\n

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

Set-SPOSite https:\/\/mmr258720.sharepoint.com\/sites\/mr -lockstate NoAccess<\/code><\/p>\n

Test-SPOSite<\/strong> \u2013 This command will run one or several different health rules and then return the results.<\/p>\n

This command only<\/u> produces a report. It does not make any changes to your site.\u00a0 After you have reviewed the report and are comfortable with the repairs, then please run the Repair-SPOSite<\/strong> cmdlet, which I describe later.<\/p>\n

The site health rules are:<\/p>\n\n\n\n\n\n\n\n\n\n\n
Rule name<\/span><\/th>\nRule ID<\/span><\/th>\n<\/tr>\n
Conflicting Content Types<\/td>\nbefe203b-a8c0-48c2-b5f0-27c10f9e1622<\/td>\n<\/tr>\n
Customized Files<\/td>\ncd839b0d-9707-4950-8fac-f306cb920f6c<\/td>\n<\/tr>\n
Missing Galleries<\/td>\nee967197-ccbe-4c00-88e4-e6fab81145e1<\/td>\n<\/tr>\n
Missing Parent Content Types<\/td>\na9a6769f-7289-4b9f-ae7f-5db4b997d284<\/td>\n<\/tr>\n
Missing Site Templates<\/td>\n5258ccf5-e7d6-4df7-b8ae-12fcc0513ebd<\/td>\n<\/tr>\n
Unsupported Language Pack References<\/td>\n99c946f7-5751-417c-89d3-b9c8bb2d1f66<\/td>\n<\/tr>\n
Unsupported MUI References<\/td>\n6da06aab-c539-4e0d-b111-b1da4408859a<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

 <\/p>\n

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

Test-SPOSite https:\/\/mmr258720.sharepoint.com<\/code><\/p>\n

Repair-SPOSite<\/strong> \u2013 Will run the health tests from the Test-SPOSite<\/strong> command and, when possible, will automatically repair an issue.\u00a0 After the command finishes running, it will provide a report with results.<\/p>\n

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

Repair-SPOSite https:\/\/mmr258720.sharepoint.com<\/code><\/p>\n

Upgrade-SPOSite<\/strong> \u2013 Performs site collection upgrade. By default, this will be build-to-build upgrade. However, on occasion it could become a version-to-version upgrade. In this case, you must run a health check in repair mode to ensure that the site collection can be upgraded.<\/p>\n

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

Upgrade-SPOSite https:\/\/mmr258720.sharepoint.com<\/p>\n

As we prepare to migrate, we must create the new site collection that we will be migrating to, so let\u2019s look at the cmdlets that will make this possible. The first cmdlet will be New-SPOSite<\/strong> because this is the command that will create the site collection. Let\u2019s look at the parameters we can use.<\/p>\n

NOTE:<\/strong> If a site collection in the Recycle bin has the same URL, this cmdlet will fail with an error that looks like this.<\/em><\/p>\n

New-SPOSite : A site already exists at url <\/em>https:\/\/tenant.sharepoint.com\/sites\/sitecollection<\/em><\/a><\/p>\n

The solution is to restore from the Recycle bin or permanently delete the site collection.<\/em><\/p>\n