By default deleting a site collection in Office 365 just moves the site collection to the recycle bin for 30 days, but there is not an option in the admin screen to remove it from the recycle bin. This is fine, unless you want to use the same url for a new site collection. In... Continue Reading →
Upgrading SharePoint Online\Office 365 site from 2010 to 2013 using PowerShell
As of the 27th February existing Office 365 tenants are able to self-upgrade their sites to the updated wave 15 version of SharePoint online. Sites can be upgraded on an individual basis using the UI, but if you want to upgrade multiple sites as part of a process it is (in my opinion) easier to... Continue Reading →
SharePoint 2013: Creating a Publishing Page and assigning a page layout using PowerShell
The following PowerShell can be used to create a publishing page and assign a page layout. #Get SPWeb $spWeb = Get-SPWeb("Site URL"); #Get Publishing Web $pubWeb = [Microsoft.SharePoint.Publishing.PublishingWeb]::GetPublishingWeb($spWeb) #Finds the appropriate page layout $pl = $pubWeb.GetAvailablePageLayouts() | Where { $_.Name -eq "Page Layout Name"} $pages = $pubWeb.GetPublishingPages(); #Create the page; $page = $pages.Add("Page Name", $pl)... Continue Reading →
SharePoint 2013: PowerShell to update a term sets Submission Policy
The following PowerShell can be used to update a terms sets submission policy to open or closed. #Connect to Central Admin $Session = new-object Microsoft.SharePoint.Taxonomy.TaxonomySession("Central Admin URL") #Connect to Managed Metadata Service $Store = $Session.TermStores["Managed Metadata Service Name"] #Get the group $Group = $Store.Groups["Group Name"]; #Get the Term Set $TermSet = $Group.TermSets["Term Set Name"]; #Update... Continue Reading →
SharePoint 2013 Error: The filtering process has been terminated
I had just completed a PowerShell scripted deployment of a SharePoint farm and was just performing the final checks when I noticed the following error in the crawl logs. "The filtering process has been terminated" This turned out that because in the PowerShell script I had specified that the SharePoint installation location should be different to... Continue Reading →