SSMS Quick Install from PowerShell
Waned to share PowerShell snippet to download SQL Management Studio (SSMS) with one liner and the AKA MS redirect service. Cheers
Code
iwr https://aka.ms/ssmsfullsetup -outfile ssms.exe; .\ssms.exe
Screenshot
Practical PowerShell Logs
All scheduled PowerShell files should generate LOGs. “Start-Transcript” is a great cmdlet for this. Adding a few more features can boost operations support. LOGs answer essentials support questions like:
- Which parent PS1 generated this LOG?
- Did script perform needed functions?
- Any errors?
- How long did it take?
- Which user and computer ran the script?
Below is code template I recommend to for scheduled PowerShell jobs to generate a LOG. Key features include:
- Auto detect current folder and script PS1
- Create \LOG\ subfolder
- Prefix to match parent PS1
- Suffix with unique date time stamp
- Elapsed run duration (Days, Hours, Minutes)
Thank you to @ToddKlindt for improvements to formula and elapsed time. Cheers.
Video
Code
function Main() {
### YOUR CODE HERE
}
# Open Log
$prefix = $MyInvocation.MyCommand.Name
$host.UI.RawUI.WindowTitle = $prefix
$stamp = Get-Date -UFormat "%Y-%m-%d-%H-%M-%S"
Start-Transcript "$PSScriptRoot\log\$prefix-$stamp.log"
$start = Get-Date
Main
# Close Log
$end = Get-Date
$totaltime = $end - $start
Write-Host "`nTime Elapsed: $($totaltime.tostring("hh\:mm\:ss"))"
Stop-TranscriptDownload
https://github.com/spjeff/spadmin/blob/master/Practical-PowerShell-LOGs.ps1
VIDEO – Disable Quick Edit for long running PowerShell
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.
Video
Screenshot
VIDEO – Load PNP the Right Way
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
Video
Code
# 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
