NOTE – PDF format updated to include both SharePoint 2013 and 2016 notes.
Ever wondered what fixes are inside of a given CU? Please see attached PDF with full detail. I wanted a new format for easy reading. Show management and make the business case for why downtime should be taken to apply CUs. Also posted at http://sharepointupdates.com/
If you found this helpful, please leave a comment.
![shades_smile_thumb_thumb_thumb_thumb[2]](http://www.spjeff.com/wp-content/ftp_uploads/Whats-in-that-patch-SharePoint-2013--Oct_A762/shades_smile_thumb_thumb_thumb_thumb2.gif "shades_smile_thumb_thumb_thumb_thumb[2]")
| What’s in that patch – Jul 2018.PDF |
Even with Legacy auth disabled, you can successfully run Connect-PNPOnline.
Video demo shows changing SPO tenant security, then how to register new AppId for Connect-PNPOnline access to all site collections in tenant. The “AppRegNew” and “AppInv” ASPX pages can be used to establish authentication channel for PowerShell work in PNP on Office 365 tenants where Legacy Auth is disabled.
Cheers!
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 |
# 1) Check SPO Connect-SPOService "https://spjeff-admin.sharepoint.com" Get-SPOTenant | Select *legacy* | ft # 2) Disable Legacy Set-SPOTenant -LegacyAuthProtocolsEnabled $false Get-SPOTenant | Select *legacy* | ft # 3) Register App # https://spjeff-admin.sharepoint.com/_layouts/15/appregnew.aspx # 4) Invite App # https://spjeff-admin.sharepoint.com/_layouts/15/appinv.aspx # 5) PNP Login Connect-PNPOnline -AppId "e419e703-5293-402c-bb70-3aff593b850b" -AppSecret "secret-here" $w = Get-PNPWeb Get-PNPList -Web $w |
By default this value is set to $True.
Setting this parameter prevents Office clients using non-modern authentication protocols from accessing SharePoint Online resources.
A value of True- Enables Office clients using non-modern authentication protocols (such as, Forms-Based Authentication (FBA) or Identity Client Runtime Library (IDCRL)) to access SharePoint resources.
A value of False-Prevents Office clients using non-modern authentication protocols from accessing SharePoint Online resources.
Note
This may also prevent third-party apps from accessing SharePoint Online resources. Also, this will also block apps using the SharePointOnlineCredentials class to access SharePoint Online resources. For additional information about SharePointOnlineCredentials, see SharePointOnlineCredentials class.
While running Update-SBHost I saw the error below. The fix (admittedly strange) was to rename the application folder.
Seems internally SB expects “1.0” in the folder path. When running version 1.1 it appears we must rename the folder to “\1.0”, run the “Update-SBHost” cmdlet, and rename the folder back to “\1.1” in order for the Update-SBHost to complete successfully.
Cheers.
NOTE – PDF format updated to include both SharePoint 2013 and 2016 notes.
Ever wondered what fixes are inside of a given CU? Please see attached PDF with full detail. I wanted a new format for easy reading. Show management and make the business case for why downtime should be taken to apply CUs. Also posted at http://sharepointupdates.com/
If you found this helpful, please leave a comment.
| What’s in that patch – Jun 2018.PDF |
Fun software I work with every day.
Return to Top ▲
