I recently ran into the following error message when using OneDrive for Business via MySites (on-prem 2016).
“No free space. Your site is out of storage space and changes can’t be saved…”
The recommendation is to empty your recycle bin, but the recycle bin is probably empty.
The default storage limit for MySites is set to 100 MB (which doesn’t go so far these days).
If you already have a bunch of personal sites created, it’s not as easy as tweaking the quota template. You will need to update the quota template for future sites, then reset all existing sites to use the updated template as well.
Update the Quota Template
- Go to Central Admin
- Click “Application Management”
- Click “Specify quota templates” under “Site Collections”
- Change the “Personal Site” template to allow for more storage (I’d suggest at least 10GB, entered as 10240MB, but this will vary based on usage, industry, available space, etc.)
- Click OK
Learn more on quota templates: Create, edit, and delete quota templates in SharePoint Server
Set existing sites to use updated template
Now that you’ve set the storage quota template for future sites, we need to update pre-existing sites to adopt this new storage limit. We’ll need to do this via PowerShell.
- Remote connect to a SharePoint server
- Open SharePoint 2013/2016 Management Shell as administrator (right-click, Run as Administrator)
- Run the following script, replacing the web app address with your own, and the template name if different from Personal Site
$SPWebApp = Get-SPWebApplication https://mysites.MYORG.org
foreach ($SPSite in $SPWebApp.Sites)
if ($SPSite -ne $null)
Set-SPSite -Identity $SPSite.url -QuotaTemplate "Personal Site"
And that’s it! Once that has run successfully, all of your MySites should now have the new limit in place.
I’ve heard these mystical links called many things, whether persistent, permanent or durable, but they all mean the same thing:
Your document links will be unbreakable when changing file names or moving files because the links created for sharing/linking refer to the document by an ID instead of its common name.
But for this to work you must activate a site collection feature available only on SharePoint 2016 or later, or SharePoint Online/O365.
Before activating Document ID Service feature:
After activating Document ID Service feature:
Continue reading “Durable Document Links in SharePoint Server 2016 and Online/O365”
Consider either of these scenarios:
- Your organization and its departments are re-structuring and changing names
- Your IT department and content strategists decide on a new naming convention that affects your site names and URLs to access those sites OR you’re changing from http to https
- You have hundreds (thousands?) of documents, links, content queries and script references across your sites that refer to the old URLs and are now broken
Copying Sites/Structures or Creating Templates
- You need to create a team site template that contains default content and page designs
- You create the template with script references, page and promoted links that are absolute
- You have to update all of those links (some perhaps buried deep in your layouts folder) to the new site location URL unless those links are meant to call back to a different site.
Keep in mind that if a user doesn’t have access to the site or subsite library where referenced scripts are held, those scripts won’t run for that user no matter what. This can affect the look, feel, and function of the site which causes confusion and confidence issues when they call and you say “Looks fine to me!” and they have a different experience
Many of these issues and “cleanup tasks” can be avoided (for the most part) by using relative URLs instead of absolute URLs.
Continue reading “Why and when you should be using relative links in SharePoint”
Changing a SharePoint site collection name is easy enough (Site Settings –> “Title, description, and logo”), but changing the URL for a top-level site is a bit more involved than just changing a subsite URL. Note that this post applies to on-premise/server environments only.
Continue reading “Change a SharePoint site collection top-level site URL”
Sometimes “Marketing” becomes “Communication” or you’ve changed a site URL naming convention so that instead of “sharepoint.mycompany.com/marketing” you’ll be shortening all department sites to something like “sharepoint.mycompany.com/mark”. Follow these steps to change the name and URL for a SharePoint subsite.
Note: If you’re trying to change the URL for a top-level site (site collection level), you’ll need to change the URL as an administrator using PowerShell.
Continue reading “Change a SharePoint subsite name and URL”