17 May 2019
By popular demand (well, one person), the BLOB cache solution is ready for SharePoint Server 2019! The solution brings no new features as there aren’t any new BLOB cache settings for SharePoint Server 2019.
If you’re unfamiliar with this solution, it is a full trust solution that provides an interface in Central Admin -> Manage Web Applications to manage the BLOB Cache for a Web Application rather than having to edit the web.config by hand (never do this). This means that the settings persist in the Configuration database and deploy to your Web Application should you reprovision it or add a new SharePoint Server to the farm.
When you go to Manage Web Applications, a new BLOB cache button will be in the ribbon:
You can then edit a variety of BLOB cache settings:
Including flushing the BLOB cache and restoring the BLOB cache settings to their defaults (which will also disable BLOB cache since that’s also a default).
Make sure you plan on a mini-outage to make any BLOB cache settings change. As changing anything in the web.config by hand or through automated means recycles the IIS Application Pool in use by the IIS site, there will be a brief outage as you save these settings.
Enjoy!
14 May 2019
The SharePoint 2019 May 2019 Updates have been released.
For all SharePoint updates, visit SharePoint Updates.
14 May 2019
The SharePoint 2016 May 2019 Updates have been released.
For all SharePoint updates, visit SharePoint Updates.
08 May 2019
SharePoint Server 2019 does not support anonymous sharing links (aka guest links). However, it only takes four lines of PowerShell to implement. In addition, you get link expiration. This configuration does require Office Online Server as the guest sharing links leverage the web-based Office viewer/editor. Keep in mind, this isn’t a supported configuration by Microsoft.
To enable this feature, run the following PowerShell from the SharePoint Management Shell:
$farm = Get-SPFarm
$farm.Properties.Add("GuestSharingEnabled",$true)
$farm.Properties.Add("SPO-GuestSharingUIEnabled",$true)
$farm.Update()
When we visit a modern Document Library, we can now select the ‘Anyone’ option with link expiration:
This yields a URL similar to the following:
https://devsp07.cobaltatom.com/sites/team/_layouts/15/guestaccess.aspx?guestaccesstoken=sn%2F%2FbPXsO9UB8ot8LpLUEoXYxawDnQsipOl34Q%2Fj8f8%3D&docid=1f71e8af92a384035b00ebcb2bc322f4a&rev=1&expiration=2019-05-08T07%3A00%3A00.000Z&e=OCqpdW
We can then see that a link is available with a set expiration:
However you get the link to the end user (copy link or email), here is what the recipient sees (after enabling editing):
Finally, when the link expires should you choose that option, this is what the recipient sees:
And again, this is unsupported by Microsoft. After experimenting, you can disable this functionality by running the below cmdlets.
$farm = Get-SPFarm
$farm.Properties.Remove("GuestSharingEnabled")
$farm.Properties.Remove("SPO-GuestSharingUIEnabled")
$farm.Update()
28 Apr 2019
Have you seen this lately? It appears to any Office 365 Group owner where a Team has not been associated with a SharePoint Online site.
There’s a simple method to disable it. Using the SharePoint Online PnP cmdlets, run the following cmdlet.
$tenant = "https://tenant-admin.sharepoint.com"
$web = "https://tenant.sharepoint.com/sites/ModernTeam"
Connect-PnPOnline -Url $tenant -SPOManagementShell
$site = Get-PnPTenantSite -Detailed -Url $web
if ($site.DenyAddAndCustomizePages -ne 'Disabled') {
$site.DenyAddAndCustomizePages = 'Disabled'
$site.Update()
$site.Context.ExecuteQuery()
}
Set-PnPPropertyBagValue -Key 'TeamifyHidden' -Value 'True'
The first portion of the above script verifies that DenyAndAddCustomizePages is disabled on the site. This enables us to set a property bag value of TeamifyHidden to true. If you refresh the homepage after setting the value, the dialog box to create Teams should no longer appear.
At the time of writing, there is no method to disable this tenant-wide. It must be disabled on a Site Collection by Site Collection basis.