When running PowerShell administration jobs for many hours within RDP session, we are open to risk of accidental pause. Other admins might RDP into server, click around, switch windows, and accidentally pause.
Disabling the default “Quick Edit” PowerShell window feature ensures protection for script to continue uninterrupted.
Cheers.
NOTE – PDF format updated to include both SharePoint 2013, 2016, and 2019 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 https://sharepointupdates.com/
If you found this helpful, please leave a comment.
![shades_smile_thumb_thumb_thumb_thumb[2]](https://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 – Feb 2020.PDF |
Quick post about detecting if PowerShell PNP is available on the local PC and installing is missing (for new systems) to make PS1 script more portable across servers.(1) Detect command (2) Install module if missing (3) Import module. Cheers
# Load PNP module, the right way
Add-Type -Assembly "System.IO.Compression.FileSystem" -ErrorAction SilentlyContinue | Out-Null
$pnp = Get-Command Connect-PnPOnline -ErrorAction SilentlyContinue
if (!$pnp) {
Install-Module "SharePointPnPPowerShellOnline" -Force
}
Import-Module "SharePointPnPPowerShellOnline" -ErrorAction SilentlyContinue | Out-Null
Wanted to share demo for the install and configuration of Expense Report sample application. PowerApps and MS Flow leveraged to create validated input, mobile ready, rich forms input experience. MS Flow applied for approval routing and audit trail. Easily submit new request, automate approval, and enable full tracking with PowerApps and MS Flow working together. Cheers.
Fun software I work with every day.
Return to Top ▲